ChromeWeb browser · Google
CVE-2022-2856
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 · uneditedInsufficient validation of untrusted input in Intents in Google Chrome on Android prior to 104.0.5112.101 allowed a remote attacker to arbitrarily browse to a malicious website 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 · moderate confidenceInsufficient validation of untrusted input in Android Intents in Google Chrome on Android prior to version 104.0.5112.101 allows a remote attacker to craft a malicious HTML page that can force Chrome to navigate to arbitrary URLs, potentially leading to phishing or further exploit delivery.
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
< 104.0.5112.101< 104.0.5112.102
FedoraOperating system
= 37CVSS 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 installed browser packageRun 'rpm -qa | grep -iE "chrome|chromium"' on Fedora to list any installed Chrome or Chromium packages.Affected if A Google Chrome or Chromium package is installed on the system
-
Determine the installed versionRun 'google-chrome --version' for Google Chrome or 'chromium --version' for Chromium to obtain the exact version number.Affected if A version number is returned from the command
-
Check the operating system platformVerify if the system is running Android (for Chrome) or Fedora 37 (for Chromium). On Linux systems, check 'cat /etc/os-release' to identify the OS and version.Affected if The system is Fedora 37 (for Chromium) or running Android (for Google Chrome)
-
Compare version against affected rangesCompare your installed version to the affected ranges: Google Chrome versions before 104.0.5112.101 or 104.0.5112.102, or Chromium on Fedora 37.Affected if Installed version is less than 104.0.5112.101 (or 104.0.5112.102) on Android Chrome, or any version of Chromium on Fedora 37
You are affected if you have Google Chrome on Android or Chromium on Fedora 37 with a version below 104.0.5112.101/102.
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 · scoped104.0.5112.101104.0.5112.102
Update Google Chrome for Android to version 104.0.5112.101 or later to patch the intent validation vulnerability.
Chrome 104.0.5112.101 or later for Android
- Open Google Chrome on your Android device
- Navigate to Settings > Help > About Chrome
- If an update is available, Chrome will automatically download and install version 104.0.5112.101 or later
- Alternatively, open Google Play Store, search for Google Chrome, and tap Update if an update is available
- Restart Chrome after the update completes to ensure the vulnerability is patched
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Chrome
Exploited in the wild — priority engagement
- Consultation2.0 h
- Implementation1.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,696.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-2856 — 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-2856 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