Heap corruption via WebGPU buffer overflow
Published Jul 26, 2022 · Updated Aug 3, 2024
Heap buffer overflow in Google Chrome WebGPU before 101.0.4951.41 allows remote attackers to corrupt heap memory via crafted HTML. Google identifies the WebGPU component but has not published the affected function, malformed field, or out-of-bounds write operation. The attacker must first compromise the renderer process and then cause the browser to process the crafted page; the published record does not establish a further sandbox escape or code-execution outcome.
Summary
What happened
Heap buffer overflow in Google Chrome WebGPU before 101.0.4951.41 allows remote attackers to corrupt heap memory via crafted HTML. Google identifies the WebGPU component but has not published the affected function, malformed field, or out-of-bounds write operation. The attacker must first compromise the renderer process and then cause the browser to process the crafted page; the published record does not establish a further sandbox escape or code-execution outcome.
The record
- CVE
- CVE-2022-1483
- Published
- Jul 26, 2022
- Updated
- Aug 3, 2024
- Vendor
- Google Cloud
- Product
- Google Chrome
- Classifications
- CWE-787, T1203
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jul 26, 2022CVE publishedPublication date reported by the CVE source.
- Aug 3, 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 <101.0.4951.41
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
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.
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