Code execution via pattern-file heap overwrite
Published Aug 7, 2021 · Updated Jun 9, 2025
Integer overflow in GNU cpio 2.13 and earlier allows local users to execute arbitrary code through a crafted -E pattern file. The ds_fgetstr function doubles strsize without checking for integer overflow, passes the wrapped value to ds_resize, and then writes beyond the heap buffer while read_pattern_file consumes attacker-controlled pattern data. Execution requires a victim to invoke cpio with the crafted file through the -E option, and the public proof of concept targets glibc-based cpio 2.13.
Summary
What happened
Integer overflow in GNU cpio 2.13 and earlier allows local users to execute arbitrary code through a crafted -E pattern file. The ds_fgetstr function doubles strsize without checking for integer overflow, passes the wrapped value to ds_resize, and then writes beyond the heap buffer while read_pattern_file consumes attacker-controlled pattern data. Execution requires a victim to invoke cpio with the crafted file through the -E option, and the public proof of concept targets glibc-based cpio 2.13.
The record
- CVE
- CVE-2021-38185
- Published
- Aug 7, 2021
- Updated
- Jun 9, 2025
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-190, T1204.002
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Aug 7, 2021CVE publishedPublication date reported by the CVE source.
- Jun 9, 2025Record 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?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
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.
Public exploit references
- cpiopwn arbitrary-code-execution proof of conceptproof 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