dbcve.org
FirefoxWeb browser · Mozilla

CVE-2016-2807

HIGH · 8.8 CVSS v3.0 Published 2016-04-30
Fix available
A fix is available. Upgrade to after 45.0.2 or later.
See remediation →
95/100
Remediation priority · Urgent
Remotely reachable No privileges

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 unspecified vulnerabilities in the browser engine in Mozilla Firefox before 46.0, Firefox ESR 38.x before 38.8, and Firefox ESR 45.x before 45.1 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 confidence

Multiple memory corruption vulnerabilities in the Mozilla Firefox browser engine allow remote attackers to cause denial of service through application crashes or potentially execute arbitrary code via unspecified vectors in Firefox before 46.0, ESR 38.x before 38.8, and ESR 45.x before 45.1.

MitigationUpgrade affected Firefox installations to version 46.0 or later (or ESR 38.8/45.1+) to patch the browser engine vulnerabilities.

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:<= 45.0.2= 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= 38.5.0= 38.5.1
LeapOperating system
Affected:= 42.1
OpensuseOperating system
Affected:= 13.1= 13.2
Linux EnterpriseOperating system
Affected:= 12.0

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
Privileges
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

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 installed Firefox version
    Open Firefox, go to Help > About Firefox, or run 'firefox --version' from command line
    Affected if The version shown is 45.0.2 or lower, or is one of these: 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, 38.5.0, 38.5.1
  2. Check Firefox ESR version if applicable
    If using ESR branch, run 'firefox --version' or check Help > About Firefox for ESR indicator
    Affected if The ESR version is 38.x before 38.8, or 45.x before 45.1
  3. Verify browser engine is in use
    Confirm Firefox is installed and functional - the vulnerability exists in the browser engine (SpiderMonkey)
    Affected if Firefox is actively used or installed on the system
  4. Check system package version on Suse-based systems
    On Suse Linux Enterprise 12.0, OpenSUSE 13.1, 13.2, or Leap 42.1, run 'rpm -q firefox' or check via package manager
    Affected if The packaged Firefox version matches the affected versions listed for that distribution

You are affected if your installed Firefox is version 45.0.2 or lower, any of the specific 38.x versions listed, or an ESR version before 38.8 or 45.1.

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.

From vendor data
Upgrade available Upgrade to a release after 45.0.2
Interim mitigation

Upgrade affected Firefox installations to version 46.0 or later (or ESR 38.8/45.1+) to patch the browser engine vulnerabilities.

Fix this in Firefox Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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