Application crash via empty RIFF chunk vector
Published May 22, 2025 · Updated Jan 24, 2026
NULL pointer dereference in TagLib before 2.0 allows attackers to crash a tag-writing application via a crafted WAV file. During tag saving, RIFF::File::removeChunk removes the sole valid id3 chunk, and updateGlobalSize calls vector::front() on the emptied chunk vector. The file must reach a consumer that writes its tags; the demonstrated consequence is a one-time process crash after the input is overwritten.
Summary
What happened
NULL pointer dereference in TagLib before 2.0 allows attackers to crash a tag-writing application via a crafted WAV file. During tag saving, RIFF::File::removeChunk removes the sole valid id3 chunk, and updateGlobalSize calls vector::front() on the emptied chunk vector. The file must reach a consumer that writes its tags; the demonstrated consequence is a one-time process crash after the input is overwritten.
The record
- CVE
- CVE-2023-47466
- Published
- May 22, 2025
- Updated
- Jan 24, 2026
- Vendor
- TagLib
- Product
- TagLib
- Classifications
- CWE-476, T1499.004
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- May 22, 2025CVE publishedPublication date reported by the CVE source.
- Jan 24, 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=0 <2.0
What conditions does exploitation require?
What is affected?
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
- Crafted WAV proof-of-concept filesproof 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