CVE-2018-18500 is a use-after-free vulnerability in Mozilla's HTML5 stream parser, triggered when parsing HTML5 streams in conjunction with custom HTML elements. The vulnerability arises when the stream parser object is freed while it is still in use, which can lead to a potentially exploitable crash. This issue affects Thunderbird versions prior to 60.5, Firefox ESR versions prior to 60.5, and Firefox versions prior to 65.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
1 valid exploit after Mallory filtered fakes, detection scripts, and README-only repos.
This repository is a proof-of-concept (PoC) exploit for CVE-2018-18500, a use-after-free vulnerability in Mozilla Firefox. The repository contains three files: a README with a brief description and reference, 'customelements_poc.html' (the main exploit file), and 'delay_http_server.py' (a simple Python HTTP server). The exploit works by serving the HTML file via the local HTTP server, which the user then opens in a vulnerable version of Firefox. The HTML/JavaScript code manipulates FormData, FileReader, and custom elements to trigger a use-after-free condition, using a delayed XML response to help with timing. The PoC demonstrates memory corruption but does not include a shell or code execution payload. The endpoints involved are 'http://127.0.0.1/customelements_poc.html' (the exploit) and 'http://127.0.0.1/delay.xml' (used for timing). The attack vector is browser-based, requiring user interaction (opening the exploit HTML in Firefox).
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
1 sources tracked across advisories and community write-ups. News coverage will land here when it surfaces.
No news coverage yet. Advisories and community discussion only.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.