dbcve.org
FirefoxWeb browser · Mozilla

CVE-2020-6796

HIGH · 8.8 CVSS v3.1 Published 2020-03-02
Fix available
A fix is available. Upgrade to 68.5.0 / 73.0 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
A content process could have modified shared memory relating to crash reporting information, crash itself, and cause an out-of-bound write. This could have caused memory corruption and a potentially exploitable crash. This vulnerability affects Firefox < 73 and Firefox < ESR68.5.

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

A content process in Firefox could modify shared memory related to crash reporting information, allowing an out-of-bounds write that causes memory corruption and potentially exploitable crashes.

MitigationUpgrade Firefox to version 73 or later (or Firefox ESR to 68.5+) to apply the patched version.

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:< 73.0
Firefox EsrWeb browser
Affected:< 68.5.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.1/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 if Firefox is installed
    On Windows, check for firefox.exe in typical install locations (e.g., C:\Program Files\Mozilla Firefox\ or C:\Program Files (x86)\Mozilla Firefox\). On macOS, check /Applications/Firefox.app. On Linux, run 'which firefox' or check /usr/lib/firefox/.
    Affected if Firefox executable is found in the system
  2. Determine installed Firefox version
    Run 'firefox --version' from command line, or on Windows right-click firefox.exe and select Properties > Details to view File Version. On macOS, right-click Firefox.app > Get Info to see the version.
    Affected if Version number cannot be determined or is below 73.0 (or below 68.5.0 for ESR)
  3. Confirm Firefox edition type
    Check if the installation is Standard Firefox or Firefox ESR. On Windows, look for 'ESR' in the install folder name or program name. On macOS, check the application name in /Applications. On Linux, run 'firefox --version' which may display 'ESR' in output.
    Affected if Running Firefox ESR version below 68.5.0, or standard Firefox version below 73.0

If Firefox or Firefox ESR is installed and its version number is below 73.0 (standard) or below 68.5.0 (ESR), the environment is affected by this vulnerability.

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 68.5.0 / 73.0 or later
Fixed in 68.5.073.0
Interim mitigation

Upgrade Firefox to version 73 or later (or Firefox ESR to 68.5+) to apply the patched version.

Fix this in Firefox Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing1.0 h
  • Review / QA1.0 h
5.0 hours of engineering $890
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,424.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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