Cpio vulnerabilitiesRanked by how likely they are to be used.
Cpio is made by Gnu. We track 12 published vulnerabilities in it, across 16 versions. None of them is on the list of flaws known to be exploited today. If you run Cpio, keep it on a version the vendor still supports.
We keep watching the known-exploited list.
Which Cpio vulnerabilities are being exploited?
This is the list that matters most: flaws criminals are using now.
None of Cpio's published vulnerabilities is on the list of flaws known to be exploited today. We keep watching that list.
Which Cpio flaws are most likely to be used?
Ranked by the latest exploit-likelihood forecast: the chance each flaw is used in an attack in the next 30 days. A high severity score on its own doesn't tell you that. Flaws shared by many other makers' products are left out.
- 7.1%CVE-2014-9112Medium
Heap-based buffer overflow in the process_copy_in function in GNU Cpio 2.11 allows remote attackers to cause a denial of service via a large block value in a cpio archive.
- 5.5%CVE-2016-2037Medium
The cpio_safer_name_suffix function in util.c in cpio 2.11 allows remote attackers to cause a denial of service (out-of-bounds write) via a crafted cpio file.
- 4.7%CVE-2010-0624Medium
Heap-based buffer overflow in the rmt_read__ function in lib/rtapelib.c in the rmt client functionality in GNU tar before 1.23 and GNU cpio before 2.11 allows remote rmt servers to cause a denial of service (memory...
- 4.2%CVE-2021-38185High
GNU cpio through 2.13 allows attackers to execute arbitrary code via a crafted pattern file, because of a dstring.c ds_fgetstr integer overflow that triggers an out-of-bounds heap write.
- 2.9%CVE-2010-4226High
cpio, as used in build 2007.05.10, 2010.07.28, and possibly other versions, allows remote attackers to overwrite arbitrary files via a symlink within an RPM package archive.
- 2.9%
cpio 2.11, when using the --no-absolute-filenames option, allows local users to write to arbitrary files via a symlink attack on a file in an archive.
- 2.1%CVE-2005-1229Medium
Directory traversal vulnerability in cpio 2.6 and earlier allows remote attackers to write to arbitrary directories via a ..
- 0.9%CVE-2023-7207Medium
Debian's cpio contains a path traversal vulnerability.
- 0.9%CVE-2023-7216Medium
A path traversal vulnerability was found in the CPIO utility.
- 0.7%CVE-2019-14866High
In all versions of cpio before 2.13 does not properly validate input files when generating TAR archives.
Running Cpio? We'll keep checking.
Looking flaws up one at a time doesn't scale. Tell us what you run once, and we tell you which flaws matter to you, in what order, and keep watching for new ones.
- Tell us what you runPick your software from a list, or let us work it out from your website.
- We match it to every flawOver 400,000 published flaws, checked against your list.
- Ranked by real-world riskA 0 to 100 score, led by evidence criminals are using it.
- Told as soon as we knowAn alert by email, in the app or by webhook to your own tools.
Free plan, no card needed. Nothing to install.
1 new flaw affects software Acme tracks
Heap-based buffer overflow in the process_copy_in function in GNU Cpio 2.11 allows remote attackers to cause a denial of service via a large block value in a cpio archive.
- Matched to
- Cpio on Acme's software list
- What to do
- Plan in the vendor’s update
Sent to the alert recipients Acme chose. Also in the app and to Acme's webhook.
We track 12 published vulnerabilities listed under the name Cpio, across 16 versions.
None of Cpio's vulnerabilities is on the list of flaws known to be exploited today.
Create a Precursor Intelligence account and track Cpio. We match it against every published flaw, give each one a risk score from 0 to 100 and keep watching, so you hear about new ones as soon as we know, by email, in the app or by webhook.