Nine new vulnerabilities in Oracle Java announced today. Nicely summarized details are at the SecurityFocus website.
Oracle Java SE and Java for Business ‘XNewPtr()’ Remote Code Execution Vulnerability
2010-06-18
http://www.securityfocus.com/bid/39083
Oracle Java SE and Java for Business CVE-2010-0848 Remote Java 2D Vulnerability
2010-06-18
http://www.securityfocus.com/bid/39078
Oracle Java SE and Java for Business Sound Component MIDI Stream Remote Code Execution Vulnerability
2010-06-18
http://www.securityfocus.com/bid/39084
Oracle Java SE and Java for Business CVE-2010-0849 Remote Java 2D Vulnerability
2010-06-18
http://www.securityfocus.com/bid/39073
Oracle Java SE and Java for Business ‘MixerSequencer’ Remote Code Execution Vulnerability
2010-06-18
http://www.securityfocus.com/bid/39077
Oracle Java SE and Java for Business CVE-2010-0847 Remote Java 2D Vulnerability
2010-06-18
http://www.securityfocus.com/bid/39071
Oracle Java SE and Java for Business ImageIO ‘JPEGImageReader’ Remote Code Execution Vulnerability
2010-06-18
http://www.securityfocus.com/bid/39067
Oracle Java SE and Java for Business JRE Trusted Method Chaining Remote Code Execution Vulnerability
2010-06-18
http://www.securityfocus.com/bid/39065
Oracle Java Runtime Environment ‘JPEGImageEncoderImpl’ Remote Heap Buffer Overflow Vulnerability
2010-06-18
http://www.securityfocus.com/bid/39062
Apple Mac OS X CUPS Web Interface Unspecified Information Disclosure Vulnerability
2010-06-18
http://www.securityfocus.com/bid/40897
Friday, the InetDaemon.Com website crashed. HTTP 500 errors all over the place and no WordPress, just blank error pages. Oh, NO! What do I do!?!
If you haven’t been back in a while, you may have to create a new account. A spammer’s automation went berzerk and created hundreds of fake logins in an attempt to create comment spam. Because I use WP-SpamFree, comment spam is blocked, but the spammer’s automation was too stupid to figure that out and it just kept creating one account after another. To prevent this in future, I added WP-reCaptcha so that account creation ostensibly will require a human being to get past the reCaptcha protection. Unfortunately, I had to clean out the list of users and I’m afraid there wasn’t any way to tell for certain which accounts were real and which were fake so I reset the user database.
Logins are not required to read the blog, yet. Pretty soon, a login will be required in order to read full articles and those who have logins won’t see external advertising, though I will still advertise any seminars and training events I’m providing.