CVE-2018-18500
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 · uneditedA use-after-free vulnerability can occur while parsing an HTML5 stream in concert with custom HTML elements. This results in the stream parser object being freed while still in use, leading to a potentially exploitable crash. This vulnerability affects Thunderbird < 60.5, Firefox ESR < 60.5, and Firefox < 65.
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 confidenceA use-after-free vulnerability in the HTML5 stream parser of Firefox and Thunderbird allows memory corruption when parsing HTML5 streams with custom HTML elements. The stream parser object is freed while still in use, leading to potential code execution.
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< 65.0< 60.5= 14.04= 16.04= 18.04= 18.10= 8.0= 9.0= 6.0= 7.0= 6.0= 7.0= 7.6= 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.
-
Identify installed Firefox versionRun 'firefox --version' or check package manager: 'dpkg -l | grep firefox' on Debian/Ubuntu, 'rpm -qa | grep -i firefox' on RHELAffected if Version is below 65.0 (e.g., 64.x or earlier)
-
Identify installed Firefox ESR versionRun 'firefox --version' or check package manager for ESR variant: 'rpm -qa | grep firefox-esr' on RHELAffected if Version is below 60.5 (e.g., 60.4.x or earlier)
-
Identify installed Thunderbird versionRun 'thunderbird --version' or check package manager: 'dpkg -l | grep thunderbird' on Debian/Ubuntu, 'rpm -qa | grep thunderbird' on RHELAffected if Version is below 60.5 (e.g., 60.4.x or earlier)
-
Check if HTML5 stream parsing is in useInspect browser activity or check for web content using HTML5 streams with custom HTML elements. This is typically triggered when processing HTML5 media streams or custom element definitions in web content.Affected if User processes HTML5 streams with custom HTML elements in the affected browser application
A user is affected if they run Firefox below 65.0, Firefox ESR below 60.5, or Thunderbird below 60.5, AND actively use HTML5 stream parsing with custom HTML elements in web content.
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 · scoped60.565.0
Upgrade to Thunderbird 60.5+, Firefox ESR 60.5+, or Firefox 65+ to patch the vulnerability. No workarounds exist; software update is required.
Firefox 65.0+ / Firefox ESR 60.5+ / Thunderbird 60.5+
- Identify the installed Firefox, Firefox ESR, or Thunderbird version by checking About menu or running: firefox --version, thunderbird --version
- For Firefox: Upgrade to version 65.0 or later
- For Firefox ESR: Upgrade to version 60.5 or later
- For Thunderbird: Upgrade to version 60.5 or later
- On Linux systems (Ubuntu, Debian, Enterprise Linux): Run system package manager update (e.g., sudo apt-get update && sudo apt-get upgrade for Debian/Ubuntu, or sudo yum update for RHEL/CentOS)
- Restart the application after update completes
- Verify the installed version is at or above the fixed release
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation6.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-18500 — 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- 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
- usn.ubuntu.com
- usn.ubuntu.com
- www.debian.org
- www.debian.org
- lists.opensuse.org
- security.gentoo.org
- nvd.nist.gov
Practitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2018-18500 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