Threats / WebRTC / CVE-2022-2294
CVE-2022-2294
· EUVD no mirror located
· GCVE no mirror located
Verified 2026-06-22
WebRTC vulnerability
WebRTC heap buffer overflow enables remote code execution in web browsers. The vulnerability allows attackers to execute arbitrary shellcode through malicious content.
Verdict
Today item, not a backlog item.
A heap buffer overflow in WebRTC permits remote code execution when processing specially crafted input. Exploitation occurs in-browser without user interaction beyond visiting a malicious page. Active exploitation and ransomware deployment have been observed.
01
Is it exploitable?
— the evidence, ranked above the scoreReported exploitation
9 independent public reports of in-the-wild exploitation are cataloged.Distinct reporting sources (vendor, incident response, government); open them for the underlying claims.
Exploited in the wild
Listed in the CISA Known Exploited Vulnerabilities catalog (added 2022-08-25), flagged for known ransomware use.
Probability (EPSS)
EPSS 0.70461 — modeled likelihood of exploitation activity.EPSS is a daily-changing model output — open the source for today's value.
Severity / affected
Affected: WebRTC, WebRTC. Confirm exact fixed builds in the vendor advisory.
Weakness (CWE)
Mapped to CWE-122 Heap-based Buffer Overflow — weakness family: Memory safety.CWE assignment from the public NVD record; the weakness class drives how the flaw is exploited.
02
Who’s exploiting it?
— attribution turns risk into urgencyAttribution not established
No confirmed (advisory-backed) threat-actor attribution is established for this record. Absence of a named actor is not absence of compromise — see Coverage & confidence.
03
Why it matters
— the attack path, told twice: adversary, then board1
Front door — unauthenticated access narrative 1
Attacker
I craft a malicious webpage or media file that triggers the heap buffer overflow when processed by WebRTC.
Business
Users visiting untrusted sites or opening adversary-controlled media face immediate code execution risk within their browser context.
2
Keys to the kingdom — privilege/identity takeover narrative 2
Attacker
I overflow the heap buffer to overwrite adjacent memory and inject shellcode for arbitrary command execution.
Business
Attackers gain execution privileges equivalent to the browser process, enabling data theft, malware installation, or lateral movement.
3
Lateral reach — past segmentation narrative 3
Attacker
I use the code execution to deploy ransomware or establish persistence on the victim's system.
Business
Organizations face operational disruption, data encryption, extortion demands, and potential regulatory penalties from ransomware campaigns.
04
What to do
— defensible action- Remediate per the vendor advisory — confirm the fixed build for your version and verify exposure.1
Say it to the boardA vulnerability with this evidence profile is a defensible budget line, not a backlog ticket — fund the change against the proof above.
05