CVE-2015-4473
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 · uneditedMultiple unspecified vulnerabilities in the browser engine in Mozilla Firefox before 40.0 and Firefox ESR 38.x before 38.2 allow remote attackers to cause a denial of service (memory corruption and application crash) or possibly execute arbitrary code via unknown vectors.
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 confidenceMultiple memory corruption vulnerabilities in Mozilla Firefox's browser engine affecting versions before 40.0 and ESR 38.x before 38.2. The unspecified flaws allow remote attackers to trigger memory corruption leading to denial of service or potentially achieve arbitrary code execution via unknown attack vectors.
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= 12.04= 14.04= 15.04= 7.0= 8.0<= 39.0.3= 38.0= 38.0.1= 38.0.5= 38.1.0= 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
- 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 checksWork through these to decide whether this CVE applies to you.
-
Check installed Firefox versionRun 'firefox --version' or 'firefox -v' in terminal, or look at Help > About Firefox in the browser UIAffected if Version is 39.0.3 or lower, or is 38.0, 38.0.1, 38.0.5, or 38.1.0 (any ESR 38.x before 38.2)
-
Check Firefox ESR versionRun 'firefox --version' and look for 'ESR' designation; ESR versions are typically installed on enterprise/distribution systemsAffected if Version shows as Firefox ESR 38.0, 38.0.1, 38.0.5, or 38.1.0 (any 38.x version before 38.2)
-
Verify package manager versionOn Debian/Ubuntu: 'dpkg -l | grep firefox' or 'apt list --installed | grep firefox'. On openSUSE: 'rpm -qa | grep firefox'Affected if Package shows firefox version <= 39.0.3 or any 38.x version before 38.2
-
Check browser engine componentsThis CVE affects the browser engine (Gecko). The vulnerability is present in the core rendering engine and triggers when processing certain web content.Affected if Firefox is running any vulnerable version listed above; the flaw is in the browser engine itself, not a separate module
You are affected if Firefox is installed at version 39.0.3 or lower, or at any Firefox ESR 38.x version before 38.2.
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.
dbcve · scopedUpgrade Mozilla Firefox to version 40.0 or later (or Firefox ESR to 38.2 or later) to obtain the patched browser engine components.
Firefox 40.0 or Firefox ESR 38.2
- 1. Back up any important browser data (bookmarks, saved passwords, extensions) either through Firefox Sync or manual export
- 2. Close all Firefox instances
- 3. Update Firefox to version 40.0 or later for the stable release, OR update Firefox ESR to version 38.2 or later for the ESR release
- 4. On Ubuntu/Debian: Run 'sudo apt-get update && sudo apt-get install firefox' or 'sudo apt-get upgrade firefox' to get the latest packaged version
- 5. On openSUSE: Run 'sudo zypper update firefox' or use YaST Online Update
- 6. Alternatively, download Firefox 40.0 or later directly from the official Mozilla website (https://www.mozilla.org/firefox/)
- 7. After installation, verify the version by navigating to 'Help' > 'About Firefox'
- 8. Ensure the version shows 40.0 or later (or ESR 38.2 or later)
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation1.0 h
- Implementation1.0 h
- Testing2.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,376.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2015-4473 — 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
- bugzilla.mozilla.org
- bugzilla.mozilla.org
- bugzilla.mozilla.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
- rhn.redhat.com
- www.debian.org
- www.debian.org
- www.oracle.com
- www.securitytracker.com
- www.securitytracker.com
- security.gentoo.org
- www.ubuntu.com
- www.ubuntu.com
- www.ubuntu.com
- www.ubuntu.com
- nvd.nist.gov
Practitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2015-4473 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