FirefoxWeb browser · Mozilla
CVE-2023-23600
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 · uneditedPer origin notification permissions were being stored in a way that didn't take into account what browsing context the permission was granted in. This lead to the possibility of notifications to be displayed during different browsing sessions. *This bug only affects Firefox for Android. Other operating systems are unaffected.* This vulnerability affects Firefox < 109.
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 · moderate confidenceA permission storage vulnerability in Firefox for Android (< 109) allowed notification permissions to be incorrectly associated with origins regardless of the browsing context in which they were granted. This caused authorized notifications to be displayed in unintended browsing sessions.
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
FirefoxWeb browser
< 109.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
- 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 Firefox for Android versionOpen the Firefox for Android app, tap the three-dot menu, select Settings, then scroll down and tap About Firefox. The version number is displayed on that screen.Affected if The displayed version is below 109.0 (for example, 108.x or earlier)
-
Confirm notification permissions are in useIn Firefox for Android, go to Settings > Privacy & Security > Permissions > Notifications. Review the list of websites that have been granted notification permissions.Affected if Any websites have been granted notification permission while using a vulnerable version of Firefox for Android
-
Verify browsing context isolation concernThis check is informational: if you use multiple tabs or contexts (such as Private Browsing) and have granted notification permissions, those permissions may have been incorrectly associated across different browsing contexts in versions below 109.Affected if You have used multiple browsing contexts (tabs, Private Browsing) simultaneously while having granted notification permissions on a vulnerable version
You are affected if Firefox for Android version is below 109.0 and you have granted notification permissions to any websites while using that version.
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 · scoped109.0
Upgrade Firefox for Android to version 109 or later on all affected devices.
Firefox 109.0 or later
- Open Firefox for Android
- Tap the menu button (three dots)
- Select Settings
- Scroll to Firefox Updates under the Firefox section
- Tap Check for updates or navigate to the Mozilla Firefox website to download version 109.0 or later
- Download and install Firefox 109.0 or later
- Restart the browser after installation
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Firefox
Scoped from the published advisory
- Consultation2.0 h
- Implementation3.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,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-23600 — 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-23600 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