Firefox FocusWeb browser · Mozilla
CVE-2024-1563
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 · uneditedAn attacker could have executed unauthorized scripts on top origin sites using a JavaScript URI when opening an external URL with a custom Firefox scheme and a timeout race condition. This vulnerability affects Focus for iOS < 122.
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 race condition in Focus for iOS allows execution of JavaScript URIs through custom Firefox schemes when opening external URLs, enabling unauthorized script execution on top origin sites.
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 FocusWeb browser
< 122.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
- High
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H
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.
-
Confirm Firefox Focus for iOS is installedLocate the Firefox Focus app on the iOS device by checking the home screen, app library, or searching for 'Focus' in the iOS search functionAffected if The Firefox Focus app is present on the device
-
Determine the installed version of Firefox Focus for iOSOpen the iOS Settings app, go to General > Apps > Firefox Focus (or find Firefox Focus in the app list), and note the version number displayedAffected if A version number is visible in the app info
-
Compare version against affected rangeCompare the installed version number to the affected range: any version below 122.0 is vulnerable (for example, 121.5, 121.0, 120.3, etc.)Affected if The installed version is less than 122.0 (for example, 121.x, 120.x, or any earlier version)
-
Check for updates via App StoreOpen the App Store, search for Firefox Focus, and check if an update is available. The App Store will show the latest version as 122.0 or later if patchedAffected if The App Store indicates version 122.0 or later is available but the installed version remains below 122.0
The environment is affected if Firefox Focus for iOS is installed and its installed version is below 122.0, as the race condition allowing JavaScript URI execution exists in all earlier versions.
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 · scoped122.0
Upgrade to Focus for iOS version 122 or later, which contains the fix for proper validation and blocking of JavaScript URI execution in the custom scheme handler.
Firefox Focus for iOS 122.0
- Open the App Store on your iOS device
- Search for Firefox Focus or navigate to your installed apps
- Update Firefox Focus to version 122.0 or later
- Verify the update was successful by checking the app version in Settings > Firefox Focus > Version
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Firefox Focus
Scoped from the published advisory
- Consultation4.0 h
- Implementation8.0 h
- Testing6.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 $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-1563 — 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-1563 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