Google Chromium WebRTC Heap Buffer Overflow Vulnerability
Google · Chromium WebRTC
A heap buffer overflow in the WebRTC component of Google Chrome (Chromium WebRTC) allows heap corruption. An attacker who can get a victim to load a crafted HTML page can potentially exploit this, which requires user interaction and no prior authentication or special network position.
Heap buffer overflow in WebRTC in Google Chrome prior to 120.0.6099.129 allowed a remote attacker to potentially exploit heap corruption via a crafted HTML page. (Chromium security severity: High)
- Exploited
- Yes, in CISA KEV
- Reports
- 0
- Tactics
- 3/15
How an attack unfolds
Based on MITRE ATT&CKA public catalogue of the techniques attackers use, maintained by MITRE. Patchfirst uses it to describe what attackers do with a vulnerability. mappings. Select a step to see the evidence.How attackers get in
What they do
Exploitation timelineDated milestones for a CVE: when it was disclosed, when exploit code became public, when exploitation was confirmed, and when threat reports named it.
First seen exploited 2 days before it was disclosed. Public exploit code (PoC-in-GitHub) appeared 23 months after disclosure.
- First seen exploitedVulnCheck KEV evidence2 days before
- Disclosedday 0
- Added to CISA KEVEU database agrees+12 days
- Public exploit codePoC-in-GitHub+23 mo
CISA KEV listing is when exploitation was confirmed, not necessarily the first attack.
MITRE ATT&CKA public catalogue of the techniques attackers use, maintained by MITRE. Patchfirst uses it to describe what attackers do with a vulnerability. techniques
2 TechniqueOne specific attacker behaviour in MITRE ATT&CK, such as T1190 “Exploit Public-Facing Application”. IDs with a dot, like T1059.004, are sub-techniques., grouped by TacticThe attacker’s goal at a stage of an attack in MITRE ATT&CK, such as Initial Access or Persistence. Each technique belongs to one or more tactics. in kill-chain order 2Initial AccessTA0001
This heap buffer overflow vulnerability is exploited by a remote attacker via a crafted HTML page. This vulnerability has been leveraged by the NSO group to enable remote code execution within a browser's WebRTC component to install the spyware Pegasus on victim endpoints.
ExecutionTA0002
Detection
0 rules for this CVE · 11 general rules for its techniquesRules for this CVE
0Sigma ruleAn open, vendor-neutral detection rule for log data. Security teams convert Sigma rules into searches for their own SIEM. that reference CVE-2023-7024 directly.CVE-specific rules are not available in this build. Search SigmaHQ ↗
General rules for this CVE’s techniques
These detect the technique in general, not this specific vulnerability.
Drive-by CompromiseT11893 general rules
Hijack Execution FlowT15748 general rules
- Exploiting SetupComplete.cmd CVE-2019-1378hightest
- Potential PrintNightmare Exploitation Attempthightest
- Suspicious Printer Driver Empty Manufacturerhightest
- DLL Execution Via Register-cimprovider.exemediumtest
- Potential Initial Access via DLL Search Order Hijackingmediumtest
- Potential Registry Persistence Attempt Via DbgManagedDebuggermediumtest
- Regsvr32 DLL Execution With Uncommon Extensionmediumtest
- Windows Spooler Service Suspicious Binary Loadinformationaltest
Sigma rules © SigmaHQ, Detection Rule License 1.1; linked, not reproduced.
What security researchers reported
Not named in any threat report yetAlso mentioned in 50 community threat pulses (AlienVault OTX)
Weaker evidencePulses are indicator collections that anyone can publish. A mention is not confirmation of exploitation.
- Actively_Exploited_Kev | Oct 30, 202629 Oct 2026
- Actively_Exploited_Kev | Oct 29, 202628 Oct 2026
- Actively_Exploited_Kev | Oct 28, 202627 Oct 2026
- Actively_Exploited_Kev | Oct 27, 202626 Oct 2026
- Actively_Exploited_Kev | Oct 24, 202623 Oct 2026
- Actively_Exploited_Kev | Oct 23, 202622 Oct 2026
- 44 more on OTX