Heap corruption via DevTools out-of-bounds write
Published Jul 27, 2022 · Updated Aug 3, 2024
Heap buffer overflow in DevTools in Google Chrome before 102.0.5005.61 allows attackers to corrupt heap memory through crafted HTML. Google has not disclosed the affected DevTools routine, the destination buffer, or the missing bounds check that permits the out-of-bounds heap write. Exploitation requires convincing a user to install a malicious extension before attacker-controlled page content is processed, and public sources do not establish code execution.
Summary
What happened
Heap buffer overflow in DevTools in Google Chrome before 102.0.5005.61 allows attackers to corrupt heap memory through crafted HTML. Google has not disclosed the affected DevTools routine, the destination buffer, or the missing bounds check that permits the out-of-bounds heap write. Exploitation requires convincing a user to install a malicious extension before attacker-controlled page content is processed, and public sources do not establish code execution.
The record
- CVE
- CVE-2022-1876
- Published
- Jul 27, 2022
- Updated
- Aug 3, 2024
- Vendor
- Google Cloud
- Product
- Google Chrome
- Classifications
- CWE-787, T1204.002
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jul 27, 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 <102.0.5005.61
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