CVE-2022-30323
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 · uneditedgo-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.
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 · moderate confidencego-getter library versions 1.5.11 and earlier and 2.0.2 and earlier contain a denial-of-service vulnerability where processing password-protected ZIP files triggers a panic (unhandled runtime error), causing the application to crash. An attacker could exploit this by supplying specially crafted ZIP files.
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.5.11= 2.0.2CVSS 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
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- Low
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/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 in dependenciesInspect your project's go.mod file for a 'github.com/hashicorp/go-getter' entry and note the version number next to itAffected if The version listed is 1.5.11 or lower, or exactly 2.0.2
-
Check vendored go-getter versionIf using vendoring, inspect vendor/github.com/hashicorp/go-getter/go.mod or the version tag file in that directory to determine the included versionAffected if The vendored version is 1.5.11 or lower, or exactly 2.0.2
-
Verify ZIP file processing is usedSearch your codebase for calls to go-getter functions that handle ZIP files, such as 'get.Zip' or functions that decompress archives. Check if any code paths fetch and extract ZIP archivesAffected if Your application uses go-getter to fetch or extract ZIP files from external sources
-
Identify if passwords could be supplied to ZIP extractionReview how ZIP files are processed: check if user-supplied or remote ZIP files could contain passwords, and whether the code path reaches go-getter's unzip functionalityAffected if Password-protected ZIP files from untrusted sources can be processed by your application
You are affected if your project depends on go-getter version 1.5.11 or lower or exactly 2.0.2, and your application uses go-getter to process ZIP files that could be password-protected.
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.6.1 or 2.1.0 or later. If immediate upgrading is not feasible, avoid processing untrusted ZIP files or implement input validation to reject password-protected archives.
1.6.1 for Go Getter 1.x users; 2.1.0 for Go Getter 2.x users
- Identify the current version of go-getter being used in your project (e.g., check go.mod or vendor directory)
- If using go-getter version <= 1.5.11, upgrade to version 1.6.1
- If using go-getter version 2.0.2, upgrade to version 2.1.0
- Run `go mod tidy` to update dependencies
- Verify the upgrade by running tests, particularly any tests involving ZIP file processing
- Rebuild and redeploy your application
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation2.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,752.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-30323 — 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-2022-30323 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