Bugzilla will be upgraded to version 5.0 on a still to be determined date in the near future. The original upgrade date has been delayed.
Bug 892140 - (CVE-2013-0764) CVE-2013-0764 Mozilla: Crash due to handling of SSL on threads (MFSA 2013-07)
CVE-2013-0764 Mozilla: Crash due to handling of SSL on threads (MFSA 2013-07)
Status: CLOSED NOTABUG
Product: Security Response
Classification: Other
Component: vulnerability (Show other bugs)
unspecified
All Linux
high Severity high
: ---
: ---
Assigned To: Red Hat Product Security
impact=important,public=20130108,repo...
: Security
Depends On:
Blocks: 890133
  Show dependency treegraph
 
Reported: 2013-01-05 08:19 EST by Huzaifa S. Sidhpurwala
Modified: 2013-01-08 14:24 EST (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2013-01-05 08:20:16 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
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-01-05 08:19:24 EST
Jerry Baker reported a crashing issue found through Thunderbird when downloading messages over a Secure Sockets Layer (SSL) connection. This was caused by a bug in the networking code assuming that secure connections were entirely handled on the socket transport thread when they can occur on a variety of threads. The resulting crash was potentially exploitable.

While the initial issue was found through Thunderbird, the affected networking library is common to Mozilla code.


External Reference:

http://www.mozilla.org/security/announce/2013/mfsa2013-07.html


Acknowledgements:

Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Jerry Baker as the original reporter.

Statement:

Not Vulnerable. 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.