CVE-2022-30322
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 allowed asymmetric resource exhaustion when go-getter processed malicious HTTP responses. 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 · high confidenceThe go-getter library (used for fetching Go packages and resources) contains a resource exhaustion vulnerability where malicious HTTP responses can cause asymmetric resource consumption, leading to denial of service. The vulnerability affects versions up to 1.5.11 and 2.0.2.
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 version in your projectRun 'go list -m all' or inspect your go.mod file for the go-getter module version entryAffected if The version listed is 1.5.11 or earlier, or exactly 2.0.2
-
Check if go-getter fetches from HTTP/HTTPS sourcesReview your code for calls to getter.Get or getter.GetAny that use http:// or https:// URLs as the sourceAffected if HTTP or HTTPS sources are used with go-getter and the library version is vulnerable
-
Verify go-getter is a direct or indirect dependencyRun 'go mod why -m github.com/hashicorp/go-getter' to confirm the module is pulled into your dependency treeAffected if go-getter is a dependency and its version falls within the affected range
You are affected if go-getter version 1.5.11 or earlier, or exactly 2.0.2 is present in your dependencies and you use it to fetch resources over HTTP/HTTPS.
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) to patch the resource exhaustion vulnerability.
1.6.1 for 1.x users; 2.1.0 for 2.x users
- Identify the current go-getter version in use (1.x or 2.x branch)
- For 1.x users: upgrade go-getter to version 1.6.1 or later
- For 2.x users: upgrade go-getter to version 2.1.0 or later
- Verify the upgrade was successful by checking the installed version
- Test the application to ensure functionality is unaffected
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation1.0 h
- Implementation2.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,664.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-30322 — 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-30322 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