Lucene search

HistoryMar 15, 2013 - 7:04 p.m.

Security update for Mozilla Firefox (important)






MozillaFirefox has been updated to the 17.0.4ESR release.
Besides the major version update from the 10ESR stable
release line to the 17ESR stable release line, this update
brings critical security and bugfixes:

  • MFSA 2013-29 / CVE-2013-0787: VUPEN Security, via
    TippingPoint’s Zero Day Initiative, reported a
    use-after-free within the HTML editor when content script
    is run by the document.execCommand() function while
    internal editor operations are occurring. This could allow
    for arbitrary code execution.

The Firefox 17.0.3ESR release also contains lots of
security fixes:

  • MFSA 2013-28: Security researcher Abhishek Arya
    (Inferno) of the Google Chrome Security Team used the
    Address Sanitizer tool to discover a series of
    use-after-free, out of bounds read, and buffer overflow
    problems rated as low to critical security issues in
    shipped software. Some of these issues are potentially
    exploitable, allowing for remote code execution. We would
    also like to thank Abhishek for reporting four additional
    use-after-free and out of bounds write flaws introduced
    during Firefox development that were fixed before general

The following issues have been fixed in Firefox 19 and ESR

  • Heap-use-after-free in
    nsOverflowContinuationTracker::Finish, with
    -moz-columns (CVE-2013-0780)

Heap-buffer-overflow WRITE in
nsSaveAsCharset::DoCharsetConversion (CVE-2013-0782)

MFSA 2013-27 / CVE-2013-0776: Google security
researcher Michal Zalewski reported an issue where the
browser displayed the content of a proxy’s 407 response if
a user canceled the proxy’s authentication prompt. In this
circumstance, the addressbar will continue to show the
requested site’s address, including HTTPS addresses that
appear to be secure. This spoofing of addresses can be used
for phishing attacks by fooling users into entering
credentials, for example.

MFSA 2013-26 / CVE-2013-0775: Security researcher
Nils reported a use-after-free in nsImageLoadingContent
when content script is executed. This could allow for
arbitrary code execution.

MFSA 2013-25 / CVE-2013-0774: Mozilla security
researcher Frederik Braun discovered that since Firefox 15
the file system location of the active browser profile was
available to JavaScript workers. While not dangerous by
itself, this could potentially be combined with other
vulnerabilities to target the profile in an attack.

MFSA 2013-24 / CVE-2013-0773: Mozilla developer Bobby
Holley discovered that it was possible to bypass some
protections in Chrome Object Wrappers (COW) and System Only
Wrappers (SOW), making their prototypes mutable by web
content. This could be used leak information from chrome
objects and possibly allow for arbitrary code execution.

MFSA 2013-23 / CVE-2013-0765: Mozilla developer Boris
Zbarsky reported that in some circumstances a wrapped
WebIDL object can be wrapped multiple times, overwriting
the existing wrapped state. This could lead to an
exploitable condition in rare cases.

MFSA 2013-22 / CVE-2013-0772: Using the Address
Sanitizer tool, security researcher Atte Kettunen from
OUSPG found an out-of-bounds read while rendering GIF
format images. This could cause a non-exploitable crash and
could also attempt to render normally inaccesible data as
part of the image.

MFSA 2013-21: 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

Olli Pettay, Christoph Diehl, Gary Kwong, Jesse
Ruderman, Andrew McCreight, Joe Drew, and Wayne Mery
reported memory safety problems and crashes that affect
Firefox ESR 17, and Firefox 18.

Memory safety bugs fixed in Firefox ESR 17.0.3, and
Firefox 19 (CVE-2013-0783)