CVE-2024-8382
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 · uneditedInternal browser event interfaces were exposed to web content when privileged EventHandler listener callbacks ran for those events. Web content that tried to use those interfaces would not be able to use them with elevated privileges, but their presence would indicate certain browser features had been used, such as when a user opened the Dev Tools console. This vulnerability affects Firefox < 130, Firefox ESR < 128.2, Firefox ESR < 115.15, Thunderbird < 128.2, and Thunderbird < 115.15.
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 vulnerability in Firefox and Thunderbird allowed internal browser event handler interfaces to be exposed to web content when privileged EventHandler listener callbacks executed. This exposure enables web content to detect when users have activated privileged browser features like the DevTools console, representing an information disclosure vulnerability but without granting elevated privileges to the web content.
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< 130.0< 115.15>= 128.0, < 128.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
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/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.
-
Confirm Firefox or Thunderbird is installedCheck for the presence of Firefox or Thunderbird executables or application files on the system. On Windows, look in Program Files. On macOS, check /Applications. On Linux, check common paths like /usr/bin/firefox or use package manager queries.Affected if Either Firefox or Thunderbird is present on the system
-
Identify installed Firefox versionFor Firefox, navigate to Help > About Firefox, or check the application file properties, or run: firefox --version (Linux) or inspect application metadata files.Affected if The version number is less than 130.0 for standard Firefox, or falls between 128.0 (inclusive) and 128.2 (exclusive)
-
Identify installed Firefox ESR versionFor Firefox ESR, check Help > About Firefox or inspect application metadata. ESR versions are typically labeled as such in the application information.Affected if The version is less than 115.15 for ESR branches below 128, or between 128.0 (inclusive) and 128.2 (exclusive) for ESR 128.x
-
Identify installed Thunderbird versionFor Thunderbird, navigate to Help > About Thunderbird, or check application file properties, or run: thunderbird --version (Linux).Affected if The version is less than 115.15 or falls between 128.0 (inclusive) and 128.2 (exclusive)
-
Understand the exposure mechanismThis vulnerability is inherent to the browser code itself when handling EventHandler callbacks. There is no specific configuration file or toggle to check. The exposure manifests when web content can detect internal browser event interfaces during sensitive feature activation like DevTools.Affected if The browser version falls within any of the affected ranges listed above
A user is affected if they have any version of Firefox below 130.0, Firefox ESR below 115.15 or between 128.0 and 128.2, or Thunderbird below 115.15 or between 128.0 and 128.2.
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 · scoped115.15128.2130.0
Update affected installations to Firefox 130, Firefox ESR 128.2/115.15, or Thunderbird 128.2/115.15 as appropriate for the product in use.
Firefox 130.0 / Firefox ESR 115.15 / Firefox ESR 128.2 (depending on branch)
- 1. Identify which Firefox product and version is currently installed (Firefox, Firefox ESR, or Thunderbird)
- 2. For Firefox users: Upgrade to Firefox 130.0 or later
- 3. For Firefox ESR 115.x users: Upgrade to Firefox ESR 115.15 or later
- 4. For Firefox ESR 128.x users: Upgrade to Firefox ESR 128.2 or later
- 5. For Thunderbird users: Upgrade to Thunderbird 128.2 or later or Thunderbird 115.15 or later (matching the same ESR branch pattern)
- 6. Restart the browser application after upgrading to ensure all components are updated
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation1.0 h
- Implementation2.0 h
- Testing1.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,424.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-8382 — 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-2024-8382 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