Firefox FocusWeb browser · Mozilla

CVE-2023-29534

CRITICAL · 9.1 CVSS v3.1 Published 2023-06-19
Fix available
A fix is available. Upgrade to 112.0 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

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
Different techniques existed to obscure the fullscreen notification in Firefox and Focus for Android. These could have led to potential user confusion and spoofing attacks. *This bug only affects Firefox and Focus for Android. Other versions of Firefox are unaffected.* This vulnerability affects Firefox for Android < 112 and Focus for Android < 112.

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 confidence

This is a UI spoofing vulnerability in Firefox and Focus for Android where attackers could obscure or manipulate the fullscreen notification indicator. The vulnerability allows malicious sites to hide the indicator that normally shows users they're in fullscreen mode, potentially leading users to believe they're viewing content in a normal browser window when they're actually in fullscreen, enabling further spoofing or social engineering attacks.

MitigationUpdate Firefox for Android to version 112 or later, and Focus for Android to version 112 or later. Users should upgrade through the Google Play Store or organization's mobile device management solution.

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:< 112.0
Firefox MobileWeb browser
Affected:< 112.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
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 checks

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

  1. Identify if Firefox for Android is installed
    Open the device Settings, go to Apps, and look for Firefox in the installed applications list
    Affected if Firefox for Android is present on the device
  2. Check the installed version of Firefox for Android
    In Settings > Apps > Firefox, tap on App info or App details to view the version number displayed under the app name
    Affected if The displayed version is earlier than 112.0 (for example, 111.0, 110.0, etc.)
  3. Identify if Firefox Focus for Android is installed
    In Settings > Apps, look for Firefox Focus in the list of installed applications
    Affected if Firefox Focus for Android is present on the device
  4. Check the installed version of Firefox Focus for Android
    In Settings > Apps > Firefox Focus, tap on App info or App details to view the version number shown under the app name
    Affected if The displayed version is earlier than 112.0 (for example, 111.0, 110.0, etc.)

The device is affected if either Firefox for Android or Firefox Focus for Android is installed and the installed version is below 112.0.

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 112.0 or later
Fixed in 112.0
Interim mitigation

Update Firefox for Android to version 112 or later, and Focus for Android to version 112 or later. Users should upgrade through the Google Play Store or organization's mobile device management solution.

Recommended fix High confidence

Firefox 112.0 for Android / Firefox Focus 112.0 for Android

  1. Open the Google Play Store app on your Android device
  2. Search for 'Firefox' or 'Firefox Focus'
  3. Tap on the app and update to version 112.0 or later if an update is available
  4. Alternatively, ensure automatic updates are enabled for the app in the Play Store settings
  5. After updating, verify the installed version is 112.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
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing1.0 h
  • Review / QA1.0 h
5.0 hours of engineering $890
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,424.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-29534 — 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 sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2023-29534 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