cve.bz

CVE-2023-45681 nothings stb vorbis.c: Year 2038 problem, Y2K38, Y2038, Epochalypse

7.8 highEPSS 0.5%

High (7.8) in nothings stb vorbis.c. EPSS 0.5% estimated probability of exploitation activity in the next 30 days.

On this page
stb_vorbis is a single file MIT licensed library for processing ogg vorbis files. A crafted file may trigger memory write past an allocated heap buffer in `start_decoder`. The root cause is a potential integer overflow in `sizeof(char*) * (f->comment_list_length)` which may make `setup_malloc` allocate less memory than required. Since there is another integer overflow an attacker may overflow it too to force `setup_malloc` to return 0 and make the exploit more reliable. This issue may lead to code execution.

Severity

CVSS 3.1

7.8 high
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
EPSS
0.5% (unchanged from 0.5% a week ago; 0.5% 30 days ago) estimated probability of exploitation activity in the next 30 days; 45th percentile. Scored 2026-11-22. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: PoC · Automatable: no · Technical impact: total, assessed 2024-07-11. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWEs
CWE-190 Integer Overflow or Wraparound (Year 2038 problem, Y2K38, Y2038, Epochalypse)
CWE-787 Out-of-bounds Write
Published
Modified
NVD analysis
Analyzed, since modified
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2023-45681 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2023-45681?via=ask-ai-copy and https://cve.bz/cve/CVE-2023-45681?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2023-45681 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the NVD's CPE matches.

ProductAffected
nothings:stb_vorbis.c1.22

Linux distributions

DistributionReleasePackageFixed inAdvisory
Debian12, 13, 14libstbno fix listedDEBIAN-CVE-2023-45681
Ubuntu20.04:LTS, 22.04:LTS, 24.04:LTS and 3 morelibstbno fix listedUBUNTU-CVE-2023-45681
SUSEPackage Hub 15 SP6SDL2_sound2.0.4-bp156.2.3.1openSUSE-SU-2025:0037-1
openSUSELeap 15.6SDL2_sound2.0.4-bp156.2.3.1openSUSE-SU-2025:0037-1
openSUSETumbleweedSDL2_sound2.0.4-1.1openSUSE-SU-2025:14642-1
openSUSETumbleweedSDL3_sound3.2.0-1.1openSUSE-SU-2026:10978-1

From the distributions' data via OSV.dev: the Debian Security Tracker; Ubuntu Security Notices © Canonical Ltd., CC BY-SA 4.0; SUSE security data, CC BY 4.0. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Debian · Ubuntu · SUSE · openSUSE.

Attack patterns (CAPEC)

  • CAPEC-92 Forced Integer Overflow Likelihood: High · Severity: High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON