CVE-2024-3817
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’s go-getter library is vulnerable to argument injection when executing Git to discover remote branches. This vulnerability does not affect the go-getter/v2 branch and package.
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 confidenceHashiCorp’s go-getter library (v1) has an argument injection vulnerability when executing Git to discover remote branches. Attackers can inject arbitrary arguments into Git commands, potentially achieving code execution. The go-getter/v2 branch and package are not affected.
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.9, < 1.7.4CVSS 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
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/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 v1 installationCheck the installed version of the go-getter package in your project or environment. For Go projects, run 'go list -m all | grep go-getter' or inspect your go.mod file for 'github.com/hashicorp/go-getter' entries.Affected if The version listed is >= 1.5.9 and < 1.7.4
-
Confirm go-getter v1 is in useSearch your codebase for imports of 'github.com/hashicorp/go-getter' (not '/v2'). Check your dependency manifest, vendor directory, or lock file for references to the v1 module.Affected if go-getter v1 is imported and used in your code
-
Verify Git is the remote sourceInspect how go-getter is invoked in your code. Look for URLs or sources that begin with 'git://', 'ssh://', or 'git@' which trigger Git-based remote operations.Affected if Your code uses go-getter to fetch from Git-based remote sources
-
Check for remote branch discoveryReview whether your go-getter usage triggers branch or ref discovery. This typically occurs when fetching repositories without a specific commit SHA, or when using features that enumerate branches/tags.Affected if Your go-getter operations fetch remote branches, tags, or perform ref discovery from Git repositories
You are affected if go-getter v1 version is >= 1.5.9 and < 1.7.4 AND your code uses it to interact with Git-based remote sources that trigger branch or ref discovery.
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 · scoped1.7.4
Migrate from go-getter v1 to go-getter v2, or apply any available security patches to go-getter v1. Review all code paths that use go-getter to ensure no unsafe input reaches Git command execution.
go-getter v1.7.4 or later (continuing to use go-getter/v1 package)
- Identify all projects and dependencies that use go-getter version < 1.7.4 by reviewing go.mod files
- Update the go-getter requirement to version 1.7.4 or later in go.mod (e.g., replace 'github.com/hashicorp/go-getter v1.x.x' with 'github.com/hashicorp/go-getter v1.7.4')
- Run 'go mod tidy' to update all dependency references
- Rebuild and test all affected applications to ensure compatibility
- Redeploy the updated applications to production environments
- Verify that Git operations using go-getter function correctly post-upgrade
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,656.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-3817 — 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-2024-3817 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