CVE-2020-15683
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 and community members reported memory safety bugs present in Firefox 81 and Firefox ESR 78.3. 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 Firefox ESR < 78.4, Firefox < 82, and Thunderbird < 78.4.
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 81 and Firefox ESR 78.3 allowed memory corruption that could potentially be exploited for arbitrary code execution. The vulnerability affected multiple Mozilla products including Firefox, Firefox ESR, and Thunderbird.
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< 82.0< 78.4= 9.0= 10.0< 78.4= 15.1= 15.2CVSS 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 Firefox version (Windows/Mac/Linux GUI)Open Firefox, navigate to Help > About Firefox, or type 'about:firefox' in the address bar. The version number is displayed next to the Firefox logo.Affected if Version shown is less than 82.0 (for example 81.0, 80.x, etc.)
-
Check Firefox ESR version (Windows/Mac/Linux)Open Firefox ESR, navigate to Help > About Firefox ESR, or type 'about:firefox' in the address bar. Look for the ESR designation in the version string.Affected if Version shown is less than 78.4 (for example 78.3, 78.2, etc.)
-
Check Thunderbird versionOpen Thunderbird, navigate to Help > About Thunderbird, or type 'about:thunderbird' in the address bar.Affected if Version shown is less than 78.4 (for example 78.3, 78.2, etc.)
-
Check installed package version on Linux (Debian/Ubuntu)Open terminal and run: dpkg -l | grep -E 'firefox|thunderbird' (Debian) or rpm -qa | grep -E 'firefox|thunderbird' (RPM-based).Affected if Package version listed is lower than 78.4 for ESR/Thunderbird or lower than 82.0 for standard Firefox.
A user is affected if their installed Firefox, Firefox ESR, or Thunderbird version is below 82.0, 78.4, or 78.4 respectively, as these contain the memory safety bug fixes.
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 · scoped78.482.0
Upgrade to Firefox ESR 78.4+, Firefox 82+, or Thunderbird 78.4+ to obtain the patched versions containing the memory safety fixes.
Firefox 82.0+, Firefox ESR 78.4+, Thunderbird 78.4+
- Identify which Mozilla product is in use (Firefox, Firefox ESR, or Thunderbird)
- Check the currently installed version of the product
- If using Firefox < 82.0, upgrade to Firefox 82.0 or later
- If using Firefox ESR < 78.4, upgrade to Firefox ESR 78.4 or later
- If using Thunderbird < 78.4, upgrade to Thunderbird 78.4 or later
- For Debian systems, apply vendor security updates: run 'apt update && apt upgrade' or 'apt-get update && apt-get upgrade' to receive the patched Mozilla packages
- Restart the browser/application after upgrading
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation1.0 h
- Implementation1.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 $1,376.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-15683 — 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-15683 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