CVE-2024-9393
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://pdf.js` origin. This could allow them to access cross-origin PDF 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 confidenceCross-origin data leak vulnerability in PDF.js where specially crafted multipart responses allow arbitrary JavaScript execution under the resource://pdf.js origin, enabling access to cross-origin PDF content. Android clients lack Site Isolation protections present in desktop builds, allowing 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 desktop, look in Applications or program files. On Android, check installed apps in Settings > Apps.Affected if The product is Mozilla Firefox or Thunderbird and the version falls within the affected ranges listed below.
-
Check Firefox version numberIn Firefox, navigate to about:support or go to Menu > Help > About Firefox. The version is displayed on that page.Affected if Firefox version is below 131.0, OR between 116.0 and 128.3.0 (including 128.2.x), OR below 115.16.0 for ESR tracks.
-
Check Thunderbird version numberIn Thunderbird, go to Menu > Help > About Thunderbird. The version is displayed on that page.Affected if Thunderbird version is below 128.3.0, or exactly 129.0.
-
Verify PDF.js is in usePDF.js is the built-in PDF viewer. Open any PDF file in the browser or mail client, or attempt to view a PDF attachment in Thunderbird. Check if it loads using the internal PDF viewer.Affected if PDF.js processes the PDF file and the browser uses the resource://pdf.js origin.
-
Check platform on AndroidOn Android, verify the OS version in Settings > About Phone > Android version. Desktop builds have Site Isolation; Android builds do not.Affected if Running Firefox on Android and viewing cross-origin PDF content allows the full exploit.
A user is affected if they run Firefox < 131.0, Firefox ESR < 115.16.0 or 116.0-128.3.0, or Thunderbird < 128.3 or exactly 129.0, and view PDF files using the built-in PDF.js viewer, with Android being particularly vulnerable due to missing Site Isolation.
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
Update affected products to patched versions: Firefox 131+, Firefox ESR 115.16+, Firefox ESR 128.3+, or Thunderbird 128.3+/131+ depending on release track.
Firefox 131.0+ | Firefox ESR 115.16.0+ / 128.3.0+ | Thunderbird 128.3.0+ / 131.0+
- 1. Identify the installed Firefox, Firefox ESR, or Thunderbird version by navigating to Menu > Help > About (or typing 'about:support' in the address bar)
- 2. For Firefox users: Upgrade to version 131.0 or later by visiting https://www.mozilla.org/firefox/ and downloading the latest release
- 3. For Firefox ESR users: If on ESR 115.x branch, upgrade to 115.16.0 or later; if on ESR 128.x branch, upgrade to 128.3.0 or later
- 4. For Thunderbird users: Upgrade to version 128.3.0 or later, or 131.0 or later
- 5. After upgrade, restart the application to complete the update
- 6. Verify the fix by checking Menu > Help > About to confirm the version number matches a fixed release
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.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 $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-9393 — 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-9393 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