FedoraOperating system · Fedoraproject
CVE-2015-7213
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedInteger overflow in the MPEG4Extractor::readMetaData function in MPEG4Extractor.cpp in libstagefright in Mozilla Firefox before 43.0 and Firefox ESR 38.x before 38.5 on 64-bit platforms allows remote attackers to execute arbitrary code via a crafted MP4 video file that triggers a buffer overflow.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceInteger overflow in libstagefright's MPEG4Extractor::readMetaData function allows a buffer overflow when parsing crafted MP4 files on 64-bit platforms, enabling remote code execution.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
FedoraOperating system
= 22= 23
FirefoxWeb browser
= 38.0= 38.0.1= 38.0.5= 38.1.0= 38.1.1= 38.2.0= 38.2.1= 38.3.0= 38.4.0<= 42.0= 42.1= 13.1= 13.2CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- M
- Authentication
- None
- Confidentiality
- Partial
- Integrity
- Partial
- Availability
- Partial
AV:N/AC:M/Au:N/C:P/I:P/A:P
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Check installed Firefox versionRun 'firefox --version' or check the package manager (dnf for Fedora, zypper for openSUSE) for installed firefox package versionAffected if Version matches any of: 38.0, 38.0.1, 38.0.5, 38.1.0, 38.1.1, 38.2.0, 38.2.1, 38.3.0, 38.4.0, or any version <= 42.0
-
Confirm system is 64-bitRun 'uname -m' or 'arch' command; 64-bit appears as 'x86_64' or 'amd64'Affected if System architecture is 64-bit (x86_64/amd64) and Firefox version is in the affected range
-
Check if libstagefright component existsSearch for libstagefright library files: 'find /usr -name "*stagefright*" 2>/dev/null' on Linux systemsAffected if libstagefright library is present on the system (required for the vulnerability to be triggerable)
-
Verify Fedora version if applicableCheck /etc/fedora-release or run 'cat /etc/os | grep -i fedora'Affected if Running Fedora 22 or Fedora 23 with affected Firefox versions installed
System is affected if running a 64-bit platform with Firefox version 38.0 through 42.0 (or any version <= 42.0) and the libstagefright library is present, particularly on Fedora 22/23, openSUSE 13.1/13.2, or openSUSE Leap 42.1.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataUpdate Firefox to version 43.0 or later (or Firefox ESR 38.5 or later) on all affected 64-bit systems to patch the vulnerable libstagefright component.
Fix this in Fedora
Scoped from the published advisory
- Consultation1.0 h
- Implementation1.0 h
- Testing1.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,200.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2015-7213 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sources- www.mozilla.org
- lists.fedoraproject.org
- lists.fedoraproject.org
- lists.opensuse.org
- lists.opensuse.org
- lists.opensuse.org
- lists.opensuse.org
- lists.opensuse.org
- lists.opensuse.org
- lists.opensuse.org
- lists.opensuse.org
- rhn.redhat.com
- www.debian.org
- www.debian.org
- www.oracle.com
- www.oracle.com
- www.securityfocus.com
- www.securitytracker.com
- www.ubuntu.com
- www.ubuntu.com
- bugzilla.mozilla.org
- security.gentoo.org
- nvd.nist.gov
Practitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2015-7213 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data