Heap corruption via mismatched WebRTC encoding vectors
Published Jul 28, 2022 · Updated Aug 4, 2026
Heap buffer overflow in WebRTC in Google Chrome before 103.0.5060.114 allows remote attackers to trigger heap corruption via a crafted HTML page. When SDP munging removes a supported encoding, LocalConnection reconciles unequal encoding vectors and copies properties past the shorter vector's bounds. Exploitation requires a crafted page and user interaction; the out-of-bounds write corrupts the browser renderer heap, and Google confirmed exploitation in the wild.
Summary
What happened
Heap buffer overflow in WebRTC in Google Chrome before 103.0.5060.114 allows remote attackers to trigger heap corruption via a crafted HTML page. When SDP munging removes a supported encoding, LocalConnection reconciles unequal encoding vectors and copies properties past the shorter vector's bounds. Exploitation requires a crafted page and user interaction; the out-of-bounds write corrupts the browser renderer heap, and Google confirmed exploitation in the wild.
The record
- CVE
- CVE-2022-2294
- Published
- Jul 28, 2022
- Updated
- Aug 4, 2026
- Vendor
- Google Cloud
- Product
- Google Chrome
- Classifications
- T1203
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jul 28, 2022CVE publishedPublication date reported by the CVE source.
- Aug 25, 2022Exploitation reportedCISA Known Exploited Vulnerabilities catalog listing
- Aug 4, 2026Record 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 <103.0.5060.114
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.
Weakness, pattern, technique
Public exploit references
- Project Zero Chrome WebRTC trigger proof of conceptproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Reported exploitation
- CISA Known Exploited Vulnerabilities catalog listingknown exploited catalog
- Google-reported exploitation in the wildreported exploitation
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