DESCRIPTION: Some vulnerabilities have been reported in Mozilla Firefox, which can be exploited by malicious people to bypass certain security restrictions, disclose sensitive information, conduct cross-site scripting attacks, or potentially compromise a user's system.
1) Multiple errors in the layout engine can be exploited to corrupt memory and potentially execute arbitrary code.
2) An error in the processing of XBL bindings can be exploited to bypass the same-origin policy and read data from a target document in another domain.
Successful exploitation of this vulnerability requires that the target document contains a "" element and that the "id" of the read binding is known.
This is related to vulnerability #3 in: SA31984
4) An error exists when processing "XMLHttpRequest" requests to a web server which redirects the browser via a 302 HTTP status code. This can be exploited to bypass the same-origin policy and disclose sensitive information from another domain.
6) An error when processing URLs starting with whitespace or certain control characters can be exploited to output a malformed URL when rendering a hyperlink.
7) An error in the CSS parser when processing "\0" sequences can be exploited to potentially bypass third party script sanitation routines.
The vulnerabilities are reported in versions prior to 22.214.171.124.
PROVIDED AND/OR DISCOVERED BY: The vendor credits: 1) Daniel Veditz, Jesse Ruderman, and David Baron 2) Boris Zbarsky 3, 8-10) moz_bug_r_a4 4) Marius Schilder of Google Security 5) Chris Evans of Google Security 6) Chip Salzenberg, Justin Schuh, Tom Cross, and Peter William 7) Kojima Hajime
Please Note: Secunia recommends that you verify all advisories you receive by clicking the link. Secunia NEVER sends attached files with advisories. Secunia does not advise people to install third party patches, only use those supplied by the vendor.
They SWEAR this will be the last 2.0.0.x. You should be running FF3 anyway.
Just remember, every time you post one of these advisories brings to mind all the other times you DIDN'T post when there was an update. My Firefox went ahead and updated itself on its own before I read any of this stuff anyway.
With the recent windows IE issue, the fix was to use a different browser. In the past, we've pushed people to use FF via a banner add and openly supporting it. I thought that this highly critical was important enough to mention it.
I guess I can stop posting these if its such an issue.
I have no problem getting to http://luchawiki.org at home, but when I try to check in from work, I can't get to the website. I know - it's not a blocking/filtering issue - it's not the site just going down while I'm at work.