CVE-2023-5482
Published: 01 November 2023
Summary
CVE-2023-5482 is a high-severity Insufficient Verification of Data Authenticity (CWE-345) vulnerability in Fedoraproject Fedora. Its CVSS base score is 8.8 (High).
Operationally, ranked in the top 5.9% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog.
Deeper analysis
CVE-2023-5482 is an insufficient data validation flaw in the USB component of Google Chrome prior to version 119.0.6045.105. The issue permits out-of-bounds memory access and carries a CVSS 3.1 base score of 8.8 with CWE-345.
A remote attacker can trigger the vulnerability by serving a crafted HTML page to a victim, achieving high-impact effects on confidentiality, integrity, and availability without requiring authentication or special privileges beyond user interaction.
Chrome stable channel updates and downstream Fedora advisories direct users to upgrade immediately to the fixed release to eliminate the flaw.
EPSS for the CVE rose from a low baseline to a recorded peak of 0.1673, indicating emerging exploitation interest after public disclosure.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2023-57796
Vulnerability details
Insufficient data validation in USB in Google Chrome prior to 119.0.6045.105 allowed a remote attacker to perform out of bounds memory access via a crafted HTML page. (Chromium security severity: High)
- CWE(s)
Related Threats
No named actor attribution yet. ATT&CK technique mapping in progress for this CVE.
Affected Assets
Mitigating Controls
Likely Mitigating Controls AI
Per-CVE control mapping for this CVE has not run yet; the list below is derived from the weakness types (CWEs) cited in the NVD entry.
Directly requires independent verification of matching output before adverse decisions, mitigating insufficient authenticity checks on data from external sources.
Use of approved PKI certificates provides verifiable data authenticity and origin for communications and artifacts.
Mandates provision of authenticity and integrity artifacts that enable verification of name/address resolution data.
Requires explicit verification of data authenticity from authoritative sources, preventing acceptance of unauthenticated resolution responses.
Control requires verification of data authenticity/integrity (e.g., checksums) after aggregation/packing, directly reducing exploitation of insufficient verification before transmission.
Time synchronization supports reliable freshness verification when checking data authenticity across systems or components.
Mandates verification of data authenticity for software, firmware, and information.
Provenance documentation and monitoring directly enables verification of authenticity for components and data throughout their history.