Security readout for executives and security teams
Plain-English summary
This vulnerability affects Google Chrome on Android before 104.0.5112.101. A malicious web page could cause the browser to navigate in an unintended way because Chrome did not sufficiently validate Android Intent input. The CVSS score is medium, but CISA lists it as known exploited, making timely remediation important.
Executive priority
Prioritize remediation because this is a known exploited browser issue on mobile endpoints. The technical severity is medium, but browser exposure and KEV status raise operational urgency. Focus on proving Chrome update coverage across Android fleets.
Technical view
CVE-2022-2856 is CWE-20 input validation failure in Chrome Intents on Android. A remote attacker could use a crafted HTML page to make Chrome browse to a malicious website. The vector requires user interaction, has network reachability, and is rated CVSS 6.5 with high integrity impact.
Likely exposure
Exposure is most likely on Android devices running Chrome before 104.0.5112.101. Organizations using managed mobile fleets should prioritize Chrome version inventory. The source bundle also references Fedora Chromium packaging, but the primary CVE description names Chrome on Android.
Exploitation context
CISA KEV inclusion supports known exploitation. The provided sources do not include exploit timing, scale, targets, or technical exploit details. The CVE description indicates exploitation requires a user to interact with a crafted HTML page.
Researcher notes
The public bundle gives limited root-cause detail beyond insufficient Intent input validation. Avoid assuming broader platform impact. Validate affected scope against Chrome version data and vendor advisories, especially where Chromium packages are managed separately from Android Chrome.
Mitigation direction
- Update Chrome on Android to 104.0.5112.101 or later.
- Check Google Chrome release guidance for any later fixed versions.
- Review Fedora advisory if managing Chromium packages from Fedora repositories.
- Use MDM or endpoint tooling to enforce current browser versions.
- Treat CISA KEV status as a remediation deadline driver.
Validation and detection
- Inventory Android Chrome versions across managed devices.
- Flag any Chrome install earlier than 104.0.5112.101.
- Confirm mobile browser update policy is enforced and reporting correctly.
- Check vulnerability management records for CVE-2022-2856 closure.
- Review CISA KEV tracking for organizational remediation status.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-20: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCVE-2022-2856 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Medium
- CVSS
- 6.5 (3.1)
- Known Exploited
- Yes
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:N
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CISA KEV status
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:N2.83.6Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
6.5MediumVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:N
Source materials
- CVE List V5 sourceCVE List V5
- https://chromereleases.googleblog.com/2022/08/stable-channel-update-for-desktop_16.htmlCVE reference · x_refsource_MISC
- https://crbug.com/1345630CVE reference · x_refsource_MISC
- FEDORA-2022-3f28aa88cfCVE reference · vendor-advisory, x_refsource_FEDORA
- https://www.cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2022-2856CVE reference · government-resource
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Improper Input Validation
Improper Input Validation represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.