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

> Attackers can inject arbitrary configuration into Git settings via crafted submodule URLs, leading to remote code execution when specific commands are run.

- **Severity:** High 7.0 (`CVSS:3.1/AV:L/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 25 Apr 2023
- **Updated:** 4 Nov 2025
- **Also known as:** ALPINE-CVE-2023-29007, CLEANSTART-2026-BE00083, DEBIAN-CVE-2023-29007, GHSA-v48j-4xgg-4844, UBUNTU-CVE-2023-29007

## What is CVE-2023-29007?

CVE-2023-29007 is a high-severity code injection vulnerability in Fedoraproject Fedora, published on 25 Apr 2023. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

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

Weakness: CWE-74 (Improper Neutralization of Special Elements in Output Used by a Downstream Component)

## Which versions are affected by CVE-2023-29007?

It affects 2 products.


Products: Fedoraproject Fedora, Git-Scm Git.

## How do I fix CVE-2023-29007?

Upgrade to a fixed version.

## Is CVE-2023-29007 being exploited?

There is no known exploitation of CVE-2023-29007 in the wild and no public exploit code.

Public exploit code:

- PoC repository for CVE-2023-29007 (github_poc): https://github.com/ethiack/CVE-2023-29007
- https://github.com/x-Defender/CVE-2023-29007_win-version (github_poc): https://github.com/x-Defender/CVE-2023-29007_win-version

## Other vulnerabilities in Fedoraproject Fedora

- [CVE-2024-4577](https://insights.sbomify.com/CVE-2024-4577/): PHP-CGI OS Command Injection (critical 9.8, exploited in the wild)
- [CVE-2021-39226](https://insights.sbomify.com/CVE-2021-39226/): Grafana Authentication Bypass (critical 9.8, exploited in the wild)
- [CVE-2019-5544](https://insights.sbomify.com/CVE-2019-5544/): VMware ESXi and Horizon DaaS OpenSLP Heap-Based Buffer Overflow (critical 9.8, exploited in the wild)
- [CVE-2024-4947](https://insights.sbomify.com/CVE-2024-4947/): Google Chromium V8 Type Confusion (critical 9.6, exploited in the wild)
- [CVE-2024-4671](https://insights.sbomify.com/CVE-2024-4671/): Google Chromium Visuals Use-After-Free (critical 9.6, exploited in the wild)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-29007 and fix it if it is affected.

What it is: CVE-2023-29007 is a high-severity code injection vulnerability in Fedoraproject Fedora, published on 25 Apr 2023. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2023-29007 in the wild and no public exploit code.

Affected product: Fedoraproject Fedora. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2023-29007/ (Markdown: https://insights.sbomify.com/CVE-2023-29007/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2023-29007
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2023-29007
- OSV: https://osv.dev/vulnerability/CVE-2023-29007

---
From sbomify Insights: https://insights.sbomify.com/CVE-2023-29007/
Summaries are generated and may contain mistakes; the official description above is the record.