Skip to content
Noroxi
NVD / CVE Program· CNA GitHub_M

CVE-2023-29007: Arbitrary configuration injection via `git submodule deinit`

Noroxi assessment

Priority: Monitor (action score 33/100)

  • Public proof-of-concept code exists (GitHub); there is no record of exploitation in the wild.
  • Probability of exploitation in the next 30 days: 5.6% (FIRST EPSS); higher than 92.8% of all records.
  • Someone with local access to the system can trigger it. No account or password is required. A user must open a link or visit a page. No special conditions are required; it is repeatable.
  • 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

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`.

HighCVSS 7.8 · v3.1—Proof of concept Fix available
Published
Apr 25, 2023
Updated
Jun 17, 2026
EPSS
5.6% · 92th percentile

Report tools

JSON

Action score

33

Monitor

Low priority for now.

CVSS
31 / 40 · 7.8 / 10
CISA KEV
0 / 30 · Not listed
EPSS
2 / 30 · 5.6%

CNA vs NVD score

NVD
7.8
CNA · GitHub_M
7.0
0.8 point gap

CVSS:3.1/AV:L/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:H

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
  • Proof of concept exists, no weaponized module
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2023-29007

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

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 help

Affected 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.

VendorProduct
git-scmgit
fedoraprojectfedora

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • fedoraproject fedora36
  • fedoraproject fedora37
  • fedoraproject fedora38
  • git-scm git2.33.0 and later · before 2.33.8
  • git-scm git2.34.0 and later · before 2.34.8
  • git-scm git2.35.0 and later · before 2.35.8
  • git-scm git2.36.0 and later · before 2.36.5
  • git-scm gitbefore 2.30.9
  • git-scm git2.38.0 and later · before 2.38.5
  • git-scm git2.39.0 and later · before 2.39.3
  • git-scm git2.37.0 and later · before 2.37.7
  • git-scm git2.31.0 and later · before 2.31.8
  • git-scm git2.32.0 and later · before 2.32.7
  • git-scm git2.40.0

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.9, >= 2.31.0, < 2.31.8, >= 2.32.0, < 2.32.7, >= 2.33.0, < 2.33.8, >= 2.34.0, < 2.34.8, >= 2.35.0, < 2.35.8, >= 2.36.0, < 2.36.6, >= 2.37.0, < 2.37.7, >= 2.38.0, < 2.38.5, >= 2.39.0, < 2.39.3, >= 2.40.0, < 2.40.1affected

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
AlmaLinux:8gitbefore 2.39.3-1.el8_82.39.3-1.el8_8
AlmaLinux:8git-allbefore 2.39.3-1.el8_82.39.3-1.el8_8
AlmaLinux:8git-corebefore 2.39.3-1.el8_82.39.3-1.el8_8
AlmaLinux:8git-core-docbefore 2.39.3-1.el8_82.39.3-1.el8_8
AlmaLinux:8git-credential-libsecretbefore 2.39.3-1.el8_82.39.3-1.el8_8
AlmaLinux:8git-daemonbefore 2.39.3-1.el8_82.39.3-1.el8_8
AlmaLinux:8git-emailbefore 2.39.3-1.el8_82.39.3-1.el8_8
AlmaLinux:8git-guibefore 2.39.3-1.el8_82.39.3-1.el8_8
AlmaLinux:8git-instawebbefore 2.39.3-1.el8_82.39.3-1.el8_8
AlmaLinux:8git-subtreebefore 2.39.3-1.el8_82.39.3-1.el8_8
AlmaLinux:8git-svnbefore 2.39.3-1.el8_82.39.3-1.el8_8
AlmaLinux:8gitkbefore 2.39.3-1.el8_82.39.3-1.el8_8
AlmaLinux:8gitwebbefore 2.39.3-1.el8_82.39.3-1.el8_8
AlmaLinux:8perl-Gitbefore 2.39.3-1.el8_82.39.3-1.el8_8
AlmaLinux:8perl-Git-SVNbefore 2.39.3-1.el8_82.39.3-1.el8_8
AlmaLinux:9gitbefore 2.39.3-1.el9_22.39.3-1.el9_2
AlmaLinux:9git-allbefore 2.39.3-1.el9_22.39.3-1.el9_2
AlmaLinux:9git-corebefore 2.39.3-1.el9_22.39.3-1.el9_2
AlmaLinux:9git-core-docbefore 2.39.3-1.el9_22.39.3-1.el9_2
AlmaLinux:9git-credential-libsecretbefore 2.39.3-1.el9_22.39.3-1.el9_2
AlmaLinux:9git-daemonbefore 2.39.3-1.el9_22.39.3-1.el9_2
AlmaLinux:9git-emailbefore 2.39.3-1.el9_22.39.3-1.el9_2
AlmaLinux:9git-guibefore 2.39.3-1.el9_22.39.3-1.el9_2
AlmaLinux:9git-instawebbefore 2.39.3-1.el9_22.39.3-1.el9_2

+96

Other 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 r
    68This week
  • CVE-2025-48384Git allows arbitrary code execution through broken config quotingKEV
    63This week
  • CVE-2021-21300malicious repositories can execute remote code while cloning
    60This week

Published before and after this one in the same product

  • ← EarlierCVE-2023-23946Feb 14, 2023 · Git's `git apply` overwriting paths outside the working tree
    30Monitor
  • ← EarlierCVE-2023-25652Apr 25, 2023 · "git apply --reject" partially-controlled arbitrary file write
    46Plan
  • Later →CVE-2024-32004May 14, 2024 · Git vulnerable to Remote Code Execution while cloning special-crafted local repositories
    31Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
almalinux:git2.39.3-1.el9_2 · AlmaLinux:9Package registry (OSV)
almalinux:git-all2.39.3-1.el9_2 · AlmaLinux:9Package registry (OSV)
almalinux:git-core2.39.3-1.el9_2 · AlmaLinux:9Package registry (OSV)
almalinux:git-core-doc2.39.3-1.el9_2 · AlmaLinux:9Package registry (OSV)
almalinux:git-credential-libsecret2.39.3-1.el9_2 · AlmaLinux:9Package registry (OSV)
almalinux:git-daemon2.39.3-1.el9_2 · AlmaLinux:9Package registry (OSV)
almalinux:git-email2.39.3-1.el9_2 · AlmaLinux:9Package registry (OSV)
almalinux:git-gui2.39.3-1.el9_2 · AlmaLinux:9Package registry (OSV)
almalinux:git-instaweb2.39.3-1.el9_2 · AlmaLinux:9Package registry (OSV)
almalinux:git-subtree2.39.3-1.el9_2 · AlmaLinux:9Package registry (OSV)
almalinux:git-svn2.39.3-1.el9_2 · AlmaLinux:9Package registry (OSV)
almalinux:gitk2.39.3-1.el9_2 · AlmaLinux:9Package registry (OSV)
alpine:git2.32.7-r0 · Alpine:v3.14Package registry (OSV)
debian:git1:2.39.5-0+deb12u1 · Debian:12Package registry (OSV)
opensuse:git2.35.3-150300.10.27.1 · openSUSE:Leap 15.4Package registry (OSV)
red hat:git0:2.18.4-3.el8_1 · Red Hat:rhel_e4s:8.1::appstreamPackage registry (OSV)
red hat:git-all0:2.18.4-3.el8_1 · Red Hat:rhel_e4s:8.1::appstreamPackage registry (OSV)
red hat:git-core0:2.18.4-3.el8_1 · Red Hat:rhel_e4s:8.1::appstreamPackage registry (OSV)
red hat:git-core-debuginfo0:2.18.4-3.el8_1 · Red Hat:rhel_e4s:8.1::appstreamPackage registry (OSV)
red hat:git-core-doc0:2.18.4-3.el8_1 · Red Hat:rhel_e4s:8.1::appstreamPackage registry (OSV)
red hat:git-daemon0:2.18.4-3.el8_1 · Red Hat:rhel_e4s:8.1::appstreamPackage registry (OSV)
red hat:git-daemon-debuginfo0:2.18.4-3.el8_1 · Red Hat:rhel_e4s:8.1::appstreamPackage registry (OSV)
red hat:git-debuginfo0:2.18.4-3.el8_1 · Red Hat:rhel_e4s:8.1::appstreamPackage registry (OSV)
red hat:git-debugsource0:2.18.4-3.el8_1 · Red Hat:rhel_e4s:8.1::appstreamPackage registry (OSV)
red hat:git-email0:2.18.4-3.el8_1 · Red Hat:rhel_e4s:8.1::appstreamPackage registry (OSV)
red hat:git-gui0:2.18.4-3.el8_1 · Red Hat:rhel_e4s:8.1::appstreamPackage registry (OSV)
red hat:git-instaweb0:2.18.4-3.el8_1 · Red Hat:rhel_e4s:8.1::appstreamPackage registry (OSV)
rocky linux:git0:2.39.3-1.el8_8 · Rocky Linux:8Package registry (OSV)
suse:git2.35.3-150300.10.27.1 · SUSE:Linux Enterprise Module for Basesystem 15 SP4Package registry (OSV)

Exploit status

Proof of concept available

A public proof of concept or detection signature exists. Exploit knowledge is out there; don't delay patching.

Evidence

  • Proof-of-concept repository on GitHub ×2

Noroxi does not host or link to exploit code. Metasploit module names and Nuclei template ids are shown (names, not code); Exploit-DB entries and PoC repositories are given as counts only.

Public exploit evidence
SourceKindDate
Proof-of-concept repository on GitHubstars:362023-04-26
Proof-of-concept repository on GitHubstars:22023-05-06

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.

  1. Published
  2. First PoCsame day
  3. TodayOct 27, 2026+1281 d
EPSS, last 120 days

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.

Finders, 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.

All national notices →

Technical details

Attack conditions

  • Someone with local access to the system can trigger it.
  • No account or password is required.
  • A user must open a link or visit a page.
  • 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
None
User interaction
Required
Scope
Unchanged
Confidentiality impact
High
Integrity impact
High
Availability impact
High

CVSS vector

CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

nvd-primary

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

All records