rpm package
suse/cpio&distro=SUSE Linux Enterprise Server 12 SP5
pkg:rpm/suse/cpio&distro=SUSE%20Linux%20Enterprise%20Server%2012%20SP5
Vulnerabilities (3)
| CVE | Sev | CVSS | KEV | Affected versions | Fixed in | Published | Description |
|---|---|---|---|---|---|---|---|
| CVE-2023-7207 | — | < 2.11-36.18.1 | 2.11-36.18.1 | Jan 5, 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 | — | < 2.11-36.12.1 | 2.11-36.12.1 | Aug 7, 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 | — | < 2.11-36.6.1 | 2.11-36.6.1 | 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-2023-7207Jan 5, 2024affected < 2.11-36.18.1fixed 2.11-36.18.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.
- CVE-2021-38185Aug 7, 2021affected < 2.11-36.12.1fixed 2.11-36.12.1
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-14866Jan 7, 2020affected < 2.11-36.6.1fixed 2.11-36.6.1
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