CVE-2024-10474
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 · uneditedFocus was incorrectly allowing internal links to utilize the app scheme used for deeplinking, which could result in links potentially circumventing some URL safety checks This vulnerability affects Focus for iOS < 132.
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 confidenceThe Focus iOS app incorrectly allowed internal links to use the app's custom URL scheme (used for deeplinking), which could bypass certain URL safety checks. This scheme misuse in internal links represents a URL validation bypass vulnerability.
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< 132.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.
-
Find the installed Firefox Focus version on iOSOpen the iOS Settings app, scroll down to locate Firefox Focus in the app list, and tap on it to view the version number. Alternatively, open the App Store app, search for Firefox Focus, and view the version displayed in the app listing.Affected if The displayed version number is lower than 132.0 or shows a version without the decimal (such as 131.x or earlier).
-
Confirm the app is the genuine Firefox FocusVerify that the app name in the Settings or App Store listing reads exactly as 'Firefox Focus' (not a clone or alternative browser) and is published by 'Mozilla Corporation' or 'Mozilla'.Affected if The app is an imitation or unauthorized version claiming to be Firefox Focus.
-
Check for pending iOS app updatesOpen the App Store app, tap your profile icon at the top right, scroll to see available updates, and check if Firefox Focus appears with an Update button indicating a newer version is available.Affected if An update for Firefox Focus is listed, suggesting the installed version is outdated.
You are affected if Firefox Focus for iOS is installed at a version below 132.0, as versions prior to 132 contain the URL scheme validation bypass in internal links.
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 · scoped132.0
Update Focus for iOS to version 132 or later to obtain the patched version that properly validates and restricts the app scheme usage in internal links.
Firefox Focus for iOS 132.0
- Open the App Store on your iOS device
- Search for "Firefox Focus" in the App Store
- Tap the "Update" button next to Firefox Focus to update to version 132.0 or later
- Alternatively, enable automatic app updates in iOS Settings > App Store > Automatic Downloads to ensure future updates are applied
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation12.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,808.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-10474 — 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-10474 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