git-ecosystem git-credential-manager up to 2.4.x permission assignment
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.3 | $0-$5k | 0.00 |
Summary
A vulnerability was found in git-ecosystem git-credential-manager up to 2.4.x. It has been rated as problematic. This impacts an unknown function. The manipulation leads to permission assignment. This vulnerability is documented as CVE-2024-32478. The attack needs to be performed locally. There is not any exploit available. Upgrading the affected component is advised.
Details
A vulnerability was found in git-ecosystem git-credential-manager up to 2.4.x. It has been rated as problematic. This issue affects an unknown function. The manipulation with an unknown input leads to a permission assignment vulnerability. Using CWE to declare the problem leads to CWE-732. The product specifies permissions for a security-critical resource in a way that allows that resource to be read or modified by unintended actors. Impacted is confidentiality, integrity, and availability. The summary by CVE is:
Git Credential Manager (GCM) is a secure Git credential helper. Prior to 2.5.0, the Debian package does not set root ownership on installed files. This allows user 1001 on a multi-user system can replace binary and gain other users' privileges. This vulnerability is fixed in 2.5.0.
It is possible to read the advisory at github.com. The identification of this vulnerability is CVE-2024-32478 since 04/12/2024. The exploitation is known to be difficult. Attacking locally is a requirement. The exploitation needs additional levels of successful authentication. It demands that the victim is doing some kind of user interaction. The technical details are unknown and an exploit is not publicly available.
Upgrading to version 2.5.0 eliminates this vulnerability. Applying the patch d9ac33c5b1478383672b4425f5ecf875a62efba9 is able to eliminate this problem. The bugfix is ready for download at github.com. The best possible mitigation is suggested to be upgrading to the latest version.
Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
Product
Type
Vendor
Name
Version
License
Website
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 5.3VulDB Meta Temp Score: 5.3
VulDB Base Score: 3.8
VulDB Temp Score: 3.7
VulDB Vector: 🔍
VulDB Reliability: 🔍
CNA Base Score: 6.9
CNA Vector (GitHub, Inc.): 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍
Exploiting
Class: Permission assignmentCWE: CWE-732 / CWE-275 / CWE-266
CAPEC: 🔍
ATT&CK: 🔍
Physical: Partially
Local: Yes
Remote: Partially
Availability: 🔍
Status: Not defined
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔍
Upgrade: git-credential-manager 2.5.0
Patch: d9ac33c5b1478383672b4425f5ecf875a62efba9
Timeline
04/12/2024 🔍04/19/2024 🔍
04/19/2024 🔍
04/04/2025 🔍
Sources
Product: github.comAdvisory: GHSA-3c3g-h9rx-f7vq
Status: Confirmed
CVE: CVE-2024-32478 (🔍)
GCVE (CVE): GCVE-0-2024-32478
GCVE (VulDB): GCVE-100-261611
Entry
Created: 04/19/2024 19:32Updated: 04/04/2025 22:41
Changes: 04/19/2024 19:32 (66), 04/04/2025 22:41 (4)
Complete: 🔍
Cache ID: 216::103
Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.