Skip to main content
No exploitation reportedFix available

CVE-2020-29529

No exploitation reported by the sources we read.

  • Published2020-12-03
  • Fixed in0.5.0
  • WeaknessCWE-22 · CWE-59

Am I affected?

With a domain, we read the version its public headers and pages expose. A distribution build can carry the fix under an older number.

Description

HashiCorp go-slug up to 0.4.3 did not fully protect against directory traversal while unpacking tar archives, and protections could be bypassed with specific constructions of multiple symlinks. Fixed in 0.5.0.

Timeline

dates in UTC
  1. 2020-12-0320:15CVE publishedNVD

Versions per branch

NVD · OSV
Hashicorp go-slug
BranchAffectedFixed in
0.5< 0.5.00.5.0

as publishedRanges as NVD and OSV publish them; a distribution’s build can be fixed under an older number.

Distribution builds and vendor advisories

Packages from OSV.dev and products from the vendors' CSAF advisories.

version not verifiedVersions not verified: read as OSV.dev and the vendors publish them, not checked against each vendor's release list.

Packages

  • golang-github-hashicorp-go-slugDebian:12all versions · fixed in 0.5.0-1

Vendor advisories

  • CVE-2020-29529 Red Hat Product Security2 known affected

    go-slug: partial protection against zip slip attacks

    rhacm2/multicloud-manager-rhel8 as a component of Red Hat Advanced Cluster Management for Kubernetes 2 · rhacm2/openshift-hive-rhel8 as a component of Red Hat Advanced Cluster Management for Kubernetes 2

  • RHSA-2021:1168 Red Hat Product Security77 products fixed

    Red Hat Security Advisory: Red Hat Advanced Cluster Management 2.2.2 security and bug fix update

Full record on NVD

Fix

  1. Update Hashicorp go-slug to 0.5.0
  2. Vendor fix Red Hat Product Security RHSA-2021:1168 · 77 productsFor details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258
  3. No fix available, says the vendor Red Hat Product Security CVE-2020-29529 · 2 productsAffected

Advisories and patches

Detection

Nuclei template
none so far
ProjectDiscovery
Exploit-DB
no entry
Exploit-DB
Proof of concept
Metasploit modules
none listed
Metasploit Framework

Sources

  • NVDCVSS 3.17.5read 2026-10-23
  • NVDCVSS 2.05read 2026-10-23
  • NVDweakness (CWE)CWE-22, CWE-59read 2026-10-23
  • FIRST EPSSEPSS score2.8 %2026-11-08
  • OSVaffected packages—
  • GitHub AdvisoriesadvisoryHIGH2023-02-06

Identifiers

Technical details

CVSS v3 Vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
Published
2020-12-03
Last Modified
2026-06-17
NVD status
Modified
GitHub Advisory
GHSA-2g5j-5x95-r6hr

Frequently asked questions

What is CVE-2020-29529?

HashiCorp go-slug up to 0.4.3 did not fully protect against directory traversal while unpacking tar archives, and protections could be bypassed with specific constructions of multiple symlinks. Fixed in 0.5.0.

Is CVE-2020-29529 actively exploited?

Active exploitation of CVE-2020-29529 has not been confirmed. Its EPSS score was 2.8% on 2026-11-08, the estimated probability of exploitation in the next 30 days.

What is the CVSS score for CVE-2020-29529?

CVE-2020-29529 has a CVSS v3 base score of 7.5 (HIGH severity), with vector string CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N.

Running hashicorp/go-slug? Hear about its next vulnerability

Surveillance reads the versions in your stack — a domain, a lockfile or a list — checks each CVE against the ranges its sources publish, and alerts you when one you run is exploited or enters CISA KEV. A version it cannot read stays « version not verified ».

Get alerts for this productCISA KEV additions, November 2026Search CVEs

No credit card required · No monthly cap on website lookups · 250 API requests/month

Go further

Related vulnerabilities

Same product first, then the same vendor advisory and the same publication week.

Back to CVE Database

Sources for this record