First published: Tue May 24 2022(Updated: )
go-getter up to 1.5.11 and 2.0.2 allowed protocol switching, endless redirect, and configuration bypass via abuse of custom HTTP response header processing. Fixed in 1.6.1 and 2.1.0.
Credit: cve@mitre.org
Affected Software | Affected Version | How to fix |
---|---|---|
redhat/github.com/hashicorp/go-getter | <1.6.1 | 1.6.1 |
redhat/github.com/hashicorp/go-getter | <2.1.0 | 2.1.0 |
HashiCorp Go-Getter | <=1.5.11 | |
HashiCorp Go-Getter | =2.0.2 |
The fix includes new configuration options to help limit the security exposure and have more secure defaults.
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
(Appears in the following advisories)
The vulnerability ID for go-getter is CVE-2022-26945.
The severity level of CVE-2022-26945 is critical with a CVSS score of 9.8.
HashiCorp go-getter versions up to 1.5.11 and 2.0.2 are affected by CVE-2022-26945.
An attacker can exploit CVE-2022-26945 by misusing go-getter to execute commands on the host.
To fix CVE-2022-26945, update HashiCorp go-getter to version 1.6.1 or 2.1.0.