Git up to 2.40.0 Reject path traversal

Summaryinfo

A vulnerability was found in Git up to 2.40.0. It has been rated as critical. This issue affects some unknown processing of the component Reject Handler. Performing a manipulation results in path traversal. This vulnerability is identified as CVE-2023-25652. The attack can be initiated remotely. There is not any exploit available. Upgrading the affected component is advised.

Detailsinfo

A vulnerability, which was classified as critical, was found in Git up to 2.40.0 (Versioning Software). This affects an unknown function of the component Reject Handler. The manipulation with an unknown input leads to a path traversal vulnerability. CWE is classifying the issue as 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. This is going to have an impact on integrity, and availability. The summary by CVE is:

Git is a revision control system. Prior to versions 2.30.9, 2.31.8, 2.32.7, 2.33.8, 2.34.8, 2.35.8, 2.36.6, 2.37.7, 2.38.5, 2.39.3, and 2.40.1, by feeding specially crafted input to `git apply --reject`, a path outside the working tree can be overwritten with partially controlled contents (corresponding to the rejected hunk(s) from the given patch). A fix is available in versions 2.30.9, 2.31.8, 2.32.7, 2.33.8, 2.34.8, 2.35.8, 2.36.6, 2.37.7, 2.38.5, 2.39.3, and 2.40.1. As a workaround, avoid using `git apply` with `--reject` when applying patches from an untrusted source. Use `git apply --stat` to inspect a patch before applying; avoid applying one that create a conflict where a link corresponding to the `*.rej` file exists.

The weakness was released 04/25/2023 as GHSA-2hvf-7c8p-28fx. It is possible to read the advisory at github.com. This vulnerability is uniquely identified as CVE-2023-25652 since 02/09/2023. The technical details are unknown and an exploit is not publicly available. The attack technique deployed by this issue is T1006 according to MITRE ATT&CK.

Upgrading to version 2.30.9, 2.31.8, 2.32.7, 2.33.8, 2.34.8, 2.35.8, 2.36.6, 2.37.7, 2.38.5, 2.39.3 or 2.40.1 eliminates this vulnerability. Applying the patch 18e2b1cfc80990719275d7b08e6e50f3e8cbc902 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.

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.30.0
• 2.30.1
• 2.30.2
• 2.30.3
• 2.30.4
• 2.30.5
• 2.30.6
• 2.30.7
• 2.30.8
• 2.31
• 2.31.0
• 2.31.1
• 2.31.2
• 2.31.3
• 2.31.4
• 2.31.5
• 2.31.6
• 2.31.7
• 2.32
• 2.32.0
• 2.32.1
• 2.32.2
• 2.32.3
• 2.32.4
• 2.32.5
• 2.32.6
• 2.33
• 2.33.0
• 2.33.1
• 2.33.2
• 2.33.3
• 2.33.4
• 2.33.5
• 2.33.6
• 2.33.7
• 2.34
• 2.34.0
• 2.34.1
• 2.34.2
• 2.34.3
• 2.34.4
• 2.34.5
• 2.34.6
• 2.34.7
• 2.35
• 2.35.0
• 2.35.1
• 2.35.2
• 2.35.3
• 2.35.4
• 2.35.5
• 2.35.6
• 2.35.7
• 2.36
• 2.36.0
• 2.36.1
• 2.36.2
• 2.36.3
• 2.36.4
• 2.36.5
• 2.37
• 2.37.0
• 2.37.1
• 2.37.2
• 2.37.3
• 2.37.4
• 2.37.5
• 2.37.6
• 2.38
• 2.38.0
• 2.38.1
• 2.38.2
• 2.38.3
• 2.38.4
• 2.39
• 2.39.0
• 2.39.1
• 2.39.2
• 2.40.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

Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.

Discussion