LiveActive security incident?Get immediate response
CVE Record

CVE-2020-7667: Arbitrary File Write via Archive Extraction (Zip Slip)

In package github.com/sassoftware/go-rpmutils/cpio before version 0.1.0, the CPIO extraction functionality doesn't sanitize the paths of the archived files for leading and non-leading ".." which leads in file extraction outside of the current directory. Note: the fixing commit was applied to all affected versions which were re-released.

HighCVSS 7.5Not KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

Software using this Go CPIO extraction package could be tricked into writing archived files outside the intended folder. The business risk is unauthorized file modification if the application processes attacker-controlled archives.

Executive priority

Treat as high priority where the library handles untrusted archives. Prioritize internet-facing upload or ingestion workflows first. If the package is not present or only trusted archives are processed, urgency is lower.

Technical view

CVE-2020-7667 is a path traversal flaw in github.com/sassoftware/go-rpmutils/cpio before 0.1.0. The extractor did not sanitize leading or embedded '..' paths, allowing archive entries to be written outside the extraction directory. CVSS 3.1 is 7.5 with high integrity impact.

Likely exposure

Exposure is likely limited to Go applications, services, or tools that depend on github.com/sassoftware/go-rpmutils/cpio and extract CPIO/RPM archive content, especially from uploads, feeds, or other untrusted sources.

Exploitation context

The provided sources do not show CISA KEV listing or active exploitation. Exploitation depends on a vulnerable application extracting a crafted archive. The sources support arbitrary file write, but do not prove code execution.

Researcher notes

This is a Zip Slip-style arbitrary file write in archive extraction. The source bundle names path sanitization failure and a fixing commit. It does not provide evidence of weaponized exploitation, affected downstream products, or broader impact beyond file write.

Mitigation direction

  • Upgrade github.com/sassoftware/go-rpmutils/cpio to version 0.1.0 or a vendor-released fixed version.
  • Confirm the build uses the fixing commit or a release containing it.
  • Avoid extracting untrusted archives until the dependency is fixed.
  • Follow vendor guidance if pinned or re-released versions differ in your build system.

Validation and detection

  • Check Go dependency manifests for github.com/sassoftware/go-rpmutils/cpio.
  • Identify application paths that extract CPIO or RPM archive content.
  • Confirm deployed artifacts include the fixed dependency version or commit.
  • Verify extraction tests reject paths containing leading or embedded '..'.
Prepared
Confidence
high
Sources
4

Public sources used

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.

description · low confidence lookup

File access behavior lookup

The CVE wording references file access or upload behavior, so file telemetry and web shell review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2020-7667 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
High
CVSS
7.5 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N

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
3Source 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
7.5CVSS 3.1HighCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N3.93.6Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

7.5High
CVSS 3.1 vector shape for CVE-2020-7667Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N

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

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/agithub.com/sassoftware/go-rpmutils/cpiounspecifiedListed
Weakness

CWE details

No CWE listed

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