Heap corruption via bad CSS object cast
Published Jun 3, 2020 · Updated Aug 6, 2024
Incorrect type conversion in Google Chrome before 11.0.0.0 allows remote attackers to corrupt heap memory through crafted CSS in an HTML page. Chrome's CSS handling casts a CSS value to an incompatible object type, causing heap corruption when the crafted page is rendered. Exploitation requires a user to open attacker-controlled content and can compromise browser confidentiality, integrity, and availability.
Summary
What happened
Incorrect type conversion in Google Chrome before 11.0.0.0 allows remote attackers to corrupt heap memory through crafted CSS in an HTML page. Chrome's CSS handling casts a CSS value to an incompatible object type, causing heap corruption when the crafted page is rendered. Exploitation requires a user to open attacker-controlled content and can compromise browser confidentiality, integrity, and availability.
The record
- CVE
- CVE-2011-1805
- Published
- Jun 3, 2020
- Updated
- Aug 6, 2024
- Vendor
- Google Cloud
- Product
- Google Chrome
- Classifications
- CWE-704, T1203
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jun 3, 2020CVE publishedPublication date reported by the CVE source.
- Aug 6, 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=unspecified <11.0.0.0
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