CVE-2024-9394
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 attacker could, via a specially crafted multipart response, execute arbitrary JavaScript under the `resource://devtools` origin. This could allow them to access cross-origin JSON content. This access is limited to "same site" documents by the Site Isolation feature on desktop clients, but full cross-origin access is possible on Android versions. This vulnerability affects Firefox < 131, Firefox ESR < 128.3, Firefox ESR < 115.16, Thunderbird < 128.3, and Thunderbird < 131.
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 confidenceThis is a cross-site scripting (XSS) vulnerability in Firefox and Thunderbird where a specially crafted multipart response allows arbitrary JavaScript execution under the `resource://devtools` origin, enabling access to cross-origin JSON content. While desktop clients are partially protected by Site Isolation (limited to same-site documents), Android versions allow full cross-origin access.
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< 131.0< 115.16.0>= 116.0, < 128.3.0< 128.3= 129.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
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
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 the installed productCheck if Mozilla Firefox or Thunderbird is installed on the system. In Firefox, navigate to 'about:support' or go to Help > About Firefox. In Thunderbird, go to Help > About Thunderbird.Affected if The product is Firefox or Thunderbird
-
Determine the Firefox versionIn Firefox, type 'about:support' in the address bar or go to Help > About Firefox. Note the version number displayed (e.g., 130.0.3, 115.15.0, 128.2.0).Affected if Firefox version is less than 131.0, or is between 116.0 and 128.2.x inclusive, or is less than 115.16.0 for ESR branches
-
Determine the Thunderbird versionIn Thunderbird, go to Help > About Thunderbird. Note the version number displayed (e.g., 128.2.0, 129.0).Affected if Thunderbird version is less than 128.3 or equals 129.0 exactly
-
Check if this is Firefox for AndroidOn Android devices, verify the Firefox installation by checking the app version in the Google Play Store or device Settings > Apps > Firefox. Android versions have full cross-origin access exploitation capability.Affected if The affected Firefox version is running on Android, which allows full cross-origin access rather than limited same-site access
-
Confirm devtools accessibilityThe vulnerability requires the resource://devtools origin to be accessible. In Firefox, verify if DevTools have been used or if the browser profile has devtools enabled by default. No additional configuration check is needed as this is enabled by default in affected versions.Affected if DevTools are accessible in the browser (enabled by default in all standard installations)
A user is affected if they are running any Firefox version below 131.0, Firefox ESR below 115.16.0 or between 116.0 and 128.2.x, or Thunderbird below 128.3 or exactly 129.0, with the Android platform being the most severely impacted.
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.16.0128.3128.3.0
Upgrade Firefox to version 131 or later, Firefox ESR to 128.3+/115.16+, and Thunderbird to 128.3+/131+ to remediate this vulnerability.
Firefox 131.0+ | Firefox ESR 128.3.0+ (or 115.16.0+) | Thunderbird 128.3+
- Upgrade Firefox to version 131.0 or later
- Upgrade Firefox ESR 128.x to version 128.3.0 or later
- Upgrade Firefox ESR 115.x to version 115.16.0 or later
- Upgrade Thunderbird to version 128.3 or later (or 131.0 for Thunderbird 129.x users)
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation1.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,200.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-9394 — 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-9394 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