# CVE-2014-9938: Code injection in n/a

> A malicious Git repository can execute arbitrary code by exploiting unsanitized branch names in the shell prompt configuration.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H`)
- **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:** Yes
- **Published:** 20 Mar 2017
- **Updated:** 6 Aug 2024
- **Also known as:** DEBIAN-CVE-2014-9938, GHSA-6vhm-rfmv-gf4j, UBUNTU-CVE-2014-9938, USN-3243-1

## What is CVE-2014-9938?

CVE-2014-9938 is a high-severity code injection vulnerability in n/a, published on 20 Mar 2017. 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

contrib/completion/git-prompt.sh in Git before 1.9.3 does not sanitize branch names in the PS1 variable, allowing a malicious repository to cause code execution.

Weakness: CWE-116 (Improper Encoding or Escaping of Output)

## Which versions are affected by CVE-2014-9938?

It affects 1 product.


Products: Git-Scm Git.

## How do I fix CVE-2014-9938?

Upgrade to a fixed version.

## Is CVE-2014-9938 being exploited?

There is no known exploitation of CVE-2014-9938 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-2014-9938 and fix it if it is affected.

What it is: CVE-2014-9938 is a high-severity code injection vulnerability in n/a, published on 20 Mar 2017. 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-2014-9938 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-2014-9938/ (Markdown: https://insights.sbomify.com/CVE-2014-9938/index.md)
```

## Sources

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

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