Security readout for executives and security teams
Plain-English summary
This is a Google Chrome browser memory-safety flaw in WebSerial. A remote attacker could potentially trigger heap corruption by getting a vulnerable user to open crafted HTML. The source bundle identifies affected Chrome versions as prior to 91.0.4472.164.
Executive priority
Prioritize remediation for user endpoints because browser memory-corruption issues can affect ordinary web browsing. Treat this as high priority if legacy Chrome remains in use, but evidence here does not support claiming active exploitation.
Technical view
CVE-2021-30562 is a use-after-free vulnerability in Chrome WebSerial. The CVE description says crafted HTML could potentially exploit heap corruption before Chrome 91.0.4472.164. No CVSS, CWE, public exploit details, or vendor mitigation beyond the fixed version are included here.
Likely exposure
Exposure is likely limited to systems running Google Chrome versions earlier than 91.0.4472.164. Risk is highest where users browse untrusted sites or receive links that open in vulnerable Chrome installations.
Exploitation context
The provided sources describe remote exploitation via a crafted HTML page, but do not state active exploitation. CISA KEV status is false in the bundle, and the Chromium bug reference may not provide public technical detail.
Researcher notes
The record lacks CVSS, CWE mapping, and public exploit details. Analysis should remain centered on Chrome WebSerial, use-after-free behavior, heap corruption, crafted HTML, and the fixed version boundary of 91.0.4472.164.
Mitigation direction
- Upgrade Google Chrome to 91.0.4472.164 or later.
- Confirm managed endpoints receive Chrome security updates automatically.
- Check Google Chrome release guidance for platform-specific update details.
- Reduce exposure to untrusted browsing on systems that cannot update promptly.
Validation and detection
- Inventory Chrome versions across managed endpoints.
- Flag any Chrome installation earlier than 91.0.4472.164.
- Verify browser update policies are enabled and functioning.
- Review vulnerability scanner results for this CVE after update rollout.
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.
CVE-2021-30562 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
- Unknown
- CVSS
- Not scored
- Known Exploited
- No
- Published
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.
CVSS and timeline data
No CVSS vectors or timeline events were available in the normalized CVE source material.
Source materials
- CVE List V5 sourceCVE List V5
- https://chromereleases.googleblog.com/2021/07/stable-channel-update-for-desktop.htmlCVE reference · x_refsource_MISC
- https://crbug.com/1220078CVE reference · x_refsource_MISC
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.