Git up to 2.48.0 escape output

Summaryinfo

A vulnerability was found in Git up to 2.48.0. It has been classified as problematic. This affects an unknown part. The manipulation leads to escape output. This vulnerability is documented as CVE-2024-52006. The attack can be initiated remotely. There is not any exploit available. Upgrading the affected component is recommended.

Detailsinfo

A vulnerability was found in Git up to 2.48.0 and classified as problematic. This issue affects an unknown code block. The manipulation with an unknown input leads to a escape output vulnerability. Using CWE to declare the problem leads to CWE-116. The product prepares a structured message for communication with another component, but encoding or escaping of the data is either missing or done incorrectly. As a result, the intended structure of the message is not preserved. Impacted is integrity. The summary by CVE is:

Git is a fast, scalable, distributed revision control system with an unusually rich command set that provides both high-level operations and full access to internals. Git defines a line-based protocol that is used to exchange information between Git and Git credential helpers. Some ecosystems (most notably, .NET and node.js) interpret single Carriage Return characters as newlines, which renders the protections against CVE-2020-5260 incomplete for credential helpers that treat Carriage Returns in this way. This issue has been addressed in commit `b01b9b8` which is included in release versions v2.48.1, v2.47.2, v2.46.3, v2.45.3, v2.44.3, v2.43.6, v2.42.4, v2.41.3, and v2.40.4. Users are advised to upgrade. Users unable to upgrade should avoid cloning from untrusted URLs, especially recursive clones.

The advisory is shared at github.com. The identification of this vulnerability is CVE-2024-52006 since 11/04/2024. The exploitation is known to be easy. The attack may be initiated remotely. No form of authentication is needed for a successful exploitation. Neither technical details nor an exploit are publicly available.

The vulnerability scanner Nessus provides a plugin with the ID 214142 (Ubuntu 24.10 : Git vulnerabilities (USN-7207-1)), which helps to determine the existence of the flaw in a target environment.

Upgrading to version 2.40.4, 2.41.3, 2.42.4, 2.43.6, 2.44.3, 2.45.3, 2.46.3, 2.47.1 or 2.48.1 eliminates this vulnerability. Applying the patch b01b9b81d36759cdcd07305e78765199e1bc2060 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.

The vulnerability is also documented in the databases at Tenable (214142) and CERT Bund (WID-SEC-2025-1905). If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Affected

• IBM QRadar SIEM

Productinfo

Type

• Versioning Software

Name

• Git

Version

• 2.0
• 2.1
• 2.2
• 2.3
• 2.4
• 2.5
• 2.6
• 2.7
• 2.8
• 2.9
• 2.10
• 2.11
• 2.12
• 2.13
• 2.14
• 2.15
• 2.16
• 2.17
• 2.18
• 2.19
• 2.20
• 2.21
• 2.22
• 2.23
• 2.24
• 2.25
• 2.26
• 2.27
• 2.28
• 2.29
• 2.30
• 2.31
• 2.32
• 2.33
• 2.34
• 2.35
• 2.36
• 2.37
• 2.38
• 2.39
• 2.40
• 2.40.0
• 2.40.1
• 2.40.2
• 2.40.3
• 2.41
• 2.41.0
• 2.41.1
• 2.41.2
• 2.42
• 2.42.0
• 2.42.1
• 2.42.2
• 2.42.3
• 2.43
• 2.43.0
• 2.43.1
• 2.43.2
• 2.43.3
• 2.43.4
• 2.43.5
• 2.44
• 2.44.0
• 2.44.1
• 2.44.2
• 2.45
• 2.45.0
• 2.45.1
• 2.45.2
• 2.46
• 2.46.0
• 2.46.1
• 2.46.2
• 2.47
• 2.47.0
• 2.48.0

License

• open-source

Website

• Product: https://github.com/git/git/

CPE 2.3info

• 🔍
• 🔍
• 🔍

CPE 2.2info

• 🔍
• 🔍
• 🔍

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Discussion