Skip to content
Fencer Vulns
medium 6.1

CVE-2021-38000 kev in the critical feed json

Insufficient validation of untrusted input in Intents in Google Chrome on Android prior to 95.0.4638.69 allowed a remote attacker to arbitr…

published 2021-11-23 4 y ago modified 2026-06-17 4 mo ago also EUVD-2021-24473

cvss
6.1
version 3.1, CNA
cisa kev
Exploited
added 2021-11-03
epss
4.9%
EPSS 4.9% chance of exploitation in 30 days, percentile 92%
public exploits
0
none known

Summary

Insufficient validation of untrusted input in Intents in Google Chrome on Android prior to 95.0.4638.69 allowed a remote attacker to arbitrarily browser to a malicious URL via a crafted HTML page.

Patch / fix

cisa required action Apply updates per vendor instructions.

  • Google Chrome 95.0.4638.69
  • chromium Debian 14, Debian 13, Debian 12 97.0.4692.71-0.1

debian advisories DEBIAN-CVE-2021-38000

  • chromium-browser Ubuntu 18.04 LTS 95.0.4638.69-0ubuntu0.18.04.1

ubuntu advisories UBUNTU-CVE-2021-38000

Ubuntu security data © Canonical Ltd., from https://github.com/canonical/ubuntu-security-notices via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0

  • chromium openSUSE Tumbleweed 95.0.4638.69-1.1
  • chromium openSUSE Tumbleweed 113.0.5672.92-1.1
  • chromium Package Hub 15 SP3, openSUSE Leap 15.3, openSUSE Leap 15.2 95.0.4638.69-bp153.2.40.3

opensuse advisories openSUSE-SU-2024:11604-1openSUSE-SU-2024:12948-1openSUSE-SU-2021:1462-1

  • vivaldi Arch Linux 5.0.2497.24-1
  • chromium Arch Linux 95.0.4638.69-1

arch linux advisories AVG-2475AVG-2504

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2021-38000 updated cvss 8.8

chromium-browser: Insufficient validation of untrusted input in Intents

  • Red Hat All currently supported Red Hat products
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

Timeline

  1. Found exploited as a 0-day (Project Zero)
  2. 0-day patched (Project Zero)
  3. Added to CISA KEV
  4. CISA patch deadline
  5. Published
  6. CISA SSVC: exploitation active

Known exploited

Added
5 y ago
Patch by
2021-11-17 (4 y ago)
Ransomware
Not known
Required action
Apply updates per vendor instructions.
Vendor, product
Google, Chromium Intents
CISA name
Google Chromium Intents Improper Input Validation Vulnerability

Zero-day

Detected in real attacks while still unknown to the vendor and the public, per Google Project Zero's 0day In-the-Wild tracker.

Found
2021-09-15
Patched
2021-10-28
Details
project zero root cause analysis

ATT&CK techniques

How it is exploited and what it leads to, in MITRE ATT&CK terms.

  • T1660 Phishing exploitation, mobile
  • T1437 Application Layer Protocol primary impact, mobile
  • T1658 Exploitation for Client Execution primary impact, mobile

kev release 2025-07-28, att&ck v16.1. KEV to ATT&CK mappings by the MITRE Center for Threat-Informed Defense (Mappings Explorer, Apache-2.0). © 2026 The MITRE Corporation. This work is reproduced and distributed with the permission of The MITRE Corporation. Terms of use

CISA SSVC

Exploitation
Active, exploited in the wild
Automatable
no
Technical impact
partial
Assessed
2 y ago

Exploit prediction

4.95% chance of exploitation in the next 30 days, higher than 92% of all scored CVEs (FIRST EPSS, 2026-11-08).

Exploits and checks

  • crbug.com https://crbug.com/1249962 referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by version score vector
CISA ADP 3.1 6.1 CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N
NVD 3.1 6.1 CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N
CNA 3.1 6.1 CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N
NVD 2.0 5.8 AV:N/AC:M/Au:N/C:P/I:P/A:N

Affected products

  • Google Chrome
  • google android

Classification

Weakness
  • CWE-20 Improper Input Validation
  • CWE-601 URL Redirection to Untrusted Site
Technology feeds

References

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.