dbcve.org
Firefox FocusWeb browser · Mozilla

CVE-2024-0606

MEDIUM · 6.1 CVSS v3.1 Published 2024-01-22
Fix available
A fix is available. Upgrade to 122.0 or later.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable No privileges

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 · unedited
An attacker could execute unauthorized script on a legitimate site through UXSS using window.open() by opening a javascript URI leading to 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 confidence

Focus for iOS before version 122 contains a Universal Cross-Site Scripting (UXSS) vulnerability where opening a javascript URI via window.open() allows an attacker to execute arbitrary scripts in the context of a legitimate website the user has loaded, bypassing same-origin restrictions.

MitigationUsers should update Focus for iOS to version 122 or later. Development teams should sanitize or block javascript: URIs from being opened via window.open() to prevent script execution in the context of loaded pages.

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
Affected:< 122.0

CVSS 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
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/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 checks

Work through these to decide whether this CVE applies to you.

  1. Confirm the app is Mozilla Firefox Focus for iOS
    Open the iOS Settings app, scroll to the Focus app listing, or check the App Store listing to verify the application name is exactly 'Firefox Focus' or 'Mozilla Firefox Focus' for iOS.
    Affected if The installed app is Mozilla Firefox Focus for iOS.
  2. Check the installed version number
    Open the iOS App Store, go to your purchased apps list, or check within the app's App Store page to view the version number. Alternatively, check the app version in Settings > General > iPhone Storage > Firefox Focus if available.
    Affected if The version number is lower than 122.0 (for example, 121.x, 120.x, etc.).
  3. Determine if the app handles web content with javascript: URI support
    Inspect the app's WebView configuration or test whether the browser can navigate to javascript: URIs by examining network traffic or testing with a known javascript: URI handler.
    Affected if The app's WebView component processes javascript: URIs and allows them to execute within page contexts.
  4. Verify if window.open() can accept javascript: URIs
    Test whether web content loaded in the browser can execute JavaScript via window.open('javascript:...') calls, which would indicate the vulnerability is present.
    Affected if The browser allows window.open() with javascript: URIs to execute script in the context of loaded pages, bypassing same-origin restrictions.

A user is affected if they are running Mozilla Firefox Focus for iOS with a version lower than 122.0 and the browser permits javascript: URIs to be opened via window.open(), allowing script execution in the context of legitimate websites.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 122.0 or later
Fixed in 122.0
Interim mitigation

Users should update Focus for iOS to version 122 or later. Development teams should sanitize or block javascript: URIs from being opened via window.open() to prevent script execution in the context of loaded pages.

Recommended fix High confidence

Firefox Focus for iOS 122.0 or later

  1. 1. Open the App Store on your iOS device
  2. 2. Search for Firefox Focus or navigate to your installed Firefox Focus app
  3. 3. Update the application to the latest version (122.0 or later)
  4. 4. Verify the update completed successfully 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
22.0 hours of engineering $3,860
Get the upgrade done

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 locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-0606 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-0606 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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