CVE-2023-4580
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 · uneditedPush notifications stored on disk in private browsing mode were not being encrypted potentially allowing the leak of sensitive information. This vulnerability affects Firefox < 117, Firefox ESR < 115.2, and Thunderbird < 115.2.
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 confidencePush notifications stored on disk during private browsing mode were not encrypted, potentially exposing sensitive information contained in those notifications.
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< 117.0< 115.2< 115.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
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/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.
-
Check installed Firefox versionOpen Firefox, go to Menu > Help > About Firefox (or navigate to about:support). Record the version number displayed.Affected if Version is below 117.0 (for regular Firefox) or below 115.2 (for Firefox ESR)
-
Check installed Thunderbird versionOpen Thunderbird, go to Menu > Help > About Thunderbird. Record the version number displayed.Affected if Version is below 115.2
-
Locate private browsing profile directoryNavigate to the profile folder (about:profiles in Firefox, or check profile manager in Thunderbird). Identify profiles that have been used in Private Browsing mode.Affected if A private browsing profile exists and the application version is vulnerable
-
Examine push notification storageIn the private browsing profile folder, look for files in the push notification directory (typically under storage/default or notifications folder). Check if these files are encrypted or stored in plain text.Affected if Push notification files exist and are stored unencrypted (plain text JSON or readable content)
-
Verify encryption statusOpen any found notification files in a text editor. If the content is readable (not garbled/encrypted), the notifications are unencrypted.Affected if Notification content is readable plain text rather than encrypted binary data
User is affected if running Firefox < 117.0 (or ESR < 115.2) or Thunderbird < 115.2, AND has used private browsing mode with push notifications enabled, with those notifications stored unencrypted on disk.
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.2117.0
Upgrade to Firefox 117, Firefox ESR 115.2, Thunderbird 115.2 or later to ensure push notifications are properly encrypted in private browsing mode.
Firefox 117.0+ | Firefox ESR 115.2+ | Thunderbird 115.2+ (depending on product in use)
- Check the current version of Mozilla product (Firefox, Firefox ESR, or Thunderbird) by navigating to Help > About in the application menu
- If using Firefox: upgrade to version 117.0 or later
- If using Firefox ESR: upgrade to version 115.2 or later
- If using Thunderbird: upgrade to version 115.2 or later
- Restart the application after upgrade
- Verify the installed version matches or exceeds the fixed release
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation1.0 h
- Implementation1.0 h
- Testing1.0 h
- Review / QA0.5 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-2023-4580 — 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-2023-4580 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