dbcve.org
FirefoxWeb browser · Mozilla

CVE-2016-2818

HIGH · 8.8 CVSS v3.0 Published 2016-06-13
Fix available
A fix is available. Upgrade to after 46.0.1 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 47.0 and Firefox ESR 45.x before 45.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 · moderate confidence

Memory corruption vulnerabilities in Mozilla Firefox's browser engine (Gecko) affecting versions before 47.0 and Firefox ESR before 45.2. Remote attackers can exploit unspecified vectors to cause denial of service through memory corruption and application crashes, with potential for arbitrary code execution.

MitigationUpgrade Firefox to version 47.0 or later, or Firefox ESR to 45.2 or later, 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.1.0= 45.1.1<= 46.0.1
Debian LinuxOperating system
Affected:= 8.0
Enterprise Linux DesktopOperating system
Affected:= 5.0= 6.0= 7.0
Enterprise Linux For Ibm Z SystemsOperating system
Affected:= 5.0= 6.0= 7.0
Enterprise Linux For Ibm Z Systems EusOperating system
Affected:= 7.2
Enterprise Linux For Power Big EndianOperating system
Affected:= 5.0= 6.0= 7.0
Enterprise Linux For Power Big Endian EusOperating system
Affected:= 7.2
Enterprise Linux For Power Little EndianOperating system
Affected:= 7.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. Verify Firefox is installed
    Check for Firefox installation: On Windows, look in Program Files for Mozilla Firefox folder. On macOS, check /Applications for Firefox.app. On Linux, run 'which firefox' or check /usr/bin/firefox
    Affected if Firefox is not installed on the system, this CVE does not apply
  2. Determine Firefox version number
    Open Firefox, click menu > Help > About Firefox. Alternatively, run 'firefox --version' in command line. On Windows, check firefox.exe properties. On Linux, run 'rpm -q firefox' or 'dpkg -l firefox' for package version
    Affected if Cannot determine version - manual verification required
  3. Compare installed version to affected range
    The affected vulnerable versions are: 45.1.0, 45.1.1, and any version from 45.2 through 46.0.1. Also Firefox ESR versions before 45.2. Compare your detected version against these
    Affected if Installed version equals 45.1.0, 45.1.1, or is 45.2 through 46.0.1 (inclusive), or is Firefox ESR before 45.2 - system is affected

If Firefox is installed and its version is 45.1.0, 45.1.1, or any version from 45.2 through 46.0.1 (or Firefox ESR before 45.2), the environment is vulnerable to this CVE.

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

Upgrade Firefox to version 47.0 or later, or Firefox ESR to 45.2 or later, to patch the browser engine vulnerabilities.

Fix this in Firefox Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,750
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,800.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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