dbcve.org
FirefoxWeb browser · Mozilla

CVE-2015-4479

HIGH · 10.0 CVSS v2.0 Published 2015-08-16
Fix available
A fix is available. Upgrade to after 39.0.3 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 40.0 and Firefox ESR 38.x before 38.2 allow remote attackers to execute arbitrary code via a crafted saio chunk in MPEG-4 video data.

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 overflow vulnerabilities exist in libstagefright's parsing of the saio chunk within MPEG-4 video files. These overflows allow a remote attacker to trigger heap-based memory corruption and achieve arbitrary code execution by tricking a user into viewing specially crafted video content.

MitigationUpgrade Mozilla Firefox to version 40.0 or later (or Firefox ESR 38.2 or later) to incorporate the patched libstagefright library that properly validates integer values when parsing saio chunks in MPEG-4 containers.

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:<= 39.0.3= 38.0= 38.0.1= 38.0.5= 38.1.0
Ubuntu LinuxOperating system
Affected:= 12.04= 14.04= 15.04
OpensuseOperating system
Affected:= 13.1= 13.2

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
Low
Authentication
None
Confidentiality
Complete
Integrity
Complete
Availability
Complete

AV:N/AC:L/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. Check Mozilla Firefox version
    Open Firefox and navigate to Help > About Firefox, or run 'firefox --version' from command line
    Affected if Version is 38.0, 38.0.1, 38.0.5, 38.1.0, 39.0, 39.0.1, 39.0.2, or 39.0.3 (any version <= 39.0.3 that is not 38.2+ or 40.0+)
  2. Verify libstagefright is enabled in Firefox
    In Firefox address bar, go to about:config and check the media.libstagefright.enabled preference; verify it is set to true
    Affected if media.libstagefright.enabled is set to true (this enables the vulnerable code path)
  3. Check Ubuntu system version
    Run 'lsb_release -a' or check /etc/lsb-release file
    Affected if Ubuntu version is exactly 12.04, 14.04, or 15.04 and has vulnerable libstagefright packages installed
  4. Check openSUSE system version
    Run 'cat /etc/os-release' or 'cat /etc/SuSE-release'
    Affected if openSUSE version is exactly 13.1 or 13.2 and has vulnerable libstagefright packages installed

You are affected if Firefox version is <= 39.0.3 (and not patched 38.2+ or 40.0+), libstagefright is enabled, AND the underlying OS is Ubuntu 12.04/14.04/15.04 or openSUSE 13.1/13.2 with vulnerable libstagefright libraries.

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 39.0.3
Interim mitigation

Upgrade Mozilla Firefox to version 40.0 or later (or Firefox ESR 38.2 or later) to incorporate the patched libstagefright library that properly validates integer values when parsing saio chunks in MPEG-4 containers.

Recommended fix High confidence

Firefox 40.0 or Firefox ESR 38.2

  1. Update Firefox to version 40.0 or later (for standard release users)
  2. Update Firefox ESR to version 38.2 or later (for ESR users)
  3. On Ubuntu/Linux: Run 'sudo apt-get update && sudo apt-get upgrade firefox' or use the Software Updater
  4. On OpenSUSE: Run 'sudo zypper update MozillaFirefox' to apply the security patch
  5. Restart the browser after the update completes
  6. Verify the version by navigating to 'about:firefox' or checking Help > About Firefox
Caveat Upgrading from Firefox 38.x to 40.0 may cause some legacy extensions/plugins to become incompatible; Firefox ESR 38.2 is a safer minimal-update path for enterprise environments

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

Fix this in Firefox Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,130
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,408.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2015-4479 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

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-4479 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