Heap corruption via CSS type confusion
Published Mar 7, 2023 · Updated Oct 17, 2024
Type confusion in Google Chrome before 111.0.5563.64 allows remote attackers to corrupt heap memory through a crafted HTML page. Google identifies the affected component only as CSS; the restricted Chromium issue does not publicly disclose the specific object types or operation that become confused. Exploitation requires a user to load attacker-controlled HTML, and successful heap corruption can compromise the browser process's confidentiality, integrity, or availability.
Summary
What happened
Type confusion in Google Chrome before 111.0.5563.64 allows remote attackers to corrupt heap memory through a crafted HTML page. Google identifies the affected component only as CSS; the restricted Chromium issue does not publicly disclose the specific object types or operation that become confused. Exploitation requires a user to load attacker-controlled HTML, and successful heap corruption can compromise the browser process's confidentiality, integrity, or availability.
The record
- CVE
- CVE-2023-1215
- Published
- Mar 7, 2023
- Updated
- Oct 17, 2024
- Vendor
- Google Cloud
- Product
- Google Chrome
- Classifications
- CWE-843, T1189
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Mar 7, 2023CVE publishedPublication date reported by the CVE source.
- Oct 17, 2024Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <111.0.5563.64
- Affected versionversion=111.0.5563.64 <111.0.5563.64
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo