ChromeWeb browser · Google
CVE-2022-0802
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 confidenceA remote attacker can exploit an implementation flaw in Google Chrome's fullscreen mode on Android to hide the Omnibox (URL bar) via a crafted HTML page. This UI spoofing vulnerability could facilitate phishing attacks by deceiving users about the actual website they're visiting.
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 Google Chrome for Android versionOpen Chrome, tap the three dots menu, go to Settings > About Chrome to view the version numberAffected if The installed version is below 99.0.4844.51
-
Verify the fullscreen mode behaviorOpen any webpage in Chrome on Android and trigger fullscreen mode (e.g., by watching a video in fullscreen or using the fullscreen API)Affected if The Omnibox (URL bar) can be hidden or does not appear when exiting fullscreen mode on a crafted page
-
Confirm Android platform usageVerify the Chrome browser is running on an Android device (this vulnerability affects only Android, not iOS or desktop)Affected if Chrome is running on Android and the version is below 99.0.4844.51
A user is affected if Google Chrome for Android is installed at a version lower than 99.0.4844.51 and fullscreen mode can be triggered in the browser.
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 for Android to version 99.0.4844.51 or later to obtain the vendor patch.
Chrome for Android version 99.0.4844.51 or later
- 1. Open the Google Play Store app on the Android device
- 2. Search for "Google Chrome" or locate it in the app library
- 3. If an update is available, tap the "Update" button
- 4. Alternatively, enable auto-updates in Play Store settings to ensure Chrome stays current
- 5. Restart Chrome if the update did not complete automatically
- 6. Verify the Chrome version by navigating to chrome://version to confirm version 99.0.4844.51 or later is installed
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Chrome
Scoped from the published advisory
- Consultation1.0 h
- Implementation2.0 h
- Testing1.0 h
- Review / QA1.0 h
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 locallyCheck whether your project pulls in CVE-2022-0802 — 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-0802 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