Heap corruption via crafted WebRTC packets
Published Dec 23, 2021 · Updated Aug 3, 2024
Out-of-bounds write in Google Chrome before 96.0.4664.93 allows remote attackers to corrupt heap memory via crafted WebRTC packets. Google identifies WebRTC as the affected component but has not published the specific parser, buffer, or bounds-checking error that writes beyond the allocation. Network delivery requires no authentication, but user interaction is required; successful exploitation compromises browser data and operation.
Summary
What happened
Out-of-bounds write in Google Chrome before 96.0.4664.93 allows remote attackers to corrupt heap memory via crafted WebRTC packets. Google identifies WebRTC as the affected component but has not published the specific parser, buffer, or bounds-checking error that writes beyond the allocation. Network delivery requires no authentication, but user interaction is required; successful exploitation compromises browser data and operation.
The record
- CVE
- CVE-2021-4079
- Published
- Dec 23, 2021
- Updated
- Aug 3, 2024
- Vendor
- Google Cloud
- Product
- Google Chrome
- Classifications
- CWE-787, T1203
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Dec 23, 2021CVE 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 <96.0.4664.93
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.
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