Code execution via reused malicious Git configuration
Published Jun 25, 2024 · Updated Aug 1, 2024
Command injection in HashiCorp go-getter before 1.7.5 allows remote authenticated users to execute arbitrary code during Git updates. GitGetter's update path reused the destination repository's existing .git/config before invoking git pull, so an attacker who modified that configuration after cloning could make Git launch attacker-chosen code. Exploitation requires control sufficient to alter the cloned repository's Git configuration and a separate user action that causes go-getter to update it.
Summary
What happened
Command injection in HashiCorp go-getter before 1.7.5 allows remote authenticated users to execute arbitrary code during Git updates. GitGetter's update path reused the destination repository's existing .git/config before invoking git pull, so an attacker who modified that configuration after cloning could make Git launch attacker-chosen code. Exploitation requires control sufficient to alter the cloned repository's Git configuration and a separate user action that causes go-getter to update it.
The record
- CVE
- CVE-2024-6257
- Published
- Jun 25, 2024
- Updated
- Aug 1, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-77
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Jun 25, 2024CVE publishedPublication date reported by the CVE source.
- Aug 1, 2024Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo