Bug 1023846 - (CVE-2013-5591) CVE-2013-5591 Mozilla: Miscellaneous memory safety hazards (rv:25.0 / rv:124.1) (MFSA 2013-93)
CVE-2013-5591 Mozilla: Miscellaneous memory safety hazards (rv:25.0 / rv:124....
Product: Security Response
Classification: Other
Component: vulnerability (Show other bugs)
All Linux
urgent Severity urgent
: ---
: ---
Assigned To: Red Hat Product Security
: Security
Depends On:
Blocks: 1015366
  Show dependency treegraph
Reported: 2013-10-28 00:51 EDT by Huzaifa S. Sidhpurwala
Modified: 2013-10-29 13:11 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2013-10-28 01:19:29 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Huzaifa S. Sidhpurwala 2013-10-28 00:51:13 EDT
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.

In general these flaws cannot be exploited through email in the Thunderbird and Seamonkey products because scripting is disabled, but are potentially a risk in browser or browser-like contexts.

Vladimir Vukicevic reported a crash that affected Firefox ESR 24, and Firefox 24.

Jesse Ruderman, Gary Kwong, and Kannan Vijayan reported memory safety problems and crashes that affect Firefox 24.

External Reference:



Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Vladimir Vukicevic, Jesse Ruderman, Gary Kwong, and Kannan Vijayan as the original reporter.


This issue does not affect the version of firefox and thunderbird as shipped with Red Hat Enterprise Linux 5 and 6

Note You need to log in before you can comment on or make changes to this bug.