Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
🐹
🐹 Go
Not in CISA KEV
CRITICAL severity

GHSA-v9j4-cp63-qv62

CRITICALFix: gen2brain/go-unarr@239ec40

GHSA-v9j4-cp63-qv62 is a critical-severity (CVSS 9.8) Path Traversal vulnerability in github.com/gen2brain/go-unarr. 1 public exploit reference exists, so weaponization risk is real. O3 Security confirms whether GHSA-v9j4-cp63-qv62 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

Tarslip in go-unarr

Also known asCVE-2021-38197GO-2022-0929
Published
Sep 1, 2021
Updated
Aug 21, 2024
Affected
1 pkg
Patched
1 / 1
Exploits
1 known
Exploitation data as of Aug 21, 2024 · OSV.dev, NVD, FIRST.org (EPSS)

Real-World Exposure

1 pkg affected
🐹github.com/gen2brain/go-unarr

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

unarr.go in go-unarr (aka Go bindings for unarr) 0.1.1 allows Directory Traversal via ../ in a pathname within a TAR archive.

Affected Packages

1 total 1 fixed
EcosystemPackageVulnerable rangeFix
🐹Gogithub.com/gen2brain/go-unarrall versions0.1.4
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/gen2brain/go-unarr. 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/gen2brain/go-unarr to 0.1.4 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-v9j4-cp63-qv62 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-v9j4-cp63-qv62 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-v9j4-cp63-qv62. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

unarr.go in go-unarr (aka Go bindings for unarr) 0.1.1 allows Directory Traversal via ../ in a pathname within a TAR archive.
O3 Security · Impact-Aware SCA

Is GHSA-v9j4-cp63-qv62 in your dependencies?

O3 detects GHSA-v9j4-cp63-qv62 across Go dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

GHSA-v9j4-cp63-qv62: Tarslip in go-unarr… | O3 Security