NTLM hash disclosure via renamed UNC paths
Published May 21, 2025 · Updated May 21, 2025
Information disclosure in GitHub Desktop before 3.4.20-beta3 allows attackers to obtain Windows NTLM hashes through a malicious commit. The history-view diff passes a renamed file's old and new paths to Git, whose realpath resolution follows a crafted UNC path and triggers Windows NTLM authentication. Exploitation requires a Windows user to open the attacker-controlled commit's file diff; it discloses the computer name, signed-in user name, and NTLM hash.
Summary
What happened
Information disclosure in GitHub Desktop before 3.4.20-beta3 allows attackers to obtain Windows NTLM hashes through a malicious commit. The history-view diff passes a renamed file's old and new paths to Git, whose realpath resolution follows a crafted UNC path and triggers Windows NTLM authentication. Exploitation requires a Windows user to open the attacker-controlled commit's file diff; it discloses the computer name, signed-in user name, and NTLM hash.
The record
- CVE
- CVE-2025-48064
- Published
- May 21, 2025
- Updated
- May 21, 2025
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-200, T1187
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- May 21, 2025CVE publishedPublication date reported by the CVE source.
- May 21, 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?
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