ChromeWeb browser · Google
CVE-2022-0455
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 98.0.4758.80 allowed a remote attacker to spoof 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 confidenceThis is a URL spoofing vulnerability in Google Chrome for Android's full screen mode. A remote attacker can craft a malicious HTML page that, when viewed in fullscreen mode, causes the Omnibox (URL bar) to display a spoofed URL different from the actual site being visited, potentially tricking users into believing they're on a legitimate website.
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
< 98.0.4758.80CVSS 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.
-
Identify Google Chrome for Android installationCheck if Google Chrome is installed on the Android device. On the device, go to Settings > Apps > Chrome, or check the Chrome app icon on the home screen or app drawer.Affected if Google Chrome for Android is installed on the device.
-
Determine installed Chrome versionOpen Chrome on the Android device, tap the three-dot menu in the top right, go to Settings > About Chrome. The version number is displayed on this page.Affected if The displayed version number is lower than 98.0.4758.80.
-
Check for fullscreen mode usageDetermine if the Chrome browser is being used in fullscreen mode. This mode is typically activated when watching videos in fullscreen, using presentation mode, or when the browser UI elements are hidden to maximize screen real estate.Affected if Chrome for Android is being used in fullscreen mode with a version lower than 98.0.4758.80.
A user is affected if Google Chrome for Android version lower than 98.0.4758.80 is installed and the browser is being used in fullscreen mode, allowing the Omnibox to display a spoofed URL.
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 · scoped98.0.4758.80
Update Google Chrome for Android to version 98.0.4758.80 or later. In enterprise environments, use mobile device management (MDM) tools to verify and enforce Chrome updates across managed devices.
Chrome 98.0.4758.80 (or later) for Android
- Open the Google Play Store app on the Android device
- Search for 'Google Chrome' or locate it in your installed apps
- If an update is available, tap the 'Update' button to install version 98.0.4758.80 or later
- Alternatively, ensure 'Auto-update apps' is enabled in Play Store settings to receive future security updates automatically
- After updating, fully close and restart Google Chrome to ensure the security patch is applied
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Chrome
Scoped from the published advisory
- Consultation3.0 h
- Testing2.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,728.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-0455 — 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-0455 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