cpio: improper input validation when writing tar header fields leads to unexpected tar generation
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| Red Hat | cpio | affected |
|
Configuration 1 [-]
|
Configuration 2 [-]
|
| Package | CPE | Advisory | Released Date |
|---|---|---|---|
| Red Hat Enterprise Linux 7 | |||
| cpio-0:2.11-28.el7 | cpe:/o:redhat:enterprise_linux:7 | RHSA-2020:3908 | 2020-09-29T00:00:00Z |
| Red Hat Enterprise Linux 8 | |||
| cpio-0:2.12-10.el8 | cpe:/o:redhat:enterprise_linux:8 | RHSA-2021:1582 | 2021-05-18T00:00:00Z |
| Red Hat Enterprise Linux 8.2 Extended Update Support | |||
| cpio-0:2.12-8.el8_2.1 | cpe:/o:redhat:rhel_eus:8.2 | RHSA-2022:0073 | 2022-01-11T00:00:00Z |
| Red Hat OpenShift Do | |||
| openshiftdo/odo-init-image-rhel7:1.1.3-2 | cpe:/a:redhat:openshift_do:1.0::el7 | RHSA-2021:0949 | 2021-03-22T00:00:00Z |
No data available yet.
| Source | ID | Title |
|---|---|---|
Debian DLA |
DLA-1981-1 | cpio security update |
Debian DLA |
DLA-3445-1 | cpio security update |
EUVD |
EUVD-2019-5982 | 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 did not have access to. Extracting those archives from a high-privilege user without carefully reviewing them may lead to the compromise of the system. |
Ubuntu USN |
USN-4176-1 | GNU cpio vulnerability |
No CVSS v4.0
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.686% probability within 30 days)
Key SSVC decision points have not yet been added.
No history.