LiveActive security incident?Get immediate response
CVE Record

CVE-2023-2033: Type confusion in V8 in Google Chrome prior to 112.0.5615.121 allowed a remote attacker to potentially expl...

Type confusion in V8 in Google Chrome prior to 112.0.5615.121 allowed a remote attacker to potentially exploit heap corruption via a crafted HTML page. (Chromium security severity: High)

HighCVSS 8.8Known exploitedUpdated
Glexia's TakeAutomated analysiscritical

Security readout for executives and security teams

Plain-English summary

CVE-2023-2033 is a high-severity Chrome V8 flaw that could let an attacker compromise a user’s browser through a malicious HTML page. Because CISA lists it as known exploited, organizations should treat unpatched Chrome or Chromium-based packages as urgent exposure.

Executive priority

Treat this as urgent patching work because it affects widely deployed browsers and is listed by CISA as known exploited. User interaction is required, but malicious web content is a common delivery path.

Technical view

The flaw is a V8 type confusion issue, mapped to CWE-843, affecting Google Chrome before 112.0.5615.121. The CVSS 3.1 score is 8.8 with network attack vector, low complexity, no privileges required, and user interaction required. Successful exploitation could affect confidentiality, integrity, and availability.

Likely exposure

Exposure is most likely on endpoints or managed Linux systems running Chrome or Chromium packages older than the fixed 112.0.5615.121 release or vendor-patched equivalents.

Exploitation context

CISA KEV status supports active exploitation. Public details in the bundle describe exploitation via a crafted HTML page and heap corruption, but do not provide safe evidence for specific campaigns, targeting, or exploit mechanics.

Researcher notes

The provided sources identify a V8 type confusion leading to potential heap corruption. The Chromium bug link is referenced, but the bundle does not include detailed root-cause analysis, exploit primitives, or campaign indicators.

Mitigation direction

  • Update Google Chrome to 112.0.5615.121 or later.
  • Apply Chromium package updates from Debian, Fedora, Gentoo, or relevant vendors.
  • Prioritize browsers on executive, finance, developer, and admin endpoints.
  • Check vendor advisories for any product-specific remediation guidance.
  • Confirm browser auto-update policies are enabled and enforced.

Validation and detection

  • Inventory installed Chrome and Chromium versions across managed endpoints.
  • Verify no Chrome builds older than 112.0.5615.121 remain.
  • Review Linux package manager status for patched Chromium builds.
  • Confirm CISA KEV tracking includes CVE-2023-2033 remediation status.
  • Check EDR or browser telemetry for suspicious browser crash patterns.
Prepared
Confidence
high
Sources
6

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

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 · low confidence lookup

CWE-843: 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 lookup
cve · low confidence lookup

CVE-2023-2033 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
High
CVSS
8.8 (3.1)
Known Exploited
Yes
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

Official CVE source material

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.

1CVSS vectors
0Timeline events
0ADP providers
13Source links

CISA KEV status

Status
Known exploited
Source
CISA / ADP
Date added
Not provided

CVSS vector scores

1 official score

We 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.

ScoreVersionSeverityVectorExploitImpactSource
8.8CVSS 3.1HighCVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H2.85.9Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

8.8High
CVSS 3.1 vector shape for CVE-2023-2033Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
GoogleChrome112.0.5615.121Listed
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-843 · source CWE mapping

Access of Resource Using Incompatible Type ('Type Confusion')

Access of Resource Using Incompatible Type ('Type Confusion') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.