Credential theft via remote URL host confusion
Published Jan 15, 2025 · Updated Jan 15, 2025
Credential exposure in GitHub Desktop 3.3.15 through 3.4.11 allows attackers to steal stored Git credentials via crafted remote URLs. GitHub Desktop misinterprets Git credential requests derived from a malicious remote URL and supplies credentials for a different host to the server Git is contacting. A user must clone an attacker-controlled repository directly or through a submodule, exposing a GitHub username and OAuth token or other stored remote-host credentials.
Summary
What happened
Credential exposure in GitHub Desktop 3.3.15 through 3.4.11 allows attackers to steal stored Git credentials via crafted remote URLs. GitHub Desktop misinterprets Git credential requests derived from a malicious remote URL and supplies credentials for a different host to the server Git is contacting. A user must clone an attacker-controlled repository directly or through a submodule, exposing a GitHub username and OAuth token or other stored remote-host credentials.
The record
- CVE
- CVE-2025-23040
- Published
- Jan 15, 2025
- Updated
- Jan 15, 2025
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-522, T1555
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Jan 15, 2025CVE publishedPublication date reported by the CVE source.
- Jan 15, 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