Bug 40276 - Iceweasel: Security issues from 38.5 (4.0)
Iceweasel: Security issues from 38.5 (4.0)
Status: RESOLVED DUPLICATE of bug 39388
Product: UCS
Classification: Unclassified
Component: Security updates
UCS 4.0
Other Linux
: P5 normal (vote)
: ---
Assigned To: Security maintainers
https://www.mozilla.org/en-US/securit...
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2015-12-16 20:35 CET by Arvid Requate
Modified: 2017-06-01 18:34 CEST (History)
1 user (show)

See Also:
What kind of report is it?: ---
What type of bug is this?: ---
Who will be affected by this bug?: ---
How will those affected feel about the bug?: ---
User Pain:
Enterprise Customer affected?:
School Customer affected?:
ISV affected?:
Waiting Support:
Flags outvoted (downgraded) after PO Review:
Ticket number:
Bug group (optional): Security
Max CVSS v3 score:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Arvid Requate univentionstaff 2015-12-16 20:35:51 CET
+++ This bug was initially created as a clone of Bug #40273 ++++

Firefox ESR 38.5 fixes these issues:

* cross-origin restriction bypass using data: and view-source: uri scheme (CVE-2015-7214)
* potential underflow in 'covr', unchecked allocation and copy in Metadata::setData (CVE-2015-7222)
* integer underflow in covr MPEG4 processing (no cve? mfsa2015-147)
* 64bit: Overflow in MPEG4Extractor::readMetaData causes memory-safety bug (CVE-2015-7213)
* Underflow in RTPReceiverVideo::ParseRtpPacket causes memory-safety bug and information leak (CVE-2015-7205)
* Memset crash in mozilla::layers::BufferTextureClient::AllocateForSurface (CVE-2015-7212)
* UAF due to DataChannelConnection not Destroy()ed before deletion (CVE-2015-7210)
* Memory safety bugs fixed in Firefox ESR 38.5 and Firefox 43. (CVE-2015-7201)
Comment 1 Arvid Requate univentionstaff 2016-01-11 14:10:22 CET
Firefox ESR 38.5.2:

* Prevent MD5 Downgrade in TLS 1.2 Signatures (CVE-2015-7575)
Comment 2 Arvid Requate univentionstaff 2016-01-28 16:44:27 CET

*** This bug has been marked as a duplicate of bug 39388 ***