BlackTreeCVE IntelligenceRed Hat · cpio
Official source article: Siemens SSA-202008 ↗. Check the applicable product and release in the original source.
High technical severity with public exploit material referenced by a structured source; prioritise exposed affected systems while verifying vendor guidance. Verified remediation exists for at least one product or source, but 11 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.
Verified remediation exists for at least one product or source, but 11 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.
Alpine, Debian findings are scoped to the named distribution, release and source package. An absent finding does not mean a package is unaffected.
A published vendor fix does not prove that a matching update is enabled and installable on a particular asset. Confirm the local package candidate before scheduling remediation.
| Distribution release | Source package | Vendor state | Fixed version | Evidence |
|---|---|---|---|---|
| Alpine v3.23v3.23 · community | cpio | Vendor fix publishedAlpine records a security fix at this version. An absent entry does not mean the package is unaffected. | 2.13-r0 | Alpine Security Database ↗Source updated 22 Oct 2026 |
| Alpine v3.22v3.22 · community | cpio | Vendor fix publishedAlpine records a security fix at this version. An absent entry does not mean the package is unaffected. | 2.13-r0 | Alpine Security Database ↗Source updated 22 Oct 2026 |
| Alpine v3.21v3.21 · community | cpio | Vendor fix publishedAlpine records a security fix at this version. An absent entry does not mean the package is unaffected. | 2.13-r0 | Alpine Security Database ↗Source updated 22 Oct 2026 |
| Debian trixietrixie · source | cpio | Vendor fix publishedDebian records a fixed source-package version for this release. | 2.13+dfsg-1 | Debian Security Tracker ↗Source updated 24 Oct 2026 |
| Debian bookwormbookworm · source | cpio | Vendor fix publishedDebian records a fixed source-package version for this release. | 2.13+dfsg-1 | Debian Security Tracker ↗Source updated 24 Oct 2026 |
| Debian forkyforky · source | cpio | Vendor fix publishedDebian records a fixed source-package version for this release. | 2.13+dfsg-1 | Debian Security Tracker ↗Source updated 24 Oct 2026 |
| Debian sidsid · source | cpio | Vendor fix publishedDebian records a fixed source-package version for this release. | 2.13+dfsg-1 | Debian Security Tracker ↗Source updated 24 Oct 2026 |
Structured product status and remediation from the issuing vendor. Product-state explanations are always visible; large lists can be searched or downloaded.
The vendor explicitly identifies these products as affected by this CVE.
The vendor explicitly identifies these products as affected by this CVE.
High technical severity with public exploit material referenced by a structured source; prioritise exposed affected systems while verifying vendor guidance. Verified remediation exists for at least one product or source, but 11 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.
Fix availability varies by productIn 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.
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.
The product receives input or data, but it does not validate or incorrectly validates that the input has the properties that are required to process the data safely and correctly.
An attacker operating through local access may attempt exploitation with low privileges. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.
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.
The product receives input or data, but it does not validate or incorrectly validates that the input has the properties that are required to process the data safely and correctly.
An attacker operating through local access may attempt exploitation with low privileges. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.
CVSS severity, EPSS forecast probability, public exploit material and CISA-confirmed exploitation are separate signals.
No CISA KEV match was present at the last successful refresh. This means no confirmation from that source, not proof of no exploitation.
A structured CVE source labels at least one public reference as exploit material. BlackTree has not independently validated that it is safe, reliable or weaponised.
CWE-20: Improper Input Validation. The product receives input or data, but it does not validate or incorrectly validates that the input has the properties that are required to process the data safely and correctly.
CVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:HCommon Vulnerability Scoring System 3.1: the compact vector below is decoded into plain language.
Operational remediation based on structured source evidence.
Published 7 Jan 2020 · Last source change 13 Feb 2025, 16:27 UTC · CWE-20 · Improper Input Validation
Core structured fields are present and their contributing authorities are shown above.