Credential disclosure via misclassified repository configuration
Published Sep 2, 2024 · Updated Sep 3, 2024
Configuration-scope confusion in GitoxideLabs gix-path before 0.10.10 allows context-dependent attackers to read repository credentials. The installation_config functions parse the first git config --show-origin result and misclassify repository-local configuration as installation-wide when higher scopes are empty. Exploitation requires a victim operation on another repository from the configured repository; affected settings can then reach that repository's remote.
Summary
What happened
Configuration-scope confusion in GitoxideLabs gix-path before 0.10.10 allows context-dependent attackers to read repository credentials. The installation_config functions parse the first git config --show-origin result and misclassify repository-local configuration as installation-wide when higher scopes are empty. Exploitation requires a victim operation on another repository from the configured repository; affected settings can then reach that repository's remote.
The record
- CVE
- CVE-2024-45305
- Published
- Sep 2, 2024
- Updated
- Sep 3, 2024
- Vendor
- GitoxideLabs
- Product
- gitoxide
- Classifications
- CWE-706, T1187
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Sep 2, 2024CVE publishedPublication date reported by the CVE source.
- Sep 3, 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 <0.10.10
- Affected versionversion=< 0.10.10
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.
Weakness, pattern, technique
Public exploit references
- Upstream cross-repository credential disclosure proof of conceptproof of concept · demonstrated
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