Heap corruption via WebAssembly type confusion
Published Nov 2, 2021 · Updated Aug 5, 2024
Type confusion in WebAssembly in Google Chrome before 66.0.3359.139 allows remote attackers to corrupt heap memory via crafted HTML. Public records identify WebAssembly in the V8 engine as the locus but do not disclose the incompatible types or faulty operation that triggers the confusion. A user must open attacker-controlled content; available sources establish heap corruption but do not document whether exploitation escapes browser sandboxing or achieves code execution.
Summary
What happened
Type confusion in WebAssembly in Google Chrome before 66.0.3359.139 allows remote attackers to corrupt heap memory via crafted HTML. Public records identify WebAssembly in the V8 engine as the locus but do not disclose the incompatible types or faulty operation that triggers the confusion. A user must open attacker-controlled content; available sources establish heap corruption but do not document whether exploitation escapes browser sandboxing or achieves code execution.
The record
- CVE
- CVE-2018-6122
- Published
- Nov 2, 2021
- Updated
- Aug 5, 2024
- Vendor
- Google Cloud
- Product
- Google Chrome
- Classifications
- CWE-843, T1203
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Nov 2, 2021CVE publishedPublication date reported by the CVE source.
- Aug 5, 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 <66.0.3359.139
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