Skip to content
CTI Academy Sponsor CTI Academy
MEDIUM · CVSS 6.5 CISA Known Exploited Vulnerability

CVE-2022-2856

Google Chromium Intents Insufficient Input Validation Vulnerability

Google Chromium Intents

Insufficient 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.

CVSS
6.5
MEDIUM
EPSS
4.6%
30-day exploitation
Ransomware groups
0
recorded exploiting
Published
26 Sep 2022
CWE-20

Exploitation status

CISA Known Exploited Vulnerabilities

Listed by CISA on 18 August 2022. US federal agencies were required to remediate it by 8 September 2022.

EPSS — exploitation probability

FIRST puts the probability of exploitation activity in the next 30 days at 4.6%, which is higher than 91.7% of all scored vulnerabilities. EPSS is a forecast of activity, not a measure of severity, and it is rescored daily.

CVSS vector

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:N

Frequently asked questions

Is CVE-2022-2856 being exploited by ransomware groups?

No ransomware group in this database is currently recorded as exploiting CVE-2022-2856.

What does CVE-2022-2856 affect?

CVE-2022-2856 affects Google Chromium Intents. Insufficient 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.

How severe is CVE-2022-2856?

CVE-2022-2856 is rated MEDIUM with a CVSS base score of 6.5. EPSS puts the probability of exploitation in the next 30 days at 4.6%, higher than 91.7% of all scored vulnerabilities. It is listed in the CISA Known Exploited Vulnerabilities catalog, with a federal remediation deadline of 8 September 2022.

How should organisations respond to CVE-2022-2856?

Apply the vendor patch for Google Chromium Intents as the first priority, and treat any internet-facing instance as the most urgent. Because this vulnerability is associated with ransomware activity, also review whether the affected systems were reachable before patching, rather than assuming that patching alone closes the incident.