go-getter up to 1.5.11 and 2.0.2 allowed protocol switching, endless redirect, and…
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.
No HashiCorp vulnerabilities are listed in CISA KEV.
9 records in Go-getter · all components
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.
HashiCorp’s go-getter library is vulnerable to argument injection when executing Git to discover remote branches.
go-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.
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.
HashiCorp's go-getter library subdirectory download feature is vulnerable to symlink attacks leading to unauthorized read access beyond the designated directory boundaries.
go-getter up to 1.5.11 and 2.0.2 panicked when processing password-protected ZIP files.
go-getter up to 1.5.11 and 2.0.2 allowed asymmetric resource exhaustion when go-getter processed malicious HTTP responses.
HashiCorp go-getter up to 1.6.2 and 2.1.1 is vulnerable to decompression bombs.
The Hashicorp go-getter library before 1.5.11 does not redact an SSH key from a URL query parameter.