Skip to content
Fencer Intel
high 8.8

CVE-2023-5996 json

Use after free in WebAudio in Google Chrome prior to 119.0.6045.123 allowed a remote attacker to potentially exploit heap corruption via a…

published 3y ago modified 4mo ago also EUVD-2023-58263

cvss
8.8
version 3.1, NVD
cisa kev
Not listed
not in CISA's catalog
epss
1.9%
EPSS 1.9% chance of exploitation in 30 days, percentile 80%
public exploits
0
none known

Summary

Use after free in WebAudio in Google Chrome prior to 119.0.6045.123 allowed a remote attacker to potentially exploit heap corruption via a crafted HTML page. (Chromium security severity: High)

Patch / fix

  • google chrome 119.0.6045.123
  • chromium Debian 12 119.0.6045.123-1~deb12u1
  • chromium Debian 14, Debian 13 119.0.6045.123-1

debian advisories DEBIAN-CVE-2023-5996

  • chromium openSUSE Tumbleweed 119.0.6045.123-1.1
  • chromium Package Hub 15 SP5, Package Hub 15 SP4, openSUSE Leap 15.5 +1 more 119.0.6045.123-bp155.2.55.1
  • gn Package Hub 15 SP5, Package Hub 15 SP4, openSUSE Leap 15.5 +1 more 0.20231023-bp155.5.3.1

opensuse advisories openSUSE-SU-2024:13419-1openSUSE-SU-2024:13423-1openSUSE-SU-2023:0368-1

  • qt5-qtwebengine Alpine 3.18 5.15.13-r11
  • qt5-qtwebengine Alpine 3.23, Alpine 3.22, Alpine 3.21 +2 more 5.15.15-r7
  • qt6-qtwebengine Alpine 3.24, Alpine 3.23, Alpine 3.22 +3 more 6.6.0-r5

alpine advisories ALPINE-CVE-2023-5996

Alpine secdb © Alpine Linux, from https://secdb.alpinelinux.org via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0

Is CVE-2023-5996 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Exploit prediction

1.93% chance of exploitation in the next 30 days, higher than 80% of all scored CVEs (FIRST EPSS, 2026-11-15).

CVSS scores

assigned by version score vector
NVD 3.1 8.8 CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

Affected products

  • Google Chrome

Classification

Weakness
Technology feeds

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.