Access member only content, take part in discussions with comments on blogs, news and reviews and receive all the latest security industry news directly to your inbox. Join now for free.
A confirmation email has been sent to your email address - SUPPLIED EMAIL HERE. Please click on the link in the email to verify your email address. You need to verify your email before you can start posting.
If you do not receive your confirmation email within the next few minutes, it may be because the email has been captured by a junk mail filter. Please ensure you add the domain @scmagazine.com.au to your white-listed senders.
It claimed that the patch, named CVE-2009-1441, would mean that a failure to properly validate input from a renderer (tab) process could allow an attacker to crash the browser and possibly run arbitrary code with the privileges of the logged on user. To exploit this vulnerability, an attacker would need to be able to run arbitrary code inside the renderer process. Google has rated this vulnerability as critical. A vulnerability was also patched that would allow an attacker to be able to run arbitrary code within the Google Chrome sandbox. This vulnerability has been rated as high, as a victim would need to visit a page under an attacker's control, and any code that an attacker might be able to run inside the renderer process would be inside the sandbox. See original article on scmagazineus.com
It claimed that the patch, named CVE-2009-1441, would mean that a failure to properly validate input from a renderer (tab) process could allow an attacker to crash the browser and possibly run arbitrary code with the privileges of the logged on user.
To exploit this vulnerability, an attacker would need to be able to run arbitrary code inside the renderer process. Google has rated this vulnerability as critical.
A vulnerability was also patched that would allow an attacker to be able to run arbitrary code within the Google Chrome sandbox. This vulnerability has been rated as high, as a victim would need to visit a page under an attacker's control, and any code that an attacker might be able to run inside the renderer process would be inside the sandbox.
To begin commenting right away, you can log in below or register an account if you don't yet have one. Please read our guidelines on commenting. Offending posts will be removed and your access may be suspended. Abusive or obscene language will not be tolerated. The comments below do not necessarily reflect the views or opinions of SC Magazine, Haymarket Media or its employees.