CVE-2020-6814
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 · uneditedMozilla developers reported memory safety bugs present in Firefox and Thunderbird 68.5. Some of these bugs showed evidence of memory corruption and we presume that with enough effort some of these could have been exploited to run arbitrary code. This vulnerability affects Thunderbird < 68.6, Firefox < 74, Firefox < ESR68.6, and Firefox ESR < 68.6.
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 confidenceMemory safety bugs in Firefox and Thunderbird 68.5 led to memory corruption vulnerabilities that could potentially be exploited for arbitrary code execution. This is a critical client-side vulnerability affecting multiple Mozilla products.
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< 74.0< 68.6.0= 16.04= 18.04= 19.10< 68.6.0CVSS 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
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/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 checksWork through these to decide whether this CVE applies to you.
-
Check installed Firefox versionRun 'firefox --version' or 'firefox -v' in terminal, or navigate to Firefox menu > Help > About FirefoxAffected if Version is below 74.0 (for example, 73.x or earlier)
-
Check installed Firefox ESR versionRun 'firefox --version' and verify ESR status via 'firefox -v' output which typically shows 'Mozilla Firefox ESR' in the version stringAffected if Version is below 68.6.0 and is the ESR release
-
Check installed Thunderbird versionRun 'thunderbird --version' or 'thunderbird -v' in terminal, or navigate to Thunderbird menu > Help > About ThunderbirdAffected if Version is below 68.6.0
-
Check Ubuntu system Mozilla package versionsRun 'dpkg -l | grep -i firefox' or 'apt list --installed | grep -i firefox' on Ubuntu systems to list installed Mozilla package versionsAffected if Ubuntu 16.04, 18.04, or 19.10 has Firefox packages installed (these releases shipped with vulnerable Firefox versions)
A user is affected if Firefox (including ESR) is below version 74.0, Thunderbird is below 68.6.0, or the system runs Ubuntu 16.04/18.04/19.10 with bundled Firefox packages.
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 · scoped68.6.074.0
Upgrade affected installations to Thunderbird 68.6+, Firefox 74+, or Firefox ESR 68.6+ to receive the patched versions containing the memory safety fixes.
Firefox 74.0+, Firefox ESR 68.6.0+, Thunderbird 68.6.0+
- Back up any critical data (bookmarks, emails, passwords) before upgrading
- Update Firefox to version 74.0 or later: On Windows/macOS, use Help > About Firefox > Check for Updates, or download from https://www.mozilla.org/firefox/
- Update Thunderbird to version 68.6.0 or later: Use Help > About Thunderbird > Check for Updates, or download from https://www.thunderbird.net/
- For Ubuntu Linux systems, run: sudo apt update && sudo apt upgrade (or sudo apt full-upgrade) to receive security updates for Firefox/Thunderbird from Ubuntu repositories
- For Ubuntu 16.04 (EOL), enable ESM (Extended Security Maintenance) if still receiving updates, or upgrade to a newer Ubuntu LTS version
- Verify the updated version by checking: Firefox: Navigate to about:support, Thunderbird: Help > About Thunderbird
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.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 $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-6814 — 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 sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2020-6814 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