CVE-2024-0747
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 · uneditedWhen a parent page loaded a child in an iframe with `unsafe-inline`, the parent Content Security Policy could have overridden the child Content Security Policy. This vulnerability affects Firefox < 122, Firefox ESR < 115.7, and Thunderbird < 115.7.
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 confidenceWhen a parent page loads a child in an iframe with the `unsafe-inline` directive, the parent's Content Security Policy incorrectly overrides the child's CSP, breaking the security isolation between the parent and child contexts and allowing potential script injection attacks.
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< 122.0< 115.7= 10.0< 115.7CVSS 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
- None
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/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.
-
Check installed Firefox versionNavigate to Firefox menu > Help > About Firefox, or enter 'about:support' in the address bar, to view the installed version numberAffected if Version is below 122.0 (e.g., 121.x, 120.x, etc.)
-
Check installed Firefox ESR versionNavigate to Firefox ESR menu > Help > About Firefox ESR, or enter 'about:support' in the address bar, to view the installed ESR version numberAffected if Version is below 115.7 (e.g., 115.6, 115.0, etc.)
-
Check installed Thunderbird versionNavigate to Thunderbird menu > Help > About Thunderbird, or enter 'about:support' in the address bar, to view the installed version numberAffected if Version is below 115.7 (e.g., 115.6, 115.0, etc.)
-
Identify iframe usage with CSP unsafe-inlineReview web application code or browser console for pages that load iframes while setting Content-Security-Policy headers that include the 'unsafe-inline' directiveAffected if Parent pages load iframe content AND apply CSP headers containing 'unsafe-inline' directive
You are affected if running Firefox < 122.0, Firefox ESR < 115.7, or Thunderbird < 115.7 AND your application loads iframes while enforcing a CSP with the unsafe-inline directive.
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.7122.0
Update affected browsers to Firefox 122+, Firefox ESR 115.7+, or Thunderbird 115.7+ to apply the vendor patch.
Firefox 122.0 (or Firefox ESR 115.7), Thunderbird 115.7
- Check current Firefox version by navigating to about:firefox or running 'firefox --version'
- Check current Thunderbird version by navigating to about:thunderbird or running 'thunderbird --version'
- For Firefox: Update to version 122.0 or later via the application's built-in update mechanism (Help > About Firefox > Check for Updates)
- For Firefox ESR: Update to version 115.7 or later
- For Thunderbird: Update to version 115.7 or later
- Restart the application after updating
- Verify the update was successful by checking the version again
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-0747 — 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-0747 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