CVE-2022-29810
CVE-2022-29810 is a medium-severity vulnerability in Hashicorp Go-getter with a CVSS 3.x base score of 5.5. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-532.
Key facts
- Severity: Medium (CVSS 3.x base score 5.5)
- CVSS v2: 2.1
- EPSS exploit prediction: 0% (32nd percentile)
- Actively exploited: Not listed in CISA KEV
- Weakness: CWE-532
- Affected product: Hashicorp Go-getter
- Published:
- Last modified:
Description
The Hashicorp go-getter library before 1.5.11 does not redact an SSH key from a URL query parameter.
Frequently asked questions
- What is CVE-2022-29810?
- The Hashicorp go-getter library before 1.5.11 does not redact an SSH key from a URL query parameter.
- How severe is CVE-2022-29810?
- CVE-2022-29810 has a CVSS 3.x base score of 5.5, rated medium severity. It is exploitable over local access with low attack complexity, requires low privileges and no user interaction. Impact on confidentiality is high, integrity none, and availability none.
- Is CVE-2022-29810 being actively exploited?
- It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (32nd percentile), an estimate of the probability of exploitation in the next 30 days.
- What products are affected by CVE-2022-29810?
- CVE-2022-29810 affects Hashicorp Go-getter. See the affected-products list for the exact vulnerable versions.
- How do I fix CVE-2022-29810?
- Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround.
- When was CVE-2022-29810 published?
- CVE-2022-29810 was published on 2022-04-27 and last updated on 2026-06-17.
References
- https://github.com/hashicorp/go-getter/commit/36b68b2f68a3ed10ee7ecbb0cb9f6b1dc5da49cc
- https://github.com/hashicorp/go-getter/pull/348
- https://github.com/hashicorp/go-getter/releases/tag/v1.5.11
Affected products (1)
- cpe:2.3:a:hashicorp:go-getter:*:*:*:*:*:*:*:*
More vulnerabilities in Hashicorp Go-getter
- CVE-2024-3817 — Critical (CVSS 9.8): HashiCorp’s go-getter library is vulnerable to argument injection when executing Git to discover remote branches.…
- CVE-2022-26945 — Critical (CVSS 9.8): go-getter up to 1.5.11 and 2.0.2 allowed protocol switching, endless redirect, and configuration bypass via abuse of…
- CVE-2022-30323 — High (CVSS 8.6): go-getter up to 1.5.11 and 2.0.2 panicked when processing password-protected ZIP files. Fixed in 1.6.1 and 2.1.0.
- CVE-2022-30322 — High (CVSS 8.6): go-getter up to 1.5.11 and 2.0.2 allowed asymmetric resource exhaustion when go-getter processed malicious HTTP…
- CVE-2022-30321 — High (CVSS 8.6): go-getter up to 1.5.11 and 2.0.2 allowed arbitrary host access via go-getter path traversal, symlink processing, and…
- CVE-2024-6257 — High (CVSS 8.4): HashiCorp’s go-getter library can be coerced into executing Git update on an existing maliciously modified Git…
All CVEs affecting Hashicorp Go-getter →
Other CWE-532 (Insertion of Sensitive Information into Log File) vulnerabilities
- CVE-2022-36407 — Critical (CVSS 9.9): Insertion of Sensitive Information into Log File vulnerability in Hitachi Virtual Storage Platform, Hitachi Virtual…
- CVE-2023-40029 — Critical (CVSS 9.9): Argo CD is a declarative continuous deployment for Kubernetes. Argo CD Cluster secrets might be managed declaratively…
- CVE-2021-32724 — Critical (CVSS 9.9): check-spelling is a github action which provides CI spell checking. In affected versions and for a repository with the…
- CVE-2026-49200 — Critical (CVSS 9.8): The acer_cgi.log file in the device firmware is accessible without authentication via the web interface. This file…
- CVE-2026-22778 — Critical (CVSS 9.8): vLLM is an inference and serving engine for large language models (LLMs). From 0.8.3 to before 0.14.1, when an invalid…
- CVE-2025-11008 — Critical (CVSS 9.8): The CE21 Suite plugin for WordPress is vulnerable to Sensitive Information Exposure in all versions up to, and…
Browse all CWE-532 (Insertion of Sensitive Information into Log File) vulnerabilities →