FirefoxWeb browser · Mozilla

CVE-2015-4496

HIGH · 9.3 CVSS v2.0 Published 2015-08-16
Fix available
A fix is available. Upgrade to after 37.0.2 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

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 · unedited
Multiple integer overflows in libstagefright in Mozilla Firefox before 38.0 allow remote attackers to execute arbitrary code via crafted sample metadata in an MPEG-4 video file, a related issue to CVE-2015-1538.

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 confidence

Multiple integer overflows in Mozilla Firefox's libstagefright when parsing MPEG-4 video sample metadata allow remote attackers to execute arbitrary code by tricking users into opening specially crafted video files.

MitigationUpgrade Firefox to version 38.0 or later, which contains patched bounds checking in the libstagefright sample metadata parser. For custom applications using libstagefright, apply the corresponding upstream patch.

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
FirefoxWeb browser
Affected:<= 37.0.2
SolarisOperating system
Affected:= 11.3

CVSS 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
Complete
Integrity
Complete
Availability
Complete

AV:N/AC:M/Au:N/C:C/I:C/A:C

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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify Firefox version
    Open Firefox, go to Help > About Firefox, or run 'firefox --version' from command line
    Affected if Version number is 37.0.2 or lower
  2. Check for libstagefright library presence
    Search for libstagefright.so in Firefox installation directory or system libraries (common paths: /usr/lib/firefox/, ~/.mozilla/)
    Affected if The libstagefright library file exists in the Firefox installation
  3. Verify handling of MPEG-4 video content
    Check if Firefox has been used to open or preview .mp4, .m4v, or similar MPEG-4 container files; review browser history for media file access
    Affected if Users have opened or previewed MPEG-4 video files in Firefox
  4. Confirm Solaris environment (if applicable)
    On Oracle Solaris 11.3, check for presence of libstagefright in /usr/lib/ or application-specific paths using 'find /usr/lib -name '*stagefright*'
    Affected if Running Oracle Solaris 11.3 with libstagefright library present

If Firefox version is 37.0.2 or lower and the libstagefright library is present and has processed MPEG-4 video files, the system is vulnerable to arbitrary code execution via the integer overflow flaw.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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.

dbcve · scoped
Upgrade available Upgrade to a release after 37.0.2
Interim mitigation

Upgrade Firefox to version 38.0 or later, which contains patched bounds checking in the libstagefright sample metadata parser. For custom applications using libstagefright, apply the corresponding upstream patch.

Recommended fix High confidence

Firefox 38.0 or later

  1. Check current Firefox version via Help > About Firefox or by running 'firefox --version' in command line
  2. Back up your Firefox profile folder (contains bookmarks, passwords, saved sessions) before upgrading
  3. Download Firefox 38.0 or later from the official Mozilla website (www.mozilla.org)
  4. Uninstall the current Firefox version
  5. Install the upgraded Firefox 38.0 or later version

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Firefox Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,080
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,328.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2015-4496 — 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

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2015-4496 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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