FirefoxWeb browser · Mozilla
CVE-2018-12361
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 · uneditedAn integer overflow can occur in the SwizzleData code while calculating buffer sizes. The overflowed value is used for subsequent graphics computations when their inputs are not sanitized which results in a potentially exploitable crash. This vulnerability affects Thunderbird < 60, Firefox ESR < 60.1, and Firefox < 61.
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 confidenceAn integer overflow vulnerability exists in the SwizzleData component of Firefox and Thunderbird. The overflow occurs when calculating buffer sizes, and the resulting overflowed value is subsequently used in graphics computations without proper input sanitization, leading to a potentially exploitable crash.
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
< 61.0
Firefox EsrWeb browser
< 60.1
Debian LinuxOperating system
= 8.0= 9.0
Ubuntu LinuxOperating system
= 14.04= 16.04= 17.10= 18.04< 60.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
- 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 checksWork through these to decide whether this CVE applies to you.
-
Identify installed Mozilla productOpen terminal and run: firefox --version OR thunderbird --version. Alternatively, check via package manager: dpkg -l | grep -i firefox OR dpkg -l | grep -i thunderbirdAffected if The product is Firefox or Thunderbird
-
Check Firefox versionRun: firefox --version. For Debian/Ubuntu, also check: apt-cache policy firefoxAffected if Version is less than 61.0 (standard) or less than 60.1 (ESR)
-
Check Thunderbird versionRun: thunderbird --version. For Debian/Ubuntu, also check: apt-cache policy thunderbirdAffected if Version is less than 60.0
-
Check OS-specific package versionsOn Debian: dpkg -l | grep -E 'firefox|thunderbird'. On Ubuntu: apt list --installed | grep -E 'firefox|thunderbird'Affected if Running Debian 8.0 or 9.0, or Ubuntu 14.04, 16.04, 17.10, or 18.04 with unpatched Mozilla packages
You are affected if you are running any version of Firefox below 61.0 (or below 60.1 ESR), or Thunderbird below 60.0, particularly on Debian 8.0/9.0 or Ubuntu 14.04/16.04/17.10/18.04.
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.
From vendor data60.060.161.0
Update affected products to non-vulnerable versions: Firefox >= 61, Firefox ESR >= 60.1, or Thunderbird >= 60.
Fix this in Firefox
Scoped from the published advisory
- Consultation1.0 h
- Implementation2.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,664.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-12361 — 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-2018-12361 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