OESA-2023-1269 (CVE-2023-25652)
Vulnerability from osv_openeuler – Published: 2023-05-06 11:05 – Updated: 2026-08-06 11:05 – Source websiteGit is a free and open source distributed version control system designed to handle everything from small to very large projects with speed and efficiency. Git is easy to learn and has a tiny footprint with lightning fast performance. It outclasses SCM tools like Subversion, CVS, Perforce, and ClearCase with features like cheap local branching, convenient staging areas, and multiple workflows.
Security Fix(es):
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.(CVE-2023-25652)
In Git for Windows, the Windows port of Git, no localized messages are shipped with the installer. As a consequence, Git is expected not to localize messages at all, and skips the gettext initialization. However, due to a change in MINGW-packages, the gettext() function's implicit initialization no longer uses the runtime prefix but uses the hard-coded path C:\mingw64\share\locale to look for localized messages. And since any authenticated user has the permission to create folders in C:\ (and since C:\mingw64 does not typically exist), it is possible for low-privilege users to place fake messages in that location where git.exe will pick them up in version 2.40.1.
This vulnerability is relatively hard to exploit and requires social engineering. For example, a legitimate message at the end of a clone could be maliciously modified to ask the user to direct their web browser to a malicious website, and the user might think that the message comes from Git and is legitimate. It does require local write access by the attacker, though, which makes this attack vector less likely. Version 2.40.1 contains a patch for this issue. Some workarounds are available. Do not work on a Windows machine with shared accounts, or alternatively create a C:\mingw64 folder and leave it empty. Users who have administrative rights may remove the permission to create folders in C:\.(CVE-2023-25815)
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, a specially crafted .gitmodules file with submodule URLs that are longer than 1024 characters can used to exploit a bug in config.c::git_config_copy_or_rename_section_in_file(). This bug can be used to inject arbitrary configuration into a user's $GIT_DIR/config when attempting to remove the configuration section associated with that submodule. When the attacker injects configuration values which specify executables to run (such as core.pager, core.editor, core.sshCommand, etc.) this can lead to a remote code execution. A fix 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 running git submodule deinit on untrusted repositories or without prior inspection of any submodule sections in $GIT_DIR/config.(CVE-2023-29007)
| URL | Type | |
|---|---|---|
{
"affected": [
{
"ecosystem_specific": {
"aarch64": [
"git-debugsource-2.27.0-14.oe1.aarch64.rpm",
"git-daemon-2.27.0-14.oe1.aarch64.rpm",
"git-debuginfo-2.27.0-14.oe1.aarch64.rpm",
"git-2.27.0-14.oe1.aarch64.rpm"
],
"noarch": [
"git-gui-2.27.0-14.oe1.noarch.rpm",
"perl-Git-2.27.0-14.oe1.noarch.rpm",
"git-email-2.27.0-14.oe1.noarch.rpm",
"git-web-2.27.0-14.oe1.noarch.rpm",
"gitk-2.27.0-14.oe1.noarch.rpm",
"git-help-2.27.0-14.oe1.noarch.rpm",
"git-svn-2.27.0-14.oe1.noarch.rpm",
"perl-Git-SVN-2.27.0-14.oe1.noarch.rpm"
],
"src": [
"git-2.27.0-14.oe1.src.rpm"
],
"x86_64": [
"git-debuginfo-2.27.0-14.oe1.x86_64.rpm",
"git-debugsource-2.27.0-14.oe1.x86_64.rpm",
"git-2.27.0-14.oe1.x86_64.rpm",
"git-daemon-2.27.0-14.oe1.x86_64.rpm"
]
},
"package": {
"ecosystem": "openEuler:20.03-LTS-SP1",
"name": "git",
"purl": "pkg:rpm/openEuler/git\u0026distro=openEuler-20.03-LTS-SP1"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "2.27.0-14.oe1"
}
],
"type": "ECOSYSTEM"
}
]
},
{
"ecosystem_specific": {
"aarch64": [
"git-2.27.0-17.oe1.aarch64.rpm",
"git-debuginfo-2.27.0-17.oe1.aarch64.rpm",
"git-debugsource-2.27.0-17.oe1.aarch64.rpm",
"git-daemon-2.27.0-17.oe1.aarch64.rpm"
],
"noarch": [
"git-gui-2.27.0-17.oe1.noarch.rpm",
"perl-Git-SVN-2.27.0-17.oe1.noarch.rpm",
"perl-Git-2.27.0-17.oe1.noarch.rpm",
"gitk-2.27.0-17.oe1.noarch.rpm",
"git-svn-2.27.0-17.oe1.noarch.rpm",
"git-help-2.27.0-17.oe1.noarch.rpm",
"git-email-2.27.0-17.oe1.noarch.rpm",
"git-web-2.27.0-17.oe1.noarch.rpm"
],
"src": [
"git-2.27.0-17.oe1.src.rpm"
],
"x86_64": [
"git-debuginfo-2.27.0-17.oe1.x86_64.rpm",
"git-daemon-2.27.0-17.oe1.x86_64.rpm",
"git-debugsource-2.27.0-17.oe1.x86_64.rpm",
"git-2.27.0-17.oe1.x86_64.rpm"
]
},
"package": {
"ecosystem": "openEuler:20.03-LTS-SP3",
"name": "git",
"purl": "pkg:rpm/openEuler/git\u0026distro=openEuler-20.03-LTS-SP3"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "2.27.0-17.oe1"
}
],
"type": "ECOSYSTEM"
}
]
},
{
"ecosystem_specific": {
"aarch64": [
"git-debugsource-2.33.0-10.oe2203.aarch64.rpm",
"git-debuginfo-2.33.0-10.oe2203.aarch64.rpm",
"git-2.33.0-10.oe2203.aarch64.rpm",
"git-daemon-2.33.0-10.oe2203.aarch64.rpm",
"git-2.33.0-11.oe2203sp1.aarch64.rpm",
"git-daemon-2.33.0-11.oe2203sp1.aarch64.rpm",
"git-debuginfo-2.33.0-11.oe2203sp1.aarch64.rpm",
"git-debugsource-2.33.0-11.oe2203sp1.aarch64.rpm",
"git-core-2.33.0-11.oe2203sp1.aarch64.rpm"
],
"noarch": [
"perl-Git-2.33.0-10.oe2203.noarch.rpm",
"git-svn-2.33.0-10.oe2203.noarch.rpm",
"perl-Git-SVN-2.33.0-10.oe2203.noarch.rpm",
"git-email-2.33.0-10.oe2203.noarch.rpm",
"git-help-2.33.0-10.oe2203.noarch.rpm",
"git-web-2.33.0-10.oe2203.noarch.rpm",
"git-gui-2.33.0-10.oe2203.noarch.rpm",
"gitk-2.33.0-10.oe2203.noarch.rpm",
"git-svn-2.33.0-11.oe2203sp1.noarch.rpm",
"perl-Git-2.33.0-11.oe2203sp1.noarch.rpm",
"git-web-2.33.0-11.oe2203sp1.noarch.rpm",
"perl-Git-SVN-2.33.0-11.oe2203sp1.noarch.rpm",
"git-email-2.33.0-11.oe2203sp1.noarch.rpm",
"git-help-2.33.0-11.oe2203sp1.noarch.rpm",
"git-gui-2.33.0-11.oe2203sp1.noarch.rpm",
"gitk-2.33.0-11.oe2203sp1.noarch.rpm"
],
"src": [
"git-2.33.0-10.oe2203.src.rpm",
"git-2.33.0-11.oe2203sp1.src.rpm"
],
"x86_64": [
"git-debuginfo-2.33.0-10.oe2203.x86_64.rpm",
"git-daemon-2.33.0-10.oe2203.x86_64.rpm",
"git-debugsource-2.33.0-10.oe2203.x86_64.rpm",
"git-2.33.0-10.oe2203.x86_64.rpm",
"git-debuginfo-2.33.0-11.oe2203sp1.x86_64.rpm",
"git-daemon-2.33.0-11.oe2203sp1.x86_64.rpm",
"git-core-2.33.0-11.oe2203sp1.x86_64.rpm",
"git-2.33.0-11.oe2203sp1.x86_64.rpm",
"git-debugsource-2.33.0-11.oe2203sp1.x86_64.rpm"
]
},
"package": {
"ecosystem": "openEuler:22.03-LTS",
"name": "git",
"purl": "pkg:rpm/openEuler/git\u0026distro=openEuler-22.03-LTS"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "2.33.0-11.oe2203sp1"
}
],
"type": "ECOSYSTEM"
}
]
},
{
"ecosystem_specific": {
"aarch64": [
"git-2.33.0-11.oe2203sp1.aarch64.rpm",
"git-daemon-2.33.0-11.oe2203sp1.aarch64.rpm",
"git-debuginfo-2.33.0-11.oe2203sp1.aarch64.rpm",
"git-debugsource-2.33.0-11.oe2203sp1.aarch64.rpm",
"git-core-2.33.0-11.oe2203sp1.aarch64.rpm"
],
"noarch": [
"git-svn-2.33.0-11.oe2203sp1.noarch.rpm",
"perl-Git-2.33.0-11.oe2203sp1.noarch.rpm",
"git-web-2.33.0-11.oe2203sp1.noarch.rpm",
"perl-Git-SVN-2.33.0-11.oe2203sp1.noarch.rpm",
"git-email-2.33.0-11.oe2203sp1.noarch.rpm",
"git-help-2.33.0-11.oe2203sp1.noarch.rpm",
"git-gui-2.33.0-11.oe2203sp1.noarch.rpm",
"gitk-2.33.0-11.oe2203sp1.noarch.rpm"
],
"src": [
"git-2.33.0-11.oe2203sp1.src.rpm"
],
"x86_64": [
"git-debuginfo-2.33.0-11.oe2203sp1.x86_64.rpm",
"git-daemon-2.33.0-11.oe2203sp1.x86_64.rpm",
"git-core-2.33.0-11.oe2203sp1.x86_64.rpm",
"git-2.33.0-11.oe2203sp1.x86_64.rpm",
"git-debugsource-2.33.0-11.oe2203sp1.x86_64.rpm"
]
},
"package": {
"ecosystem": "openEuler:22.03-LTS-SP1",
"name": "git",
"purl": "pkg:rpm/openEuler/git\u0026distro=openEuler-22.03-LTS-SP1"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "2.33.0-11.oe2203sp1"
}
],
"type": "ECOSYSTEM"
}
]
}
],
"database_specific": {
"severity": "High"
},
"details": "Git is a free and open source distributed version control system designed to handle everything from small to very large projects with speed and efficiency. Git is easy to learn and has a tiny footprint with lightning fast performance. It outclasses SCM tools like Subversion, CVS, Perforce, and ClearCase with features like cheap local branching, convenient staging areas, and multiple workflows.\r\n\r\nSecurity Fix(es):\r\n\r\nGit 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.(CVE-2023-25652)\r\n\r\nIn Git for Windows, the Windows port of Git, no localized messages are shipped with the installer. As a consequence, Git is expected not to localize messages at all, and skips the gettext initialization. However, due to a change in MINGW-packages, the `gettext()` function\u0026apos;s implicit initialization no longer uses the runtime prefix but uses the hard-coded path `C:\\mingw64\\share\\locale` to look for localized messages. And since any authenticated user has the permission to create folders in `C:\\` (and since `C:\\mingw64` does not typically exist), it is possible for low-privilege users to place fake messages in that location where `git.exe` will pick them up in version 2.40.1.\r\n\r\nThis vulnerability is relatively hard to exploit and requires social engineering. For example, a legitimate message at the end of a clone could be maliciously modified to ask the user to direct their web browser to a malicious website, and the user might think that the message comes from Git and is legitimate. It does require local write access by the attacker, though, which makes this attack vector less likely. Version 2.40.1 contains a patch for this issue. Some workarounds are available. Do not work on a Windows machine with shared accounts, or alternatively create a `C:\\mingw64` folder and leave it empty. Users who have administrative rights may remove the permission to create folders in `C:\\`.(CVE-2023-25815)\r\n\r\nGit 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, a specially crafted `.gitmodules` file with submodule URLs that are longer than 1024 characters can used to exploit a bug in `config.c::git_config_copy_or_rename_section_in_file()`. This bug can be used to inject arbitrary configuration into a user\u0026apos;s `$GIT_DIR/config` when attempting to remove the configuration section associated with that submodule. When the attacker injects configuration values which specify executables to run (such as `core.pager`, `core.editor`, `core.sshCommand`, etc.) this can lead to a remote code execution. A fix 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 running `git submodule deinit` on untrusted repositories or without prior inspection of any submodule sections in `$GIT_DIR/config`.(CVE-2023-29007)",
"id": "OESA-2023-1269",
"modified": "2026-08-06T11:05:44Z",
"published": "2023-05-06T11:05:44Z",
"references": [
{
"type": "ADVISORY",
"url": "https://www.openeuler.org/en/security/safety-bulletin/detail.html?id=openEuler-SA-2023-1269"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2023-25652"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2023-25815"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2023-29007"
}
],
"schema_version": "1.7.2",
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N",
"type": "CVSS_V3"
}
],
"summary": "git security update",
"upstream": [
"CVE-2023-25652",
"CVE-2023-25815",
"CVE-2023-29007"
]
}
Sightings
| Author | Source | Type | Date | Other |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or observed by the user.
- Confirmed: The vulnerability has been validated from an analyst's perspective.
- Published Proof of Concept: A public proof of concept is available for this vulnerability.
- Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
- Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
- Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
- Not confirmed: The user expressed doubt about the validity of the vulnerability.
- Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.
Browse all ATT&CK techniques and the vulnerabilities related to each.
Related by attack behaviour
Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.