dbcve.org
FirefoxWeb browser · Mozilla

CVE-2016-2835

HIGH · 8.8 CVSS v3.0 Published 2016-08-05
Fix available
A fix is available. Upgrade to after 47.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 48.0 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 unspecified vulnerabilities in Mozilla Firefox's browser engine before version 48.0 allow remote attackers to trigger memory corruption, causing denial of service through application crashes or potentially achieve arbitrary code execution via unknown vectors.

MitigationUpgrade Firefox to version 48.0 or later to address all multiple browser engine vulnerabilities. This is a critical security update that should be prioritized given the CVSS 8.8 severity rating and potential for arbitrary code execution.

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:<= 47.0.1

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 Firefox version via About dialog
    Open Firefox, click the menu button (three horizontal lines), select Help, then About Firefox. The version number is displayed in the window that opens.
    Affected if The displayed version is 47.0.1 or earlier (e.g., 47.0, 46.0, 45.x, etc.)
  2. Check Firefox version via command line
    Run the command: firefox --version or firefox -v. On Windows, you can also check: "C:\Program Files\Mozilla Firefox\firefox.exe" -v
    Affected if The reported version is 47.0.1 or any version lower than 48.0
  3. Check Firefox version via registry (Windows)
    Open Registry Editor and navigate to HKEY_LOCAL_MACHINE\SOFTWARE\Mozilla\Mozilla Firefox\CurrentVersion (or HKLM\SOFTWARE\WOW6432Node\Mozilla\Mozilla Firefox\CurrentVersion for 32-bit Firefox on 64-bit Windows)
    Affected if The value in the CurrentVersion key is 47.0.1 or lower
  4. Check Firefox package version (Linux)
    Run: dpkg -l firefox | grep firefox (Debian/Ubuntu) or rpm -q firefox (RHEL/CentOS)
    Affected if The listed package version is less than 48.0 (e.g., 47.0.1-0ubuntu1, 47.0-1.el7, etc.)

A user is affected if they have any installed version of Mozilla Firefox that is 47.0.1 or lower, since the vulnerable browser engine code exists in all versions up through 47.0.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 47.0.1
Interim mitigation

Upgrade Firefox to version 48.0 or later to address all multiple browser engine vulnerabilities. This is a critical security update that should be prioritized given the CVSS 8.8 severity rating and potential for arbitrary code execution.

Fix this in Firefox Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,040
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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