Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
🐹 Go

GHSA-2g5j-5x95-r6hr

HIGH

GHSA-2g5j-5x95-r6hr is a high-severity (CVSS 7.5) Path Traversal vulnerability in github.com/hashicorp/go-slug. 1 public exploit reference exists, so weaponization risk is real. O3 Security confirms whether GHSA-2g5j-5x95-r6hr is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

Unsafe tar unpacking in HashiCorp go-slug

Also known asCVE-2020-29529GO-2021-0094
Published
Feb 6, 2023
Updated
Nov 8, 2023
Affected
1 pkg
Patched
1 / 1
Exploits
1 known

Blast Radius

1 pkg affected
🐹github.com/hashicorp/go-slug

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Go packages — download data is not available via public APIs for these ecosystems.

Description

HashiCorp go-slug before 0.5.0 does not address attempts at directory traversal involving ../ and symlinks.

Affected Packages

1 total 1 fixed
EcosystemPackageVulnerable rangeFix
🐹Gogithub.com/hashicorp/go-slugall versions0.5.0
Exploits & PoCs
1

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

Detection & mitigation playbook

Open-source dependency
  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/hashicorp/go-slug. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

  2. Fix

    Update github.com/hashicorp/go-slug to 0.5.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-2g5j-5x95-r6hr is resolved across your whole dependency graph.

  3. Workarounds

    If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

  4. How O3 protects you

    O3 pinpoints whether GHSA-2g5j-5x95-r6hr is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to GHSA-2g5j-5x95-r6hr. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

HashiCorp go-slug before 0.5.0 does not address attempts at directory traversal involving ../ and symlinks.
O3 Security · Impact-Aware SCA

Is GHSA-2g5j-5x95-r6hr in your dependencies?

O3 detects GHSA-2g5j-5x95-r6hr across Go dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.