FirefoxWeb browser · Mozilla
CVE-2024-10004
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 · uneditedOpening an external link to an HTTP website when Firefox iOS was previously closed and had an HTTPS tab open could in some cases result in the padlock icon showing an HTTPS indicator incorrectly This vulnerability affects Firefox for iOS < 131.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 confidenceA UI state persistence bug in Firefox iOS causes the HTTPS padlock icon to incorrectly display when opening external HTTP links, if the app was previously closed with an HTTPS tab open. This creates a mixed-content security indicator that could deceive users into believing their connection is secure when it is actually over plaintext HTTP.
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
< 131.2.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
- High
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/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 Firefox iOS versionOpen the App Store, go to your profile, find Firefox iOS in purchased apps, or open Firefox iOS and navigate to Settings > Firefox > About Firefox to see the version numberAffected if Version is lower than 131.2.0 (e.g., 131.1.x, 131.0.x, or any earlier version)
-
Identify HTTPS tab state before closeBefore closing Firefox iOS, verify you have at least one tab open that displays the HTTPS padlock (a secure HTTPS website)Affected if You close the app with an HTTPS tab as the active or most recent tab
-
Reproduce the UI state persistenceForce-close Firefox iOS completely (swipe up from app switcher), then reopen the app and tap an external link that uses HTTP (not HTTPS) - observe whether the padlock icon incorrectly appears in the address barAffected if The padlock icon appears despite the external link being over plaintext HTTP (URL starts with http:// not https://)
You are affected if Firefox iOS version is below 131.2.0 AND you can reproduce the incorrect HTTPS padlock display when opening HTTP links after app restart with a previously open HTTPS tab.
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 · scoped131.2.0
Update Firefox for iOS to version 131.2 or later to obtain the fix; users should verify the padlock behavior when opening HTTP links after app restart.
Firefox for iOS 131.2.0
- Open the App Store on your iOS device
- Search for "Firefox" or navigate to your updates section
- Update Firefox for iOS to version 131.2.0 or later
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Firefox
Scoped from the published advisory
- Consultation1.0 h
- Implementation1.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 $1,376.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-10004 — 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-10004 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