Git up to 2.39.1 path traversal

Summaryinfo

A vulnerability was found in Git up to 2.39.1. It has been declared as critical. Affected is an unknown function. Such manipulation leads to path traversal. This vulnerability is documented as CVE-2023-23946. The attack needs to be performed locally. There is not any exploit available. It is recommended to upgrade the affected component.

Detailsinfo

A vulnerability was found in Git up to 2.39.1 (Versioning Software). It has been rated as critical. Affected by this issue is some unknown processing. The manipulation with an unknown input leads to a path traversal vulnerability. Using CWE to declare the problem leads to CWE-22. The product uses external input to construct a pathname that is intended to identify a file or directory that is located underneath a restricted parent directory, but the product does not properly neutralize special elements within the pathname that can cause the pathname to resolve to a location that is outside of the restricted directory. Impacted is confidentiality, integrity, and availability. CVE summarizes:

Git, a revision control system, is vulnerable to path traversal prior to versions 2.39.2, 2.38.4, 2.37.6, 2.36.5, 2.35.7, 2.34.7, 2.33.7, 2.32.6, 2.31.7, and 2.30.8. By feeding a crafted input to `git apply`, a path outside the working tree can be overwritten as the user who is running `git apply`. A fix has been prepared and will appear in v2.39.2, v2.38.4, v2.37.6, v2.36.5, v2.35.7, v2.34.7, v2.33.7, v2.32.6, v2.31.7, and v2.30.8. As a workaround, use `git apply --stat` to inspect a patch before applying; avoid applying one that creates a symbolic link and then creates a file beyond the symbolic link.

The weakness was released 02/15/2023 as GHSA-r87m-v37r-cwfh. The advisory is available at github.com. This vulnerability is handled as CVE-2023-23946 since 01/19/2023. The technical details are unknown and an exploit is not available. This vulnerability is assigned to T1006 by the MITRE ATT&CK project.

Upgrading to version 2.30.8, 2.31.7, 2.32.6, 2.33.7, 2.34.7, 2.35.7, 2.36.5, 2.37.6, 2.38.4 or 2.39.2 eliminates this vulnerability. Applying the patch c867e4fa180bec4750e9b54eb10f459030dbebfd 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.

If you want to get best quality of vulnerability data, you may have to visit VulDB.

Productinfo

Type

• Versioning Software

Name

• Git

Version

• 2.30.0
• 2.30.1
• 2.30.2
• 2.30.3
• 2.30.4
• 2.30.5
• 2.30.6
• 2.30.7
• 2.31.0
• 2.31.1
• 2.31.2
• 2.31.3
• 2.31.4
• 2.31.5
• 2.31.6
• 2.32.0
• 2.32.1
• 2.32.2
• 2.32.3
• 2.32.4
• 2.32.5
• 2.33.0
• 2.33.1
• 2.33.2
• 2.33.3
• 2.33.4
• 2.33.5
• 2.33.6
• 2.34.0
• 2.34.1
• 2.34.2
• 2.34.3
• 2.34.4
• 2.34.5
• 2.34.6
• 2.35.0
• 2.35.1
• 2.35.2
• 2.35.3
• 2.35.4
• 2.35.5
• 2.35.6
• 2.36.0
• 2.36.1
• 2.36.2
• 2.36.3
• 2.36.4
• 2.37.0
• 2.37.1
• 2.37.2
• 2.37.3
• 2.37.4
• 2.37.5
• 2.38.0
• 2.38.1
• 2.38.2
• 2.38.3
• 2.39.0
• 2.39.1

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 best quality of vulnerability data, you may have to visit VulDB.

Discussion