Security Digest · Vulnerability record · Known exploited

CVE-2023-7024: Google Chromium WebRTC Heap Buffer Overflow Vulnerability

Exploited in the wild (CISA KEV). 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.

CISA KEV · added 2024-01-02 CVSS 8.8 High EPSS 6.7% · p94

Should you act?

Exploited: patch now if you run it

CISA has confirmed exploitation in the wild. This signal is computed from CISA KEV, EPSS and CVSS data; it is not an editorial verdict.

  • Yes, if you run Google Chromium WebRTC. CISA added this CVE to its Known Exploited Vulnerabilities catalog on 2024-01-02, which means there is reliable evidence of exploitation in the wild. US federal agencies must remediate by 2024-01-23; treat that as the outer limit, not the target.
  • EPSS 6.7%, percentile 94: FIRST’s model estimates a 6.7% chance of exploitation activity in the next 30 days, higher than 94% of all scored CVEs (elevated). EPSS is a probability, not a verdict.
  • Needs a user to click or open something. Phishing makes that realistic, but it is not wormable.

What it is

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)

CISA’s summary

Google Chromium WebRTC, an open-source project providing web browsers with real-time communication, contains a heap buffer overflow vulnerability that allows a remote attacker to potentially exploit heap corruption via a crafted HTML page. This vulnerability could impact web browsers using WebRTC, including but not limited to Google Chrome.

Weakness type: CWE-787.

Product: Google Chromium WebRTC · Assigned by: Chrome · Published: 2023-12-21

Affected and fixed versions

VendorProductAffected versions (per CVE record)
GoogleChrome120.0.6099.129 < 120.0.6099.129

Severity scores

Scored byCVSSScoreVector
CISA-ADP3.18.8 HighCVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
  • Attack vector: network (remotely reachable)
  • Attack complexity: low
  • Privileges required: none (no login)
  • User interaction: required (a user must click/open something)
  • Scope: unchanged

CVSS measures how bad a flaw is if exploited, not how likely exploitation is. Read it next to the exploitation data below.

Exploitation and urgency

  • CISA KEV: added 2024-01-02; federal due date 2024-01-23. Known ransomware use: Unknown.
  • CISA required action: Apply mitigations per vendor instructions or discontinue use of the product if mitigations are unavailable.
  • CISA SSVC assessment: exploitation active, automatable no, technical impact total.
  • FIRST EPSS (model of 2026-10-21): 6.67% probability of exploitation activity in the next 30 days; percentile 94.

Timeline

  • — CVE record published by Chrome
  • — Added to CISA’s Known Exploited Vulnerabilities catalog
  • — CISA remediation deadline for US federal agencies
  • — CVE record last updated

Sources and references

Original sources first. Version and fix details should always be confirmed against the vendor or project advisory.

Vendor and project advisories, patches

  1. Listed in CISA KEV notes (chromereleases.googleblog.com) chromereleases.googleblog.com

Vulnerability records

  1. CVE.org record CVE-2023-7024 cve.org
  2. NVD entry CVE-2023-7024 nvd.nist.gov

Government

  1. CISA Known Exploited Vulnerabilities catalog entry cisa.gov

Other references from the CVE record and advisory

  1. crbug.com crbug.com
  2. debian.org debian.org
  3. lists.fedoraproject.org lists.fedoraproject.org
  4. lists.fedoraproject.org lists.fedoraproject.org
  5. security.gentoo.org security.gentoo.org

All exploited Google vulnerabilities · Today’s Security Digest