Firefox MobileWeb browser · Mozilla
CVE-2024-38312
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 browsing private tabs, some data related to location history or webpage thumbnails could be persisted incorrectly within the sandboxed app bundle after app termination This vulnerability affects Firefox for iOS < 127.
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 confidenceIn Firefox for iOS before version 127, private browsing data including location history and webpage thumbnails are incorrectly persisted within the sandboxed app bundle after app termination instead of being properly discarded, potentially exposing private browsing activity.
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
Firefox MobileWeb browser
< 127.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
- 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.
-
Verify Firefox for iOS is installedLocate the Firefox app icon on your iOS device home screen or check in Settings > General > iPhone Storage to confirm Firefox is installedAffected if Firefox for iOS is present on the device
-
Check installed Firefox for iOS versionOpen the App Store, go to your profile, find Firefox for iOS in purchased apps, and note the version number shown, or open Firefox, tap the menu, go to Settings, and scroll to the bottom to see the versionAffected if The installed version is anything less than 127.0 (for example, 126.0, 125.5, etc.)
-
Determine if private browsing was usedRecall whether you have used Firefox for iOS Private Browsing mode (tabs with a purple mask icon) on this deviceAffected if You have used private browsing mode on an affected version (below 127.0)
You are affected if Firefox for iOS version 126.x or lower is installed and you have used private browsing mode, as private browsing data may have been incorrectly persisted in the app bundle.
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 · scoped127.0
Update Firefox for iOS to version 127 or later to ensure private browsing data is not persisted.
Firefox for iOS 127
- Open the App Store on the iOS device
- Search for Firefox for iOS
- Tap Update to upgrade to version 127 or later
- After updating, verify the version number in Settings > Firefox > Version
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Firefox Mobile
Scoped from the published advisory
- 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-38312 — 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-38312 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