CVE-2022-29187: Bypass of safe.directory protections in Git
Noroxi assessment
Priority: Monitor (action score 31/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.44% (FIRST EPSS).
- Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: git (AlmaLinux:8) 2.39.1-1.el8; git-all (AlmaLinux:8) 2.39.1-1.el8; git-core (AlmaLinux:8) 2.39.1-1.el8.
Low priority for now. Upgrade to git (AlmaLinux:8) 2.39.1-1.el8; git-all (AlmaLinux:8) 2.39.1-1.el8; git-core (AlmaLinux:8) 2.39.1-1.el8 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
Git is a distributed revision control system. Git prior to versions 2.37.1, 2.36.2, 2.35.4, 2.34.4, 2.33.4, 2.32.3, 2.31.4, and 2.30.5, is vulnerable to privilege escalation in all platforms. An unsuspecting user could still be affected by the issue reported in CVE-2022-24765, for example when navigating as root into a shared tmp directory that is owned by them, but where an attacker could create a git repository. Versions 2.37.1, 2.36.2, 2.35.4, 2.34.4, 2.33.4, 2.32.3, 2.31.4, and 2.30.5 contain a patch for this issue. The simplest way to avoid being affected by the exploit described in the example is to avoid running git as root (or an Administrator in Windows), and if needed to reduce its use to a minimum. While a generic workaround is not possible, a system could be hardened from the exploit described in the example by removing any such repository if it exists already and creating one as root to block any future attacks.
- Published
- Jul 12, 2022
- Updated
- Jun 17, 2026
- EPSS
- 0.4% · 38th percentile
- CWE
- CWE-282
Report tools
Action score
31
Monitor
Low priority for now.
- CVSS
- 31 / 40 · 7.8 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.4%
CNA vs NVD score
- NVD
- 7.8
- CNA · GitHub_M
- 7.8
- agree
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-scm | git | cpe:2.3:a:git-scm:git |
| debian | debian linux | cpe:2.3:o:debian:debian_linux |
| fedoraproject | fedora | cpe:2.3:o:fedoraproject:fedora |
| apple | xcode | cpe:2.3:a:apple:xcode |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- apple xcodebefore 14.1
- debian debian linux10.0
- fedoraproject fedora35
- fedoraproject fedora36
- fedoraproject fedora37
- git-scm git2.35.2 and later · before 2.35.4
- git-scm git2.30.3 and later · before 2.30.5
- git-scm git2.37.0 and later · before 2.37.1
- git-scm git2.36.0 and later · before 2.36.2
- git-scm git2.31.2 and later · before 2.31.4
- git-scm git2.32.1 and later · before 2.32.3
- git-scm git2.33.2 and later · before 2.33.4
- git-scm git2.34.2 and later · before 2.34.4
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 git
- >= 2.30.3, < 2.30.5, >= 2.31.2, < 2.31.4, >= 2.32.1, < 2.32.3, >= 2.33.2, < 2.33.4, >= 2.34.2, < 2.34.4, >= 2.35.2, < 2.35.4, >= 2.36, < 2.36.2, >= 2.37, < 2.37.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.1-1.el8 | 2.39.1-1.el8 |
| AlmaLinux:8 | git-all | before 2.39.1-1.el8 | 2.39.1-1.el8 |
| AlmaLinux:8 | git-core | before 2.39.1-1.el8 | 2.39.1-1.el8 |
| AlmaLinux:8 | git-core-doc | before 2.39.1-1.el8 | 2.39.1-1.el8 |
| AlmaLinux:8 | git-credential-libsecret | before 2.39.1-1.el8 | 2.39.1-1.el8 |
| AlmaLinux:8 | git-daemon | before 2.39.1-1.el8 | 2.39.1-1.el8 |
| AlmaLinux:8 | git-email | before 2.39.1-1.el8 | 2.39.1-1.el8 |
| AlmaLinux:8 | git-gui | before 2.39.1-1.el8 | 2.39.1-1.el8 |
| AlmaLinux:8 | git-instaweb | before 2.39.1-1.el8 | 2.39.1-1.el8 |
| AlmaLinux:8 | git-subtree | before 2.39.1-1.el8 | 2.39.1-1.el8 |
| AlmaLinux:8 | git-svn | before 2.39.1-1.el8 | 2.39.1-1.el8 |
| AlmaLinux:8 | gitk | before 2.39.1-1.el8 | 2.39.1-1.el8 |
| AlmaLinux:8 | gitweb | before 2.39.1-1.el8 | 2.39.1-1.el8 |
| AlmaLinux:8 | perl-Git | before 2.39.1-1.el8 | 2.39.1-1.el8 |
| AlmaLinux:8 | perl-Git-SVN | before 2.39.1-1.el8 | 2.39.1-1.el8 |
| AlmaLinux:9 | git | before 2.39.1-1.el9 | 2.39.1-1.el9 |
| AlmaLinux:9 | git-all | before 2.39.1-1.el9 | 2.39.1-1.el9 |
| AlmaLinux:9 | git-core | before 2.39.1-1.el9 | 2.39.1-1.el9 |
| AlmaLinux:9 | git-core-doc | before 2.39.1-1.el9 | 2.39.1-1.el9 |
| AlmaLinux:9 | git-credential-libsecret | before 2.39.1-1.el9 | 2.39.1-1.el9 |
| AlmaLinux:9 | git-daemon | before 2.39.1-1.el9 | 2.39.1-1.el9 |
| AlmaLinux:9 | git-email | before 2.39.1-1.el9 | 2.39.1-1.el9 |
| AlmaLinux:9 | git-gui | before 2.39.1-1.el9 | 2.39.1-1.el9 |
| AlmaLinux:9 | git-instaweb | before 2.39.1-1.el9 | 2.39.1-1.el9 |
+88
Same product
git-scm: all recordsOther highest-scoring records for the same primary product.
- CVE-2018-17456Git before 2.14.5, 2.15.x before 2.15.3, 2.16.x before 2.16.5, 2.17.x before 2.17.2, 2.18.x before 2.18.1, and 2.19.x before 2.19.1 allows r68This week
- CVE-2025-48384Git allows arbitrary code execution through broken config quotingKEV63This week
- CVE-2021-21300malicious repositories can execute remote code while cloning60This week
Published before and after this one in the same product
- ← EarlierCVE-2022-24975Feb 11, 2022 · The --mirror documentation for Git through 2.35.1 does not mention the availability of deleted content, aka the "GitBleed" issue.31Monitor
- ← EarlierCVE-2022-24765Apr 12, 2022 · Uncontrolled search for the Git directory in Git for Windows31Monitor
- Later →CVE-2022-39253Oct 19, 2022 · Git subject to exposure of sensitive information via local clone of symbolic links22Monitor
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.1-1.el9 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:git-all | 2.39.1-1.el9 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:git-core | 2.39.1-1.el9 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:git-core-doc | 2.39.1-1.el9 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:git-credential-libsecret | 2.39.1-1.el9 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:git-daemon | 2.39.1-1.el9 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:git-email | 2.39.1-1.el9 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:git-gui | 2.39.1-1.el9 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:git-instaweb | 2.39.1-1.el9 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:git-subtree | 2.39.1-1.el9 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:git-svn | 2.39.1-1.el9 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:gitk | 2.39.1-1.el9 · AlmaLinux:9 | Package registry (OSV) |
| alpine:git | 2.30.5-r0 · Alpine:v3.13 | Package registry (OSV) |
| alpine:libgit2 | 1.4.4-r0 · Alpine:v3.17 | Package registry (OSV) |
| debian:git | 1:2.37.2-1 · Debian:12 | Package registry (OSV) |
| opensuse:git | 2.26.2-150000.41.1 · openSUSE:Leap 15.3 | Package registry (OSV) |
| opensuse:libgit2 | 1.3.0-150400.3.3.1 · openSUSE:Leap 15.4 | Package registry (OSV) |
| red hat:git | 0:2.39.1-1.el9 · Red Hat:enterprise_linux:9::appstream | Package registry (OSV) |
| red hat:git-all | 0:2.39.1-1.el9 · Red Hat:enterprise_linux:9::appstream | Package registry (OSV) |
| red hat:git-core | 0:2.39.1-1.el9 · Red Hat:enterprise_linux:9::appstream | Package registry (OSV) |
| red hat:git-core-debuginfo | 0:2.39.1-1.el9 · Red Hat:enterprise_linux:9::appstream | Package registry (OSV) |
| red hat:git-core-doc | 0:2.39.1-1.el9 · Red Hat:enterprise_linux:9::appstream | Package registry (OSV) |
| red hat:git-credential-libsecret | 0:2.39.1-1.el9 · Red Hat:enterprise_linux:9::appstream | Package registry (OSV) |
| red hat:git-credential-libsecret-debuginfo | 0:2.39.1-1.el9 · Red Hat:enterprise_linux:9::appstream | Package registry (OSV) |
| red hat:git-daemon | 0:2.39.1-1.el9 · Red Hat:enterprise_linux:9::appstream | Package registry (OSV) |
| red hat:git-daemon-debuginfo | 0:2.39.1-1.el9 · Red Hat:enterprise_linux:9::appstream | Package registry (OSV) |
| red hat:git-debuginfo | 0:2.39.1-1.el9 · Red Hat:enterprise_linux:9::appstream | Package registry (OSV) |
| red hat:git-debugsource | 0:2.39.1-1.el9 · Red Hat:enterprise_linux:9::appstream | Package registry (OSV) |
| red hat:git-email | 0:2.39.1-1.el9 · Red Hat:enterprise_linux:9::appstream | Package registry (OSV) |
| suse:git | 2.26.2-150000.41.1 · SUSE:Linux Enterprise High Performance Computing 15-ESPOS | Package registry (OSV) |
+1
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.
No history yet (it accumulates with the daily EPSS job).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
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).
Technical details
Attack conditions
- Someone with local access to the system can trigger it.
- A low-privileged account is enough.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- high · data can be read
- Integrity
- high · data or configuration can be modified
- Availability
- high · the service can be disrupted
- Attack vector
- Local
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- High
Weakness class (CWE)
CWE-282 · Improper Ownership ManagementCVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
nvd-primary
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)
ATT&CK techniques
- Obfuscated Files or Information: HTML SmugglingT1027.006
- Obfuscated Files or Information: Embedded PayloadsT1027.009
- Hide Artifacts: Resource ForkingT1564.009
- Hijack Execution Flow: Executable Installer File Permissions WeaknessT1574.005
- Hijack Execution Flow: Services File Permissions WeaknessT1574.010
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (14 more)Show less
- www.openwall.com/lists/oss-security/2022/07/14/1
- github.blog/2022-04-12-git-security-vulnerability-announced
- github.com/git/git/security/advisories/GHSA-j342-m5hw-rr3v
- lists.debian.org/debian-lts-announce/2022/12/msg00025.html
- lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/DDI325LOO2XBDDKLINOAQJEG6MHAURZE/
- lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/DIKWISWUDFT2FAITYIA6372BVLH3OOOC/
- lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/HVOLER2PIGMHPQMDGG4RDE2KZB74QLA2/
- lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/TRZG5CDUQ27OWTPC5MQOR4UASNXHWEZS/
- lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/UDZRZAL7QULOB6V7MKT66MOMWJLBJPX4/
- lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/YROCMBWYFKRSS64PO6FUNM6L7LKBUKVW/
- lore.kernel.org/git/xmqqv8s2fefi.fsf%40gitster.g/T/#u
- security.gentoo.org/glsa/202312-15
- security.gentoo.org/glsa/202401-17
- support.apple.com/kb/HT213496
Vendor advisories and official records. Exploit/PoC links are deliberately left out.