Application crash via overflowing WARC content length
Published Jun 9, 2025 · Updated Sep 1, 2026
Integer overflow in libarchive before 3.8.0 allows context-dependent attackers to crash applications via a crafted WARC file. The WARC reader adds four separator bytes to an untrusted content length in one signed operation and ignores a failed skip, so content meant to be discarded can be parsed as a new entry. Exploitation requires a local user or automated system to process the file; the demonstrated consequence is a consumer-process crash.
Summary
What happened
Integer overflow in libarchive before 3.8.0 allows context-dependent attackers to crash applications via a crafted WARC file. The WARC reader adds four separator bytes to an untrusted content length in one signed operation and ignores a failed skip, so content meant to be discarded can be parsed as a new entry. Exploitation requires a local user or automated system to process the file; the demonstrated consequence is a consumer-process crash.
The record
- CVE
- CVE-2025-5916
- Published
- Jun 9, 2025
- Updated
- Sep 1, 2026
- Vendor
- 389 Directory Server
- Product
- Red Hat Enterprise Linux 10
- Classifications
- CWE-190, T1204.002
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Jun 9, 2025CVE publishedPublication date reported by the CVE source.
- Sep 1, 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?
Affected versions are unavailable in this record. Check the vendor advisory for version and patch details.
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
No public exploit references are available in this record.
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