CVE-2023-0475
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedHashiCorp go-getter up to 1.6.2 and 2.1.1 is vulnerable to decompression bombs. Fixed in 1.7.0 and 2.2.0.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceThe go-getter library used by HashiCorp products is vulnerable to decompression bomb attacks (zip bombs). Attackers can craft malicious compressed archives that expand to enormous sizes when decompressed, potentially causing denial of service by exhausting memory or disk space. The library processes compressed files without proper limits on decompression ratios.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data<= 1.6.2= 2.1.1CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify go-getter as a dependencyInspect your project's go.mod file for 'github.com/hashicorp/go-getter' or check vendor/ directory for the go-getter package. HashiCorp tools like Terraform, Vault, or Consul include this library.Affected if go-getter is present as a dependency in your project
-
Determine the installed go-getter versionRun 'go list -m github.com/hashicorp/go-getter' or check the version line in go.mod. Compare the version number against the affected ranges: <= 1.6.2 or = 2.1.1Affected if The installed version is 1.6.2 or lower, or exactly 2.1.1
-
Verify if your application fetches or processes remote resourcesSearch source code for usage of go-getter functions such as 'get.Get', 'get.GetAny', or client calls that retrieve archives from URLs, S3, or other remote sources.Affected if Your code uses go-getter to fetch archives from remote or untrusted sources
-
Confirm the application handles compressed archivesReview whether the fetched resources include compressed file types (zip, tar.gz, tgz, bz2) that would be decompressed by go-getter during retrieval.Affected if The application decompresses archives retrieved via go-getter without external limits
You are affected if your project depends on go-getter version 1.6.2 or lower, or exactly 2.2.1, and your application uses that library to fetch or decompress archives from remote or untrusted sources.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scopedUpgrade go-getter to version 1.7.0 or 2.2.0 or later to implement decompression limits. Review any code that uses go-getter to ensure it handles resource fetching safely.
1.7.0 (for 1.x line) or 2.2.0 (for 2.x line)
- Identify which version line (1.x or 2.x) of go-getter is currently in use
- For 1.x users: upgrade go-getter to version 1.7.0
- For 2.x users: upgrade go-getter to version 2.2.0
- Verify the upgrade was successful by checking the installed version
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation1.0 h
- Implementation1.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,376.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-0475 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2023-0475 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data