rpm package
opensuse/cpio&distro=openSUSE Tumbleweed
pkg:rpm/opensuse/cpio&distro=openSUSE%20Tumbleweed
Vulnerabilities (10)
| CVE | Sev | CVSS | KEV | Affected versions | Fixed in | Published | Description |
|---|---|---|---|---|---|---|---|
| CVE-2026-66486 | Med | — | < 2.15-8.1 | 2.15-8.1 | Aug 10, 2026 | GNU cpio is vulnerable to improper encoding or escaping of output in its archive member listing functionality. When listing archive members via cpio -it, member names are printed directly to output without quoting or escaping. An attacker can craft a cpio archive containing membe | |
| CVE-2026-66485 | Med | — | < 2.15-8.1 | 2.15-8.1 | Aug 10, 2026 | GNU cpio is vulnerable to an uncontrolled memory allocation in the make_path function at src/makepath.c. The function uses alloca to allocate stack memory based on the length of argpath, which is derived from an archive-controlled pathname during extraction. A malicious cpio arch | |
| CVE-2026-66484 | Med | — | < 2.15-8.1 | 2.15-8.1 | Aug 10, 2026 | GNU cpio contains a Path Traversal vulnerability in its tar archive extraction functionality. When extracting a tar archive in copy-in mode with the --no-absolute-filenames option, the extracted file name is normalized but the tar hard-link target is passed to the link_to_name fu | |
| CVE-2023-7207 | Med | 4.9 | < 2.15-1.1 | 2.15-1.1 | Feb 29, 2024 | Debian's cpio contains a path traversal vulnerability. This issue was introduced by reverting CVE-2015-1197 patches which had caused a regression in --no-absolute-filenames. Upstream has since provided a proper fix to --no-absolute-filenames. | |
| CVE-2021-38185 | Hig | 7.8 | < 2.13-3.3 | 2.13-3.3 | Aug 8, 2021 | 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. NOTE: it is unclear whether there are common cases where the pattern file, associated with th | |
| CVE-2019-14866 | Hig | 7.3 | < 2.13-3.3 | 2.13-3.3 | Jan 7, 2020 | In all versions of cpio before 2.13 does not properly validate input files when generating TAR archives. When cpio is used to create TAR archives from paths an attacker can write to, the resulting archive may contain files with permissions the attacker did not have or in paths he | |
| CVE-2016-2037 | Med | 6.5 | < 2.12-3.90 | 2.12-3.90 | Feb 22, 2016 | 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. | |
| CVE-2015-1197 | — | < 2.13-3.3 | 2.13-3.3 | Feb 19, 2015 | 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. | ||
| CVE-2014-9112 | — | < 2.12-3.90 | 2.12-3.90 | Dec 2, 2014 | 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. | ||
| CVE-2010-0624 | — | < 2.12-3.90 | 2.12-3.90 | Mar 15, 2010 | 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 corruption) or possibly execute arbitrary code by sending more da |
- affected < 2.15-8.1fixed 2.15-8.1
GNU cpio is vulnerable to improper encoding or escaping of output in its archive member listing functionality. When listing archive members via cpio -it, member names are printed directly to output without quoting or escaping. An attacker can craft a cpio archive containing membe
- affected < 2.15-8.1fixed 2.15-8.1
GNU cpio is vulnerable to an uncontrolled memory allocation in the make_path function at src/makepath.c. The function uses alloca to allocate stack memory based on the length of argpath, which is derived from an archive-controlled pathname during extraction. A malicious cpio arch
- affected < 2.15-8.1fixed 2.15-8.1
GNU cpio contains a Path Traversal vulnerability in its tar archive extraction functionality. When extracting a tar archive in copy-in mode with the --no-absolute-filenames option, the extracted file name is normalized but the tar hard-link target is passed to the link_to_name fu
- affected < 2.15-1.1fixed 2.15-1.1
Debian's cpio contains a path traversal vulnerability. This issue was introduced by reverting CVE-2015-1197 patches which had caused a regression in --no-absolute-filenames. Upstream has since provided a proper fix to --no-absolute-filenames.
- affected < 2.13-3.3fixed 2.13-3.3
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. NOTE: it is unclear whether there are common cases where the pattern file, associated with th
- affected < 2.13-3.3fixed 2.13-3.3
In all versions of cpio before 2.13 does not properly validate input files when generating TAR archives. When cpio is used to create TAR archives from paths an attacker can write to, the resulting archive may contain files with permissions the attacker did not have or in paths he
- affected < 2.12-3.90fixed 2.12-3.90
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.
- CVE-2015-1197Feb 19, 2015affected < 2.13-3.3fixed 2.13-3.3
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.
- CVE-2014-9112Dec 2, 2014affected < 2.12-3.90fixed 2.12-3.90
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.
- CVE-2010-0624Mar 15, 2010affected < 2.12-3.90fixed 2.12-3.90
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 corruption) or possibly execute arbitrary code by sending more da