LiveActive security incident?Get immediate response
CVE Record

CVE-2019-14866: In all versions of cpio before 2.13 does not properly validate input files when generating TAR archives.

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.

MediumCVSS 6.7Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2019-14866 affects cpio before 2.13 when it creates TAR archives from attacker-controlled paths. A low-privileged user could cause the archive to include unexpected paths or permissions. If an administrator later extracts that archive without careful review, the system could be compromised.

Executive priority

Treat this as a targeted operational risk, not an internet-scale emergency. Prioritize systems where cpio is used in backup or packaging workflows involving shared or user-writable directories and privileged extraction.

Technical view

The flaw is improper input validation in cpio TAR archive generation, mapped to CWE-20. It is local, high-complexity, requires low privileges and user interaction, and carries high confidentiality, integrity, and availability impact after privileged extraction. CVSS v3.0 score is 6.7.

Likely exposure

Unix or Linux systems with cpio before 2.13 are most exposed where backup, packaging, restore, CI, or admin workflows archive paths writable by untrusted users and later extract them with elevated privileges.

Exploitation context

The bundle does not show KEV listing or confirmed active exploitation. Practical exploitation depends on attacker write access to archived paths and a privileged user extracting the resulting TAR archive without review.

Researcher notes

Evidence supports affected GNU cpio versions before 2.13 and a local archive-generation abuse path. The source bundle does not provide exploit code, public exploitation confirmation, or product scope beyond cpio and vendor package advisories.

Mitigation direction

  • Upgrade cpio to 2.13 or a vendor-supported patched package.
  • Avoid creating TAR archives from attacker-writable paths with cpio.
  • Do not extract untrusted cpio-produced TAR archives as a privileged user.
  • Review archive paths and permissions before privileged extraction.
  • Check Red Hat, Debian, or OS vendor advisories for package-specific guidance.

Validation and detection

  • Inventory installed cpio versions across Linux and Unix assets.
  • Identify automation that uses cpio to generate TAR archives.
  • Check whether archived source paths are writable by low-privileged users.
  • Review restore and extraction procedures for privileged TAR extraction.
  • Confirm vendor package updates are applied where cpio is present.
Prepared
Confidence
high
Sources
6

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · low confidence lookup

CWE-20: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2019-14866 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Medium
CVSS
6.7 (3.0)
Known Exploited
No
Published

Vector: CVSS:3.0/AV:L/AC:H/PR:L/UI:R/S:U/C:H/I:H/A:H

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
5Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
6.7CVSS 3.0MediumCVSS:3.0/AV:L/AC:H/PR:L/UI:R/S:U/C:H/I:H/A:H0.85.9Primary CVE score

Vulnerability scoring details

Base CVSS 3.0 score

6.7Medium
CVSS 3.0 vector shape for CVE-2019-14866Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.0/AV:L/AC:H/PR:L/UI:R/S:U/C:H/I:H/A:H

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
Red HatcpioAll cpio versions before 2.13Listed
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-20 · source CWE mapping

Improper Input Validation

Improper Input Validation represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.