Vulnerability in HashiCorp go-slug (CVE-2020-29529)

Summary

Vulnerability in HashiCorp go-slug (CVE-2020-29529). Confidential information can be exposed externally. Mitigation: upgrade to 0.5.0 or later.

Original description

The description as published by the source.

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.

Source: OSV.dev (Open Source Vulnerabilities) NVD GitHub Advisory OSV

Auto-generated summary

Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.

A vulnerability tracked as CVE-2020-29529 has been found in HashiCorp go-slug.
Confidential information can be exposed externally.
What to do: upgrade HashiCorp go-slug to 0.5.0 or later.
If unsure, ask your IT team or search "HashiCorp go-slug CVE-2020-29529" on the vendor's site.

CVE-2020-29529 (HashiCorp go-slug)
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Patched: 0.5.0 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.

❓ What is the problem

A vulnerability (unclassified) exists in HashiCorp go-slug.

📍 Affected scope

Check the vendor advisory for the affected versions of HashiCorp go-slug.

🔥 Severity

Severity: ?. Confidential information can be exposed externally.

🔧 How to fix

Update to 0.5.0.

🛡️ Workaround

Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.

🔍 Detection

Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Audit SBOM/dependencies to find affected services.

Response actions

Concrete steps and command examples for SOC/SRE teams to execute in order

1
Identify exposure identify
```
Audit SBOM/dependencies for affected components.
```
資産台帳・SBOM・依存マニフェストで HashiCorp go-slug を使っているサービスとバージョンを洗い出す。
2
Apply patch patch
```
Upgrade HashiCorp go-slug to 0.5.0
```
ステージング環境で 0.5.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
3
Post-deployment verification verify
```
Confirm patched version is live in production
```
パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

Fix status by distribution

Fixed packages published by each distribution for this CVE

Debian DEBIAN-CVE-2020-29529 golang-github-hashicorp-go-slug Fixed in: 0.5.0-1