dbcve.org
Go GetterApplication · Hashicorp

CVE-2024-6257

HIGH · 8.8 CVSS v3.1 Published 2024-06-25
Fix available
A fix is available. Upgrade to 1.7.5 or later.
See remediation →
95/100
Remediation priority · Urgent
Remotely reachable No privileges

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 · unedited
HashiCorp’s go-getter library can be coerced into executing Git update on an existing maliciously modified Git Configuration, potentially leading to arbitrary code execution.

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 confidence

HashiCorp's go-getter library has a vulnerability where it can be coerced into executing Git update operations on an existing maliciously modified Git Configuration file. An attacker who can manipulate the Git configuration could achieve arbitrary code execution during go-getter's Git operations.

MitigationUpdate go-getter to the patched version and audit existing Git configuration files for any unauthorized or malicious modifications.

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
Go GetterApplication
Affected:< 1.7.5

CVSS 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
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify go-getter version
    Run 'go list -m all | grep go-getter' or inspect your go.mod file for the go-getter module version
    Affected if The version listed is below 1.7.5 (e.g., 1.7.4, 1.7.0, etc.)
  2. Find applications using go-getter
    Search your codebase for imports of 'github.com/hashicorp/go-getter' and identify which binaries or services depend on it
    Affected if Your project directly imports and uses go-getter for fetching sources
  3. Verify Git client configuration
    Check for Git configuration files (.gitconfig, .git/config, environment GIT_CONFIG*) that may be referenced by go-getter operations
    Affected if The Git configuration files exist in locations writable by untrusted users or contain unexpected custom commands
  4. Inspect recent Git configuration changes
    Review Git configuration history or compare current .gitconfig against known-good baselines for any unauthorized modifications
    Affected if The Git config contains unexpected aliases, hooks, or custom commands that could execute arbitrary code
  5. Audit go-getter Git source usage
    Identify if your go-getter usage patterns include Git URLs (github.com, git://, or custom Git repositories) as sources
    Affected if Your application fetches from Git repositories using go-getter and an attacker could influence the repository URL or Git configuration

You are affected if go-getter version is below 1.7.5 AND your environment uses go-getter to fetch from Git sources where an attacker could manipulate the Git configuration.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 1.7.5 or later
Fixed in 1.7.5
Interim mitigation

Update go-getter to the patched version and audit existing Git configuration files for any unauthorized or malicious modifications.

Recommended fix High confidence

1.7.5

  1. Identify all projects and dependencies that use the go-getter library (github.com/hashicorp/go-getter)
  2. Run a dependency check (e.g., go list -m all or check go.mod files) to identify current version in use
  3. Update go-getter to version 1.7.5 or later using: go get github.com/hashicorp/[email protected]
  4. Run go mod tidy to update go.sum and clean up dependencies
  5. Rebuild and test the application to ensure the upgrade does not break existing functionality
  6. Redeploy the updated application to production environments

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Go Getter Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing8.0 h
  • Review / QA4.0 h
24.0 hours of engineering $4,160
Get the upgrade done

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 locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-6257 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-6257 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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