CVE-2020-29529

Exp

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.

Published: 2020-12-03 Last update: 2026-06-16 Assigner: [email protected] Source: [email protected]
NVD Status：Modified，CVE State: published
View at NVD, CVE.org, EUVD

CVE-2020-29529 is rated High Exploit Risk (76.9/100): CVSS High severity, with medium exploitation likelihood (EPSS 2.78%). 1 public exploit reference(s) are indexed (Exploit-DB). EPSS rose +2.34% over the last day, indicating growing attacker interest. Public exploits are available—assess exposure, apply mitigations, and prioritize patching.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

Public exploit references (Exploit-DB) for CVE-2020-29529

EDB-ID Source Kind Published Link
— nvd_ref exploit_tag Exploit-DB ↗

Exploit prediction scoring system (EPSS) score for CVE-2020-29529

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2026-06-15 0.45% 2.78% +2.34%
2 2025-11-21 0.49% 0.45% -0.04%
3 2025-11-18 — 0.49% —

Full EPSS history (16 records total)

Common vulnerability scoring system (CVSS) metrics for CVE-2020-29529

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
7.5 3.1 HIGH
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N Click to expand
Attack vector (AV:N)
Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:N)
No account or special rights needed—anonymous or random user is enough.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:H)
Serious risk that confidential data gets exposed in a big way.
Integrity (I:N)
Data isn’t meaningfully altered or forged.
Availability (A:N)
Service keeps running; no real outage angle.
 3.9 3.6 [email protected]
5.0 2.0 MEDIUM
AV:N/AC:L/Au:N/C:P/I:N/A:N Click to expand
Access vector (AV:N)
Can be exploited remotely over network reachability.
Access complexity (AC:L)
Exploitation conditions are straightforward and predictable.
Authentication (AU:N)
No authentication is required.
Confidentiality impact (C:P)
Partial confidentiality impact.
Integrity impact (I:N)
No integrity impact.
Availability impact (A:N)
No availability impact.
 10.0 2.9 [email protected]

Weakness enumeration for CVE-2020-29529

GitHub Security Advisory for CVE-2020-29529

GHSA-2g5j-5x95-r6hr · Severity: high · Ecosystem: go — Unsafe tar unpacking in HashiCorp go-slug

OS Trackers for CVE-2020-29529

vendor priority summary link
debian not yet assigned CVE-2020-29529 not yet assigned priority: Debian including 1 source packages (golang-github-hashicorp-go-slug), 2 status rows across 2 suites (bookworm, bullseye): resolved 2. https://security-tracker.debian.org/tracker/CVE-2020-29529
redhat medium — https://access.redhat.com/security/cve/CVE-2020-29529
ubuntu low CVE-2020-29529 low priority: Ubuntu including 1 source packages (golang-github-hashicorp-go-slug), 16 status rows across 16 suites (bionic, focal, groovy, hirsute, impish, jammy, kinetic, lunar, mantic, noble, oracular, plucky, questing, trusty, upstream, xenial): DNE 9, ignored 5, not-affected 1, released 1. https://ubuntu.com/security/CVE-2020-29529

Affected software / configurations for CVE-2020-29529

Vendor Product Version Raw CPE
hashicorp go-slug < 0.5.0 cpe:2.3:a:hashicorp:go-slug:*:*:*:*:*:*:*:*

References for CVE-2020-29529

cvelogic Threat Intelligence