Security readout for executives and security teams
Plain-English summary
CVE-2022-3373 is a high-severity Google Chrome V8 memory corruption flaw. A malicious web page could trigger an out-of-bounds write if a user opens it, potentially compromising the browser and user session.
Executive priority
Treat as high priority for endpoint patch management. The flaw affects a widely deployed browser component and can be reached through ordinary web content, but active exploitation is not evidenced in the provided sources.
Technical view
The issue is CWE-787 out-of-bounds write in Chrome's V8 JavaScript engine before 106.0.5249.91. CVSS 3.1 is 8.8 with network attack vector, low complexity, no privileges required, and user interaction required.
Likely exposure
Organizations are exposed where Google Chrome desktop installations remain older than 106.0.5249.91, especially endpoints used for email, web browsing, or unmanaged internet access.
Exploitation context
The source bundle describes exploitation through a crafted HTML page. It does not show CISA KEV listing or cite public evidence of active exploitation.
Researcher notes
Public details are limited to V8 out-of-bounds write, crafted HTML trigger, and Chrome fix boundary. The referenced Chromium bug may contain restricted detail, so avoid assuming root cause or exploit primitives beyond the CVE text.
Mitigation direction
- Update Google Chrome to 106.0.5249.91 or later.
- Prioritize managed desktop and laptop browser fleets.
- Confirm auto-update policies are enabled and enforced.
- Check Google Chrome release guidance for any additional vendor instructions.
Validation and detection
- Inventory Chrome versions across managed endpoints.
- Flag installations older than 106.0.5249.91.
- Verify browser update policy compliance in endpoint management tooling.
- Review web-security telemetry for suspicious browser crash patterns.
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-787: 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-3373 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
- High
- CVSS
- 8.8 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
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 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:H/I:H/A:H2.85.9Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
8.8HighVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
Source materials
- CVE List V5 sourceCVE List V5
- https://chromereleases.googleblog.com/2022/09/stable-channel-update-for-desktop_30.htmlCVE reference
- https://crbug.com/1366399CVE reference
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.
Out-of-bounds Write
Out-of-bounds Write represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.