Skip to main content
CVE-2023-47212VulnerabilityPublished Updated

CVE-2023-47212: stb_vorbis.c · Integer Overflow or Wraparound

Affects stb_vorbis.cSource CVE Database V5

0

Not known to be exploited · CVSS 9.8 Critical.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 3.1 base score
9.8Critical
How severe the flaw is on the 0–10 CVSS scale.
EPSS
1.4% chance of exploitation in 30 days – higher than 72% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 1 May 2024

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-25.

What to do

Affected software

ProductAffectedFixed in
stb stb_vorbis.cAffected
  • =1.22
Fixed in–

AI-suggested

1. Monitor for official patches or updates from the stb project and apply them immediately once released. 2. Until a patch is available, implement strict input validation and sanitization on all .ogg files before processing, including size and comment field length checks. 3. Employ runtime protections such as heap canaries, address space layout randomization (ASLR), and control flow integrity (CFI) to mitigate exploitation impact. 4. Use application-layer sandboxing or containerization to isolate processes handling untrusted multimedia content. 5. Conduct code audits and static analysis on any custom integrations of stb_vorbis.c to identify and remediate unsafe parsing logic. 6. Restrict or monitor the ingestion of .ogg files from untrusted sources, especially in automated processing pipelines. 7. Update incident response plans to include detection and mitigation strategies for exploitation attempts involving malformed audio files. 8. Collaborate with vendors and supply chain partners to ensure they are aware of the vulnerability and have mitigation plans in place.

Description

A heap-based buffer overflow vulnerability exists in the comment functionality of stb _vorbis.c v1.22. A specially crafted .ogg file can lead to an out-of-bounds write. An attacker can provide a malicious file to trigger this vulnerability.

References

Community reviews

Loading reviews…