Code execution via undersized Joliet filename buffer
Published Jun 14, 2024 · Updated Jan 20, 2026
Stack-based buffer overflow in GNU Project libcdio 2.2.0 allows local users to execute arbitrary code via a crafted ISO 9660 image. The _iso9660_dir_to_statbuf function sizes a UTF-8 filename buffer from the two-byte Joliet UCS-2 input even though each converted character can require three bytes. Exploitation requires an affected application to parse attacker-controlled Joliet filenames, and successful overflow executes code in that application's context.
Summary
What happened
Stack-based buffer overflow in GNU Project libcdio 2.2.0 allows local users to execute arbitrary code via a crafted ISO 9660 image. The _iso9660_dir_to_statbuf function sizes a UTF-8 filename buffer from the two-byte Joliet UCS-2 input even though each converted character can require three bytes. Exploitation requires an affected application to parse attacker-controlled Joliet filenames, and successful overflow executes code in that application's context.
The record
- CVE
- CVE-2024-36600
- Published
- Jun 14, 2024
- Updated
- Jan 20, 2026
- Vendor
- GNU Project
- Product
- libcdio
- Classifications
- CWE-121, T1203
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jun 14, 2024CVE publishedPublication date reported by the CVE source.
- Jan 20, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=2.1.0
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- PoC-libcdio-bof.isoproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo