Raw vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:HSummary
CVE-2022-2294 is a high-severity Out-of-bounds Write (CWE-787) vulnerability in Apple Mac Os X. Its CVSS base score is 8.8 (High).
Operationally, exploitation aligns with the MITRE ATT&CK technique Exploitation for Privilege Escalation (T1068); ranked in the top 0.7% of CVEs by exploit likelihood; CISA has added it to the Known Exploited Vulnerabilities catalog.
Deeper analysis AI-assisted summary
Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.
CVE-2022-2294 is a heap buffer overflow vulnerability in the WebRTC component of Google Chrome versions prior to 103.0.5060.114. The flaw, tracked under CWE-787, stems from improper bounds checking that can lead to heap corruption when processing certain inputs.
A remote attacker can exploit the issue by convincing a user to visit a crafted HTML page, achieving arbitrary code execution or other impacts consistent with the CVSS 8.8 rating that reflects network attack vector, low complexity, and no required privileges.
Chrome stable channel updates released on 28 July 2022 address the vulnerability by advancing the browser to version 103.0.5060.114 or later; downstream distributions such as Fedora also issued corresponding package updates to incorporate the fix.
The associated EPSS score rose from a low baseline after disclosure to a peak of 0.1589 on 2024-12-17 before receding to the current value of 0.0150, indicating that exploitation interest materialized well after the original publication.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2022-34567
Vulnerability Data
Heap buffer overflow in WebRTC in Google Chrome prior to 103.0.5060.114 allowed a remote attacker to potentially exploit heap corruption via a crafted HTML page.
- CWE(s)
- KEV Date Added
- 25 August 2022
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
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.
Out-of-bounds writes that corrupt control flow or inject shellcode are rendered non-executable by the same memory protections.
Mitigating Controls (NIST CSF 2.0) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.
Secure-development practices (static analysis, bounds checking, code review) are the primary means of preventing out-of-bounds writes.
Vulnerability scanning and recording can discover out-of-bounds write flaws so they can be remediated.
Patching or replacing vulnerable software directly eliminates known instances of this coding weakness.
Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.
Security testing in development and acceptance can detect and prevent out-of-bounds write defects.
Secure development life cycle mandates practices that prevent out-of-bounds writes.
Application security requirements can specify bounds-checking and safe memory handling.
Secure architecture and engineering principles reduce the likelihood of buffer overflows.
Secure coding directly addresses out-of-bounds writes through language choice and coding standards.
Change management can enforce review gates that catch unsafe memory operations before deployment.