ChromeWeb browser · Google
CVE-2022-0804
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 · uneditedInappropriate implementation in Full screen mode in Google Chrome on Android prior to 99.0.4844.51 allowed a remote attacker to hide the contents of the Omnibox (URL bar) via a crafted HTML page.
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 confidenceInappropriate implementation in Full screen mode in Google Chrome on Android prior to 99.0.4844.51 allows a remote attacker to hide the contents of the Omnibox (URL bar) via a crafted HTML page, potentially facilitating phishing attacks by making users believe they're on a different website than the one displayed in the hidden URL bar.
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
ChromeWeb browser
< 99.0.4844.51CVSS 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.
-
Check Chrome for Android versionOpen Chrome on Android, go to Settings > Help > About Chrome, or navigate to chrome://version in the address bar to see the exact version numberAffected if Version displayed is less than 99.0.4844.51 (for example, 98.x.x.x or earlier)
-
Verify full screen mode accessibility settingOn the Android device, go to Settings > Accessibility on the device (not in Chrome), or in Chrome go to Settings > Accessibility to check if full screen mode is enabledAffected if Full screen mode toggle is turned ON in Chrome accessibility settings
-
Check for active full screen API usageWhile browsing, look for websites that may have triggered full screen mode (Chrome displays a warning banner about exiting full screen, or the URL bar disappears from view)Affected if The browser is currently displaying content in full screen mode with the Omnibox hidden from view
You are affected if Chrome for Android version is below 99.0.4844.51 AND full screen mode is enabled or actively being used by a webpage, allowing a malicious site to hide the URL bar.
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 · scoped99.0.4844.51
Update Google Chrome on Android to version 99.0.4844.51 or later to remediate this vulnerability.
Chrome 99.0.4844.51 or later for Android
- Open the Google Play Store app on your Android device
- Search for "Google Chrome" in the Play Store
- Tap on Google Chrome from the search results
- If an "Update" button appears, tap it to update to the latest version (99.0.4844.51 or later)
- Alternatively, enable automatic updates by tapping the three-dot menu and selecting "Enable auto-update"
- After updating, verify the version by opening Chrome, tapping the three-dot menu, going to Settings, and checking "Chrome version" under "About Chrome"
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Chrome
Scoped from the published advisory
- Consultation1.0 h
- Testing0.5 h
- Review / QA0.5 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,200.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-0804 — 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-2022-0804 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