Client resource exhaustion via crafted server replies
Published Jan 12, 2024 · Updated Jun 17, 2025
Denial of service in go-git before 5.11.0 allows remote attackers controlling a Git server to exhaust client resources with crafted replies. The upstream advisory does not identify the reply field, parser, or allocation that consumes resources without an effective bound. Exploitation requires a filesystem-backed go-git client to contact an attacker-controlled or otherwise malicious Git server; memory-only storage is unaffected.
Summary
What happened
Denial of service in go-git before 5.11.0 allows remote attackers controlling a Git server to exhaust client resources with crafted replies. The upstream advisory does not identify the reply field, parser, or allocation that consumes resources without an effective bound. Exploitation requires a filesystem-backed go-git client to contact an attacker-controlled or otherwise malicious Git server; memory-only storage is unaffected.
The record
- CVE
- CVE-2023-49568
- Published
- Jan 12, 2024
- Updated
- Jun 17, 2025
- Vendor
- go-git
- Product
- go-git
- Classifications
- CWE-20, T1499
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jan 12, 2024CVE publishedPublication date reported by the CVE source.
- Jun 17, 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=5.11.0
What conditions does exploitation require?
What is affected?
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.
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