Untrusted code cloning via ambiguous tag names
Published Aug 8, 2024 · Updated Sep 17, 2024
Code injection in GitLab CE/EE before 17.0.6, 17.1 before 17.1.4, and 17.2 before 17.2.2 allows remote attackers to induce untrusted clones. Ambiguous tag-name handling lets the web interface present a reference differently from the target resolved by the Git command-line client. A victim must trust the displayed tag and initiate the clone; the reported consequence is obtaining attacker-selected untrusted code, not server-side execution.
Summary
What happened
Code injection in GitLab CE/EE before 17.0.6, 17.1 before 17.1.4, and 17.2 before 17.2.2 allows remote attackers to induce untrusted clones. Ambiguous tag-name handling lets the web interface present a reference differently from the target resolved by the Git command-line client. A victim must trust the displayed tag and initiate the clone; the reported consequence is obtaining attacker-selected untrusted code, not server-side execution.
The record
- CVE
- CVE-2024-3958
- Published
- Aug 8, 2024
- Updated
- Sep 17, 2024
- Vendor
- GitLab
- Product
- GitLab
- Classifications
- CWE-94, T1204
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Aug 8, 2024CVE publishedPublication date reported by the CVE source.
- Sep 17, 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?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <17.0.6
- Affected versionversion=17.1 <17.1.4
- Affected versionversion=17.2 <17.2.2
What conditions does exploitation require?
What is affected?
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