CVE-2023-25815: Git looks for localized messages in the wrong place
Noroxi assessment
Priority: Monitor (action score 8/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.83% (FIRST EPSS); higher than 57.6% of all records.
- Someone with local access to the system can trigger it. A low-privileged account is enough. A user must open a link or visit a page. Special conditions such as timing or configuration are required.
- Fixed version: git (AlmaLinux:8) 2.39.3-1.el8_8; git-all (AlmaLinux:8) 2.39.3-1.el8_8; git-core (AlmaLinux:8) 2.39.3-1.el8_8.
- Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).
Low priority for now. Upgrade to git (AlmaLinux:8) 2.39.3-1.el8_8; git-all (AlmaLinux:8) 2.39.3-1.el8_8; git-core (AlmaLinux:8) 2.39.3-1.el8_8 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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:\`.
- BDU:2023-06650
- ALSA-2023:3245
- ALSA-2023:3246
- DLA-3844-1
- DLA-3867-1
- DSA-5769-1
- openSUSE-SU-2024:12889-1
- RHSA-2023:3192
- RHSA-2023:3243
- RHSA-2023:3245
- RHSA-2023:3246
- RHSA-2023:3247
- RHSA-2023:3248
- RHSA-2023:3280
- RHSA-2023:3382
- RLSA-2023:3246
- SUSE-SU-2023:2038-1
- SUSE-SU-2023:2038-2
- SUSE-SU-2023:2062-1
- SUSE-SU-2023:2081-1
- Published
- Apr 25, 2023
- Updated
- Jun 17, 2026
- EPSS
- 0.8% · 57th percentile
- CWE
- CWE-22
Report tools
Action score
8
Monitor
Low priority for now.
- CVSS
- 8 / 40 · 2.2 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.8%
CNA vs NVD score
- NVD
- 2.2
- CNA · GitHub_M
- 3.3
- 1.1 point gap
CVSS:3.1/AV:L/AC:H/PR:L/UI:R/S:U/C:N/I:L/A:L
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| git for windows project | git for windows | cpe:2.3:a:git_for_windows_project:git_for_windows |
| fedoraproject | fedora | cpe:2.3:o:fedoraproject:fedora |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- fedoraproject fedora37
- fedoraproject fedora38
- git for windows project git for windowsbefore 2.40.1
Versions reported by the vendor
Affected version ranges reported by the assigning authority (GitHub_M). Independent of NVD's CPE analysis and usually ahead of it.
git-for-windows git
- < 2.40.1affected
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| AlmaLinux:8 | git | before 2.39.3-1.el8_8 | 2.39.3-1.el8_8 |
| AlmaLinux:8 | git-all | before 2.39.3-1.el8_8 | 2.39.3-1.el8_8 |
| AlmaLinux:8 | git-core | before 2.39.3-1.el8_8 | 2.39.3-1.el8_8 |
| AlmaLinux:8 | git-core-doc | before 2.39.3-1.el8_8 | 2.39.3-1.el8_8 |
| AlmaLinux:8 | git-credential-libsecret | before 2.39.3-1.el8_8 | 2.39.3-1.el8_8 |
| AlmaLinux:8 | git-daemon | before 2.39.3-1.el8_8 | 2.39.3-1.el8_8 |
| AlmaLinux:8 | git-email | before 2.39.3-1.el8_8 | 2.39.3-1.el8_8 |
| AlmaLinux:8 | git-gui | before 2.39.3-1.el8_8 | 2.39.3-1.el8_8 |
| AlmaLinux:8 | git-instaweb | before 2.39.3-1.el8_8 | 2.39.3-1.el8_8 |
| AlmaLinux:8 | git-subtree | before 2.39.3-1.el8_8 | 2.39.3-1.el8_8 |
| AlmaLinux:8 | git-svn | before 2.39.3-1.el8_8 | 2.39.3-1.el8_8 |
| AlmaLinux:8 | gitk | before 2.39.3-1.el8_8 | 2.39.3-1.el8_8 |
| AlmaLinux:8 | gitweb | before 2.39.3-1.el8_8 | 2.39.3-1.el8_8 |
| AlmaLinux:8 | perl-Git | before 2.39.3-1.el8_8 | 2.39.3-1.el8_8 |
| AlmaLinux:8 | perl-Git-SVN | before 2.39.3-1.el8_8 | 2.39.3-1.el8_8 |
| AlmaLinux:9 | git | before 2.39.3-1.el9_2 | 2.39.3-1.el9_2 |
| AlmaLinux:9 | git-all | before 2.39.3-1.el9_2 | 2.39.3-1.el9_2 |
| AlmaLinux:9 | git-core | before 2.39.3-1.el9_2 | 2.39.3-1.el9_2 |
| AlmaLinux:9 | git-core-doc | before 2.39.3-1.el9_2 | 2.39.3-1.el9_2 |
| AlmaLinux:9 | git-credential-libsecret | before 2.39.3-1.el9_2 | 2.39.3-1.el9_2 |
| AlmaLinux:9 | git-daemon | before 2.39.3-1.el9_2 | 2.39.3-1.el9_2 |
| AlmaLinux:9 | git-email | before 2.39.3-1.el9_2 | 2.39.3-1.el9_2 |
| AlmaLinux:9 | git-gui | before 2.39.3-1.el9_2 | 2.39.3-1.el9_2 |
| AlmaLinux:9 | git-instaweb | before 2.39.3-1.el9_2 | 2.39.3-1.el9_2 |
+96
Same product
git for windows project: all recordsOther highest-scoring records for the same primary product.
- CVE-2023-29012Git CMD erroneously executes `doskey.exe` in the current directory, if it exists31Monitor
- CVE-2023-29011Git for Windows's config file of `connect.exe` is susceptible to malicious placing31Monitor
- CVE-2023-23618gitk can inadvertently call executables in the worktree31Monitor
Published before and after this one in the same product
- ← EarlierCVE-2016-9274Nov 11, 2016 · Untrusted search path vulnerability in Git 1.x for Windows allows local users to gain privileges via a Trojan horse git.exe file in the curr31Monitor
- ← EarlierCVE-2023-22743Feb 14, 2023 · Git for Windows' installer is susceptible to DLL side loading attacks29Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| almalinux:git | 2.39.3-1.el9_2 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:git-all | 2.39.3-1.el9_2 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:git-core | 2.39.3-1.el9_2 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:git-core-doc | 2.39.3-1.el9_2 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:git-credential-libsecret | 2.39.3-1.el9_2 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:git-daemon | 2.39.3-1.el9_2 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:git-email | 2.39.3-1.el9_2 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:git-gui | 2.39.3-1.el9_2 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:git-instaweb | 2.39.3-1.el9_2 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:git-subtree | 2.39.3-1.el9_2 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:git-svn | 2.39.3-1.el9_2 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:gitk | 2.39.3-1.el9_2 · AlmaLinux:9 | Package registry (OSV) |
| alpine:git | 2.32.7-r0 · Alpine:v3.14 | Package registry (OSV) |
| debian:git | 1:2.39.5-0+deb12u1 · Debian:12 | Package registry (OSV) |
| opensuse:git | 2.35.3-150300.10.27.1 · openSUSE:Leap 15.4 | Package registry (OSV) |
| red hat:git | 0:2.18.4-3.el8_1 · Red Hat:rhel_e4s:8.1::appstream | Package registry (OSV) |
| red hat:git-all | 0:2.18.4-3.el8_1 · Red Hat:rhel_e4s:8.1::appstream | Package registry (OSV) |
| red hat:git-core | 0:2.18.4-3.el8_1 · Red Hat:rhel_e4s:8.1::appstream | Package registry (OSV) |
| red hat:git-core-debuginfo | 0:2.18.4-3.el8_1 · Red Hat:rhel_e4s:8.1::appstream | Package registry (OSV) |
| red hat:git-core-doc | 0:2.18.4-3.el8_1 · Red Hat:rhel_e4s:8.1::appstream | Package registry (OSV) |
| red hat:git-daemon | 0:2.18.4-3.el8_1 · Red Hat:rhel_e4s:8.1::appstream | Package registry (OSV) |
| red hat:git-daemon-debuginfo | 0:2.18.4-3.el8_1 · Red Hat:rhel_e4s:8.1::appstream | Package registry (OSV) |
| red hat:git-debuginfo | 0:2.18.4-3.el8_1 · Red Hat:rhel_e4s:8.1::appstream | Package registry (OSV) |
| red hat:git-debugsource | 0:2.18.4-3.el8_1 · Red Hat:rhel_e4s:8.1::appstream | Package registry (OSV) |
| red hat:git-email | 0:2.18.4-3.el8_1 · Red Hat:rhel_e4s:8.1::appstream | Package registry (OSV) |
| red hat:git-gui | 0:2.18.4-3.el8_1 · Red Hat:rhel_e4s:8.1::appstream | Package registry (OSV) |
| red hat:git-instaweb | 0:2.18.4-3.el8_1 · Red Hat:rhel_e4s:8.1::appstream | Package registry (OSV) |
| rocky linux:git | 0:2.39.3-1.el8_8 · Rocky Linux:8 | Package registry (OSV) |
| suse:git | 2.35.3-150300.10.27.1 · SUSE:Linux Enterprise Module for Basesystem 15 SP4 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
National notice (Türkiye Cybersecurity Directorate / USOM)
Official security notices citing this record; remediation advice is on the agency's page.
- TR-23-0255 · May 2, 2023(Git Güvenlik Bildirimi)
Technical details
Attack conditions
- Someone with local access to the system can trigger it.
- A low-privileged account is enough.
- A user must open a link or visit a page.
- Special conditions such as timing or configuration are required.
If successful
- Confidentiality
- none
- Integrity
- low · data or configuration can be modified
- Availability
- none
- Attack vector
- Local
- Attack complexity
- High
- Privileges required
- Low
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality impact
- None
- Integrity impact
- Low
- Availability impact
- None
Weakness class (CWE)
CWE-22 · Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')CVSS vector
CVSS:3.1/AV:L/AC:H/PR:L/UI:R/S:U/C:N/I:L/A:N
nvd-primary
Root cause
A user-supplied file name is joined with the allowed directory, but the result is never checked to confirm it is still inside that directory.
The bug in code
The whole CWE-22 classA representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.
Vulnerable
const file = path.join(ROOT, req.query.name);
res.sendFile(file);Fixed
const file = path.resolve(ROOT, req.query.name);
if (!file.startsWith(ROOT + path.sep)) {
return res.sendStatus(400);
}
res.sendFile(file);Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
- Path TraversalCAPEC-126likelihood: High · Very High
- Using Slashes and URL Encoding Combined to Bypass Validation LogicCAPEC-64likelihood: High · High
- Manipulating Web Input to File System CallsCAPEC-76likelihood: High · Very High
- Using Escaped Slashes in Alternate EncodingCAPEC-78likelihood: High · High
- Using Slashes in Alternate EncodingCAPEC-79likelihood: High · High
ATT&CK techniques
—
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (11 more)Show less
- axcheron.github.io/exploit-101-format-strings/#writing-to-the-stack
- github.com/git-for-windows/git/releases/tag/v2.40.1.windows.1
- github.com/git-for-windows/git/security/advisories/GHSA-9w66-8mq8-5vm8
- github.com/msys2/MINGW-packages/pull/10461
- lists.debian.org/debian-lts-announce/2024/06/msg00018.html
- lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/PI7FZ4NNR5S5J5K6AMVQBH2JFP6NE4L7/
- lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/RKOXOAZ42HLXHXTW6JZI4L5DAIYDTYCU/
- lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/YFZWGQKB6MM5MNF2DLFTD7KS2KWPICKL/
- pubs.opengroup.org/onlinepubs/9699919799/functions/printf.html
- security.gentoo.org/glsa/202312-15
- lists.debian.org/debian-lts-announce/2024/09/msg00009.html
Vendor advisories and official records. Exploit/PoC links are deliberately left out.