Secuno
ENNL
Book demo

CVE-2024-3817

Hashicorp Go-getter vulnerability

9.8 CRITICALEPSS 1.33%
  1. Published17 Apr 2024

Description

HashiCorp’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.

CVSS 3.1 breakdown

Attack vectorNetwork
Attack complexityLow
Privileges requiredNone
User interactionNone
ScopeUnchanged
ConfidentialityHigh
IntegrityHigh
AvailabilityHigh
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Affected products

Hashicorp Go-getter≥ 1.5.9 < 1.7.4

Remediation

Fixed in
Hashicorp Go-getter≥ 1.7.4

References

Related CVEs

Recent high-severity vulnerabilities sharing a weakness type.

CVE-2026-1089299.9
A flaw has been found in Netcore NR268 1.7.121109. The affected element is the function…
CVE-2026-1089638.8
databasement before 1.8.2 allows remote code execution because it runs certain commands…
CVE-2026-194828.8
IBM Security Verify Access 10.0 through 10.0.9.2 and IBM Verify Identity Access 11.0…
CVE-2026-187408.8
IBM Security Verify Access 10.0 through 10.0.9.2 and IBM Verify Identity Access 11.0…
CVE-2026-1076398.8
ILIAS before 9.24, 10.x before 10.12 and 11.x before 11.5 contains an argument…
CVE-2026-1075109.1
An authenticated high privilege user can inject arguments in troubleshooting commands…

Frequently asked

Is CVE-2024-3817 being actively exploited?

CVE-2024-3817 is not in the CISA KEV catalog. Its EPSS exploit probability is 1.33%.

How severe is CVE-2024-3817?

CVE-2024-3817 has a CVSS 3.1 base score of 9.8, rated critical. EPSS estimates a 1.33% probability of exploitation.

Which products are affected by CVE-2024-3817?

Affected products include Hashicorp Go-getter.

How do I fix CVE-2024-3817?

Upgrade affected software to a fixed version, for example Hashicorp Go-getter 1.7.4 or later, then confirm no affected versions remain in your inventory.

How Secuno handles this

Secuno correlates vulnerabilities like CVE-2024-3817 against the real software inventory on every managed device, as each hourly inventory arrives. Rather than a static severity, each match is scored in context: exploit availability, EPSS, the asset's exposure, and business criticality decide where it lands in the queue. If an affected version is present anywhere across your portfolio, it surfaces automatically with a prioritised remediation path.

See how prioritisation worksBook a demo

Get Patch this first every Monday

Five vulnerabilities that matter this week, ranked on real exploitation. Plain language, one email, no spam.

You can unsubscribe with one click from every issue. We handle your details as described in our privacy policy.

Data from the NVD, CISA KEV catalog and FIRST EPSS. CVSS 3.1 base score shown where available.