Safari 3 Beta Security Holes Closed

They may have released a hole-riddled beta, but at least Apple have been quick to do something about it.  Hot on the heels of the news that Safari 3 not only had the stability of a dodgy alpha release but was also susceptible to some critical vulnerabilities that could give an attacker control of your system, the coders have been busy and we're now up to version 3.0.1  It's recommended that you upgrade to the new release asap, but my general caveat from before still stands: if you're a casual internet user you probably want to wait until more of the compatibility and stability issues have been ironed out.

Details of the 3.0.1 changes after the cut.

CVE-ID: CVE-2007-3186

Impact: Visiting a malicious website may lead to arbitrary code execution.

Description: A command injection vulnerability exists in the Windows version of Safari 3 Public Beta. By enticing a user to visit a maliciously crafted web page, an attacker can trigger the issue which may lead to arbitrary code execution. This update addresses the issue by performing additional processing and validation of URLs. This does not pose a security issue on Mac OS X systems, but could lead to an unexpected termination of the Safari browser.

CVE-ID: CVE-2007-3185

Impact: Visiting a malicious website may lead to an unexpected application termination or arbitrary code execution.

Description: An out-of-bounds memory read issue in Safari 3 Public Beta for Windows may lead to an unexpected application termination or arbitrary code execution when visiting a malicious website. This issue does not affect Mac OS X systems.

CVE-ID: CVE-2007-2391

Impact: Visiting a malicious website may allow cross-site scripting.

Description: A race condition in Safari 3 Public Beta for Windows may allow cross site scripting. Visiting a maliciously crafted web page may allow access to JavaScript objects or the execution of arbitrary JavaScript in the context of another web page. This issue does not affect Mac OS X systems.