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

CVE-2022-30323

HIGH

HashiCorp go-getter unsafe downloads could lead to asymmetric resource exhaustion

Published
May 25, 2022
Updated
Mar 14, 2026
Affected
5 pkgs
Patched
5 / 5
Exploits
None indexed

EPSS Exploitation Probability

via FIRST.org ↗
1.3%probability of exploitation in next 30 days
Lower Risk66th percentile+0.49%
0.00%0.59%1.19%1.78%0.4%1.3%Dec 25Apr 26Jun 26

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

Blast Radius

5 pkgs affected
🐹github.com/hashicorp/go-getter🐹github.com/hashicorp/go-getter🐹github.com/hashicorp/go-getter/v2🐹github.com/hashicorp/go-getter/s3/v2🐹github.com/hashicorp/go-getter/gcs/v2

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

go-getter up to 1.5.11 and 2.0.2 panicked when processing password-protected ZIP files. Fixed in 1.6.1 and 2.1.0.

Affected Packages

5 total 5 fixed
EcosystemPackageVulnerable rangeFix
🐹Gogithub.com/hashicorp/go-getterall versions1.6.1
🐹Gogithub.com/hashicorp/go-getter2.0.0&&< 2.1.02.1.0
🐹Gogithub.com/hashicorp/go-getter/v2all versions2.1.0
🐹Gogithub.com/hashicorp/go-getter/s3/v2all versions2.1.0
🐹Gogithub.com/hashicorp/go-getter/gcs/v2all versions2.1.0

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-getter. 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-getter to 1.6.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2022-30323 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 CVE-2022-30323 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 CVE-2022-30323. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

go-getter up to 1.5.11 and 2.0.2 panicked when processing password-protected ZIP files. Fixed in 1.6.1 and 2.1.0.
O3 Security · Impact-Aware SCA

Is CVE-2022-30323 in your dependencies?

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