# CVE-2018-1000021: Command injection in n/a

> A malicious Git server or MITM attack can exploit input validation errors in the Git client to execute arbitrary code on the user's machine.

- **Severity:** Medium 5.0 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:L/I:L/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 9 Feb 2018
- **Updated:** 5 Aug 2024
- **Also known as:** DEBIAN-CVE-2018-1000021, GHSA-vpq8-fvqp-vj6h, UBUNTU-CVE-2018-1000021

## What is CVE-2018-1000021?

CVE-2018-1000021 is a medium-severity command injection vulnerability in n/a, published on 9 Feb 2018. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

GIT version 2.15.1 and earlier contains a Input Validation Error vulnerability in Client that can result in problems including messing up terminal configuration to RCE. This attack appear to be exploitable via The user must interact with a malicious git server, (or have their traffic modified in a MITM attack).

Weakness: CWE-20 (Improper Input Validation)

## Which versions are affected by CVE-2018-1000021?

It affects 1 product.


Products: Git-Scm Git.

## How do I fix CVE-2018-1000021?

No fix has been published for CVE-2018-1000021 yet. Limit exposure of the affected software until one is available.

## Is CVE-2018-1000021 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2022-23521](https://insights.sbomify.com/CVE-2022-23521/): gitattributes parsing integer overflow in git (critical 9.8)
- [CVE-2022-41903](https://insights.sbomify.com/CVE-2022-41903/): Integer overflow in `git archive`, `git log --format` leading to RCE in git (critical 9.8)
- [CVE-2019-1353](https://insights.sbomify.com/CVE-2019-1353/): Security feature bypass in Git (critical 9.8)
- [CVE-2016-2315](https://insights.sbomify.com/CVE-2016-2315/): Memory corruption in n/a (critical 9.8)
- [CVE-2016-2324](https://insights.sbomify.com/CVE-2016-2324/): Integer overflow in n/a (critical 9.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2018-1000021 and fix it if it is affected.

What it is: CVE-2018-1000021 is a medium-severity command injection vulnerability in n/a, published on 9 Feb 2018. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2018-1000021 in the wild and no public exploit code.

Affected product: n/a. 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-2018-1000021/ (Markdown: https://insights.sbomify.com/CVE-2018-1000021/index.md)
```

## Sources

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

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