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.
Historical advisory saved 17 Nov 2026 03:33:24 UTC. The publisher may have updated it since then. Latest advisory.
euvd · EUVD-2024-2209
PublishedEUVD source date text has no stated timezone and is retained without inventing a UTC instant. Related bulletin membership is not an alias, common cause or applicability claim. A missing vector with a zero score is treated as unrated. Complete vendor/product and underlying source evidence remains in the original JSON.
Original publisher date fields
datePublished: Jun 25, 2024, 4:31:03 PM
dateUpdated: Aug 1, 2024, 9:33:05 PM
6 related source bulletins · separate from aliases
openSUSE-SU-2024:0268-1: Security update for trivy
CVE-2023-42363 · CVE-2024-35192 · CVE-2024-6257
openSUSE-SU-2024:0269-1: Security update for trivy
CVE-2023-42363 · CVE-2024-35192 · CVE-2024-6257
msrc_CVE-2024-6257: HashiCorp go-getter Vulnerable to Code Execution On Git Update Via Git Config Manipulation
CVE-2024-6257
openSUSE-SU-2024:14190-1: conftest-0.54.0-1.1 on GA media
CVE-2024-6257
openSUSE-SU-2024:14183-1: trivy-0.53.0-1.1 on GA media
CVE-2024-6257
NCSC-2024-0339: Kwetsbaarheden verholpen in Microsoft Mariner
CVE-2022-2601 · CVE-2022-3775 · CVE-2022-36648 · CVE-2019-3833 · CVE-2021-3929 · CVE-2021-4158 · CVE-2021-4206 · CVE-2021-4207 · CVE-2022-26353 · CVE-2022-35414 · CVE-2023-3354 · CVE-2022-3872 · CVE-2022-4144 · CVE-2023-45288 · CVE-2023-29404 · CVE-2023-29402 · CVE-2019-3816 · CVE-2021-3750 · CVE-2022-0358 · CVE-2022-26354 · CVE-2022-3165 · CVE-2022-2962 · CVE-2022-41722 · CVE-2022-29526 · CVE-2007-4559 · CVE-2019-9674 · CVE-2017-18207 · CVE-2019-20907 · CVE-2021-23336 · CVE-2017-17522 · CVE-2024-6655 · CVE-2024-2466 · CVE-2024-39331 · CVE-2021-43565 · CVE-2024-39277 · CVE-2024-38780 · CVE-2024-39292 · CVE-2024-39482 · CVE-2024-39484 · CVE-2024-39495 · CVE-2024-40902 · CVE-2024-41110 · CVE-2024-37298 · CVE-2024-0397 · CVE-2024-38571 · CVE-2024-42077 · CVE-2024-39473 · CVE-2024-26900 · CVE-2024-39474 · CVE-2024-42073 · CVE-2024-42074 · CVE-2024-42075 · CVE-2024-42078 · CVE-2024-0853 · CVE-2024-2004 · CVE-2024-2398 · CVE-2024-38662 · CVE-2024-36288 · CVE-2024-39480 · CVE-2024-39476 · CVE-2024-39475 · CVE-2024-37371 · CVE-2024-26461 · CVE-2024-37370 · CVE-2024-6104 · CVE-2024-6257 · CVE-2024-23722 · CVE-2024-40898 · CVE-2024-38583 · CVE-2024-39493 · CVE-2024-42068 · CVE-2024-39489 · CVE-2024-42070 · CVE-2024-42076 · CVE-2024-42080 · CVE-2024-38428 · CVE-2024-42082 · CVE-2022-48788 · CVE-2023-52340 · CVE-2022-48841 · CVE-2024-39485 · CVE-2024-39483 · CVE-2024-42071 · CVE-2024-42072 · CVE-2024-42237 · CVE-2024-42083
No normalized affected-package data is projected for this source revision. The original publisher record may contain additional product and version evidence; this does not establish that a package is unaffected.
Original source record · Cite this exact observation · Complete original publisher JSON