CVE-2020-29529 json
Unsafe tar unpacking in HashiCorp go-slug
published 5y ago modified 4mo ago also GHSA-2g5j-5x95-r6hr , GO-2021-0094 , EUVD-2023-0600
- cvss
- 7.5
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 2.8%
- EPSS 2.8% chance of exploitation in 30 days, percentile 86%
- public exploits
- 0
- none known
Summary
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.
Patch / fix
- go github.com/hashicorp/go-slug 0.5.0
- hashicorp go-slug 0.5.0
- golang-github-hashicorp-go-slug Debian 12 0.5.0-1
debian advisories DEBIAN-CVE-2020-29529
Is CVE-2020-29529 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerVendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2020-29529 updated cvss 7.5
go-slug: partial protection against zip slip attacks
-
Red Hat Advanced Cluster Management for Kubernetes 2 rhacm2/openshift-hive-rhel8, rhacm2/multicloud-manager-rhel8affected: no fix available
Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf
Exploit prediction
2.82% chance of exploitation in the next 30 days, higher than 86% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- securitylab.github.com https://securitylab.github.com/advisories/GHSL-2020-262-zipslip-go-slug referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.1 | 7.5 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N |
| NVD | 2.0 | 5.0 | AV:N/AC:L/Au:N/C:P/I:N/A:N |
| GitHub | 3.1 | 7.5 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| go | github.com/hashicorp/go-slug | <0.5.0 |
0.5.0 |
Classification
References
-
github.com
/hashicorp/go-slug/pull/12
web, patch, third-party-advisory
-
github.com
/hashicorp/go-slug/compare/v0.4.3...v0.5.0
web, patch, release-notes, third-party-advisory
-
github.com
/hashicorp/go-slug/commit/28cafc59c8da6126a3ae94dfa84181df4073454f
web, patch
-
github.com
/hashicorp/go-slug/commit/764785bc4cbb9e600ad1cf1a6bd21b535c182983
web
-
securitylab.github.com
/advisories/GHSL-2020-262-zipslip-go-slug
advisory, exploit, third-party-advisory, web
-
github.com
/hashicorp/go-slug/releases/tag/v0.5.0
web, release-notes, third-party-advisory
-
nvd.nist.gov
/vuln/detail/CVE-2020-29529
advisory
-
github.com
/hashicorp/go-slug
package
-
pkg.go.dev
/vuln/GO-2021-0094
web
Sources
- CVE List CVE-2020-29529
- GitHub Advisory GHSA-2g5j-5x95-r6hr
- NVD CVE-2020-29529
- OSV GO-2021-0094
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.