Memory corruption via ustar pathname off-by-one
Published Jun 9, 2025 · Updated Sep 1, 2026
Out-of-bounds write in libarchive before 3.8.0 allows local users to corrupt memory when a crafted pathname is archived. build_ustar_entry_name permits trailing slashes to extend both pathname regions to 156 and 100 bytes, then writes a terminating NUL past the 256-byte buffer. Triggering requires an archive operation on an attacker-controlled pathname; the overflow corrupts adjacent memory, producing unpredictable behavior or a crash.
Summary
What happened
Out-of-bounds write in libarchive before 3.8.0 allows local users to corrupt memory when a crafted pathname is archived. build_ustar_entry_name permits trailing slashes to extend both pathname regions to 156 and 100 bytes, then writes a terminating NUL past the 256-byte buffer. Triggering requires an archive operation on an attacker-controlled pathname; the overflow corrupts adjacent memory, producing unpredictable behavior or a crash.
The record
- CVE
- CVE-2025-5917
- Published
- Jun 9, 2025
- Updated
- Sep 1, 2026
- Vendor
- 389 Directory Server
- Product
- Red Hat Enterprise Linux 10
- Classifications
- CWE-787
- 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
- Upstream bsdtar trailing-slash reproducerproof 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