Firefox FocusWeb browser · Mozilla
CVE-2024-0605
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 · uneditedUsing a javascript: URI with a setTimeout race condition, an attacker can execute unauthorized scripts on top origin sites in urlbar. This bypasses security measures, potentially leading to arbitrary code execution or unauthorized actions within the user's loaded webpage. 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 · moderate confidenceThis is a client-side Cross-Site Scripting (XSS) vulnerability in Focus for iOS (versions prior to 122). The flaw combines abuse of the javascript: URI scheme with a race condition involving setTimeout, allowing an attacker to execute arbitrary JavaScript in the context of the top-level origin displayed in the urlbar. This bypasses same-origin security protections, enabling unauthorized actions or code execution within the user's loaded webpage.
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
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:H/PR:N/UI:R/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.
-
Identify Firefox Focus for iOS installationCheck the iOS device for the Firefox Focus browser app in the installed applications list or App LibraryAffected if The app is not installed on the device (not affected)
-
Retrieve the installed version numberOpen the iOS App Store, go to the Firefox Focus app page, or check within the app settings under 'About' to view the version. Note the exact version number.Affected if Version cannot be determined or app not found
-
Compare version against affected rangeCompare the installed version to the affected range: versions prior to 122.0 are vulnerable. If version shows 122.0 or higher, the version includes the fix.Affected if Installed version is lower than 122.0 (for example, 121.0, 120.3, etc.)
The environment is affected if Firefox Focus for iOS with a version lower than 122.0 is installed on the device and the browser functionality is accessible to the user.
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 Focus for iOS to version 122 or later to apply the vendor patch. If immediate patching is not possible, avoid using the browser until the update is available, as user interaction (visiting a crafted page) is sufficient to trigger exploitation.
Firefox Focus for iOS 122.0 or later
- Open the App Store on your iOS device
- Search for Firefox Focus or navigate to your installed apps
- Tap Update to upgrade Firefox Focus to version 122.0 or later
- After updating, verify the version in Settings > Firefox Focus > Version to confirm installation of 122.0 or higher
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Firefox Focus
Scoped from the published advisory
- Consultation2.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,960.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-0605 — 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-0605 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