CVE-2022-30321
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 arbitrary host access via go-getter path traversal, symlink processing, and command injection flaws. 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 downloading files/packages in Go) up to versions 1.5.11 and 2.0.2 contains multiple vulnerabilities: path traversal, symlink processing flaws, and command injection. These flaws can be chained to achieve arbitrary host access from the machine running go-getter.
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 as a dependencySearch your project files (go.mod, go.sum, vendor/ directory, or dependency lock files) for the string 'github.com/hashicorp/go-getter' to confirm the library is included as a dependency.Affected if go-getter appears as a dependency and the version listed is 1.5.11 or earlier, or exactly 2.0.2.
-
Check the exact go-getter versionRun 'go list -m github.com/hashicorp/go-getter' in your project directory to display the currently resolved version, or inspect the version string in your go.sum file for the go-getter entry.Affected if The version shown is 1.5.11 or lower, or is exactly 2.0.2.
-
Determine if the application fetches remote sourcesSearch your codebase for calls to getter.Get, getter.GetAny, or similar getter functions that download files from URLs, S3 buckets, or other remote sources. Look for imports of 'github.com/hashicorp/go-getter' and usage of its Get or GetAny methods.Affected if The application code actively uses go-getter to retrieve files from remote sources at runtime.
-
Assess trust boundary of URLs processedIdentify whether the URLs or sources passed to go-getter functions can come from untrusted input such as user upload, external API responses, configuration files not controlled by the operator, or environment variables.Affected if go-getter processes URLs that originate from untrusted or user-controlled sources rather than only from a trusted, internal configuration.
You are affected if go-getter version 1.5.11 or earlier, or exactly 2.0.2, is a dependency in your project and your application uses it to fetch files from remote sources, especially when those sources are untrusted or user-controlled.
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 path traversal, symlink, and command injection vulnerabilities that allow arbitrary host access.
1.6.1 for 1.x branch, 2.1.0 for 2.x branch
- Identify the current go-getter version in use (check go.mod or vendor directory)
- If using go-getter 1.x: upgrade to version 1.6.1 or later
- If using go-getter 2.x: upgrade to version 2.1.0 or later
- Update the dependency in go.mod file (e.g., go get github.com/hashicorp/[email protected] [email protected])
- Run 'go mod tidy' to update all dependencies
- Rebuild and redeploy the application
- Verify the upgrade does not break existing functionality
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-30321 — 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-30321 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