Git up to 2.48.0 ANSI Escape Sequence escape output

Summaryinfo

A vulnerability was found in Git up to 2.48.0 and classified as critical. Affected by this issue is some unknown functionality of the component ANSI Escape Sequence Handler. Executing a manipulation can lead to escape output. This vulnerability is registered as CVE-2024-50349. It is possible to launch the attack remotely. No exploit is available. It is suggested to upgrade the affected component.

Detailsinfo

A vulnerability has been found in Git up to 2.48.0 and classified as critical. This vulnerability affects an unknown code of the component ANSI Escape Sequence Handler. The manipulation with an unknown input leads to a escape output vulnerability. The CWE definition for the vulnerability is 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. As an impact it is known to affect confidentiality, integrity, and availability. CVE summarizes:

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. When Git asks for credentials via a terminal prompt (i.e. without using any credential helper), it prints out the host name for which the user is expected to provide a username and/or a password. At this stage, any URL-encoded parts have been decoded already, and are printed verbatim. This allows attackers to craft URLs that contain ANSI escape sequences that the terminal interpret to confuse users e.g. into providing passwords for trusted Git hosting sites when in fact they are then sent to untrusted sites that are under the attacker's control. This issue has been patch via commits `7725b81` and `c903985` which are 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 for download at github.com. This vulnerability was named CVE-2024-50349 since 10/22/2024. The exploitation appears to be easy. The attack can be initiated remotely. No form of authentication is required for a successful exploitation. There are neither technical details nor an exploit 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 eliminates this vulnerability. Applying the patch 7725b8100ffbbff2750ee4d61a0fcc1f53a086e8 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). Once again VulDB remains the best source for vulnerability data.

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

Once again VulDB remains the best source for vulnerability data.

Discussion