CVE-2025-48385
BaseFortify
Publication date: 2025-07-08
Last updated on: 2025-11-04
Assigner: GitHub, Inc.
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| git | git | 2.44.4 |
| git | git | 2.50.0 |
| git | git | 2.50.1 |
| git | git | 2.46.4 |
| git | git | 2.47.3 |
| git | git | 2.45.4 |
| git | git | 2.43.7 |
| git | git | 2.49.1 |
| git | git | 2.48.2 |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-88 | The product constructs a string for a command to be executed by a separate component in another control sphere, but it does not properly delimit the intended arguments, options, or switches within that command string. |
| CWE-73 | The product allows user input to control or influence paths or file names that are used in filesystem operations. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
This vulnerability in Git involves insufficient validation of advertised bundles when cloning a repository. Git can fetch bundles from a remote server to offload parts of the clone to a CDN. However, the client does not properly validate these bundles, allowing a malicious remote server to perform protocol injection. This can cause the client to write the fetched bundle to a location controlled by the attacker, potentially leading to arbitrary code execution. The vulnerability requires certain conditions, such as control over the clone destination or recursive clones with submodules, and can be mitigated by disabling recursive clones or updating Git to fixed versions.
How can this vulnerability impact me? :
This vulnerability can allow an attacker controlling a remote Git server to execute arbitrary code on the client machine by injecting malicious protocol data and causing the client to write and execute code from a location controlled by the attacker. This can compromise the security and integrity of the affected system, potentially leading to unauthorized access, data loss, or system compromise.
What immediate steps should I take to mitigate this vulnerability?
To mitigate this vulnerability, you should disable recursive clones to avoid cases where an adversary controls the clone location, and ensure that the bundle.heuristic config option is set to disable the use of bundle URIs. Additionally, update Git to one of the fixed versions: v2.43.7, v2.44.4, v2.45.4, v2.46.4, v2.47.3, v2.48.2, v2.49.1, or v2.50.1.