Application hang via crafted revision specification
Published Feb 6, 2024 · Updated Feb 13, 2025
Denial of service in libgit2 1.4.0 through 1.6.4 and 1.7.0 through 1.7.1 allows context-dependent attackers to hang calling applications. The parsing loop in src/libgit2/revparse.c lets a crafted revision specification force loop-condition reads from arbitrary memory and repeat indefinitely. Reachability requires a consuming application to pass attacker-influenced input to git_revparse_single; the established consequence is a hung calling process.
Summary
What happened
Denial of service in libgit2 1.4.0 through 1.6.4 and 1.7.0 through 1.7.1 allows context-dependent attackers to hang calling applications. The parsing loop in src/libgit2/revparse.c lets a crafted revision specification force loop-condition reads from arbitrary memory and repeat indefinitely. Reachability requires a consuming application to pass attacker-influenced input to git_revparse_single; the established consequence is a hung calling process.
The record
- CVE
- CVE-2024-24575
- Published
- Feb 6, 2024
- Updated
- Feb 13, 2025
- Vendor
- libgit2
- Product
- libgit2
- Classifications
- T1499.004
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Feb 6, 2024CVE publishedPublication date reported by the CVE source.
- Feb 13, 2025Record 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=>= 1.4.0, < 1.6.5
- Affected versionversion=>= 1.7.0, < 1.7.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