CVE-2018-5188
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 · uneditedMemory safety bugs present in Firefox 60, Firefox ESR 60, and Firefox ESR 52.8. Some of these bugs showed evidence of memory corruption and we presume that with enough effort that some of these could be exploited to run arbitrary code. This vulnerability affects Thunderbird < 60, Thunderbird < 52.9, Firefox ESR < 60.1, Firefox ESR < 52.9, 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 · high confidenceMemory safety bugs in Firefox/Thunderbird where some showed evidence of memory corruption; with sufficient effort, some could be exploited for arbitrary code execution. This is a class of memory corruption vulnerability in the browser engine.
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= 8.0= 9.0= 14.04= 16.04= 17.10= 18.04< 61.0>= 53.0, < 60.1.0< 52.9= 6.0= 7.0= 6.0= 7.0= 7.6= 7.5= 7.6CVSS 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.0/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 versionRun 'firefox --version' or look in Help > About FirefoxAffected if Version is 53.0 or higher but below 60.1.0, or below 61.0 (for versions 53.0-60.0 range)
-
Check Thunderbird versionRun 'thunderbird --version' or look in Help > About ThunderbirdAffected if Version is 52.x but below 52.9, or 60.x but below 60.0 (verify against Mozilla's version matrix)
-
Check OS-packaged Firefox on Debian/UbuntuRun 'dpkg -l | grep firefox' or check package manager for installed firefox versionAffected if Debian 8.x/9.x or Ubuntu 14.04/16.04/17.10/18.04 with firefox package installed at vulnerable version
-
Check OS-packaged Firefox on RHEL/CentOSRun 'rpm -qa | grep firefox' to list installed Firefox packagesAffected if RHEL 6.0, 7.0, 7.5, or 7.6 with Firefox installed at vulnerable version
You are affected if Firefox or Thunderbird is installed and its version falls within 53.0 to 60.0.x (non-ESR) or below 52.9 (ESR), matching the affected OS versions for Linux distributions.
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 · scoped52.960.1.061.0
Update affected software to Firefox 61+, Firefox ESR 60.1+/52.9+, Thunderbird 60+/52.9+ to obtain patched versions.
Firefox 61.0, Firefox 60.1.0, Firefox ESR 60.1, Firefox ESR 52.9, Thunderbird 60, Thunderbird 52.9
- Update the package repository index: sudo apt-get update (Debian/Ubuntu) or sudo yum check-update (RHEL/CentOS)
- Upgrade Firefox to version 61.0 or higher, or to version 60.1.0 or higher if staying on the 60.x branch
- Upgrade Firefox ESR to version 60.1 or higher, or to version 52.9 or higher if staying on the 52.x branch
- Upgrade Thunderbird to version 60 or higher, or to version 52.9 or higher if staying on the 52.x branch
- For Enterprise Linux systems, apply the errata updates via yum update or via the Red Hat Satellite/管理的更新机制
- Verify the installed version matches the fixed release: firefox --version or thunderbird --version
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-2018-5188 — 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 sources- bugzilla.mozilla.org
- www.mozilla.org
- www.mozilla.org
- www.mozilla.org
- www.mozilla.org
- www.mozilla.org
- www.securityfocus.com
- access.redhat.com
- access.redhat.com
- access.redhat.com
- access.redhat.com
- lists.debian.org
- lists.debian.org
- security.gentoo.org
- security.gentoo.org
- usn.ubuntu.com
- usn.ubuntu.com
- usn.ubuntu.com
- www.debian.org
- nvd.nist.gov
Practitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2018-5188 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