This script is Copyright (C) 2011-2013 Tenable Network Security, Inc.
The remote SuSE 11 host is missing one or more security updates.
Mozilla Firefox was updated to the 3.6.17 security release.
- Mozilla developers identified and fixed several memory
safety bugs in the browser engine used in Firefox and
other Mozilla-based products. Some of these bugs showed
evidence of memory corruption under certain
circumstances, and we presume that with enough effort at
least some of these could be exploited to run arbitrary
code. Credits. (MFSA 2011-12)
Mozilla developer Scoobidiver reported a memory safety
issue which affected Firefox 4 and Firefox 3.6.
- The web development team of Alcidion reported a crash
that affected Firefox 4, Firefox 3.6 and Firefox 3.5.
(CVE-2011-0069) Ian Beer reported a crash that affected
Firefox 4, Firefox 3.6 and Firefox 3.5. (CVE-2011-0070)
Mozilla developers Bob Clary, Henri Sivonen, Marco
Bonardo, Mats Palmgren and Jesse Ruderman reported
memory safety issues which affected Firefox 3.6 and
Firefox 3.5. (CVE-2011-0080)
Aki Helin reported memory safety issues which affected
Firefox 3.6 and Firefox 3.5. (CVE-2011-0074 /
Ian Beer reported memory safety issues which affected
Firefox 3.6 and Firefox 3.5. (CVE-2011-0077 /
Martin Barbella reported a memory safety issue which
affected Firefox 3.6 and Firefox 3.5. (CVE-2011-0072)
- Security researcher regenrecht reported several dangling
pointer vulnerabilities via TippingPoint's Zero Day
Initiative. (MFSA 2011-13 / CVE-2011-0065 /
CVE-2011-0066 / CVE-2011-0073)
- Security researcher Paul Stone reported that a Java
applet could be used to mimic interaction with form
autocomplete controls and steal entries from the form
history. (MFSA 2011-14 / CVE-2011-0067)
- David Remahl of Apple Product Security reported that the
Java Embedding Plugin (JEP) shipped with the Mac OS X
versions of Firefox could be exploited to obtain
elevated access to resources on a user's system. (MFSA
2011-15 / CVE-2011-0076)
- Security researcher Soroush Dalili reported that the
resource: protocol could be exploited to allow directory
traversal on Windows and the potential loading of
resources from non-permitted locations. The impact would
depend on whether interesting files existed in
predictable locations in a useful format. For example,
the existence or non-existence of particular images
might indicate whether certain software was installed.
(MFSA 2011-16 / CVE-2011-0071)
- Chris Evans of the Chrome Security Team reported that
the XSLT generate-id() function returned a string that
revealed a specific valid address of an object on the
memory heap. It is possible that in some cases this
address would be valuable information that could be used
by an attacker while exploiting a different memory
corruption but, in order to make an exploit more
reliable or work around mitigation features in the
browser or operating system. (MFSA 2011-18 /
See also :
Apply SAT patch number 4463.
Risk factor :
Critical / CVSS Base Score : 10.0
Public Exploit Available : true
Family: SuSE Local Security Checks
Nessus Plugin ID: 53647 ()
CVE ID: CVE-2011-0065CVE-2011-0066CVE-2011-0067CVE-2011-0069CVE-2011-0070CVE-2011-0071CVE-2011-0072CVE-2011-0073CVE-2011-0074CVE-2011-0075CVE-2011-0076CVE-2011-0077CVE-2011-0078CVE-2011-0080CVE-2011-0081CVE-2011-1202
The cookie settings on this website are set to 'allow all cookies' to give you the very best website experience. If you continue without changing these settings, you consent to this - but if you want, you can opt out of all cookies by clicking below.