# CVE-2017-8386: Command injection in n/a

> Authenticated users can gain privileges or execute code via repository names starting with a dash in git-shell.

- **Severity:** High 8.8 (`CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 1 Jun 2017
- **Updated:** 5 Aug 2024
- **Also known as:** ALPINE-CVE-2017-8386, DEBIAN-CVE-2017-8386, DLA-938-1, DSA-3848-1, GHSA-xqh5-ghjx-6xv5, MGASA-2017-0153, SUSE-SU-2017:1357-1, SUSE-SU-2017:1432-1, UBUNTU-CVE-2017-8386, USN-3287-1

## What is CVE-2017-8386?

CVE-2017-8386 is a high-severity command injection vulnerability in Canonical Ubuntu Linux, published on 1 Jun 2017. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

git-shell in git before 2.4.12, 2.5.x before 2.5.6, 2.6.x before 2.6.7, 2.7.x before 2.7.5, 2.8.x before 2.8.5, 2.9.x before 2.9.4, 2.10.x before 2.10.3, 2.11.x before 2.11.2, and 2.12.x before 2.12.3 might allow remote authenticated users to gain privileges via a repository name that starts with a - (dash) character.

## Which versions are affected by CVE-2017-8386?

It affects 5 products.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `git` | SUSE:Linux Enterprise Server 12 SP1 | All versions | 2.12.3-26.1 |
| `git` | SUSE:Linux Enterprise Server 12 SP2 | All versions | 2.12.3-26.1 |
| `git` | SUSE:Linux Enterprise Server for Raspberry Pi 12 SP2 | All versions | 2.12.3-26.1 |
| `git` | SUSE:Linux Enterprise Server for SAP Applications 12 SP1 | All versions | 2.12.3-26.1 |
| `git` | SUSE:Linux Enterprise Server for SAP Applications 12 SP2 | All versions | 2.12.3-26.1 |
| `git` | SUSE:Linux Enterprise Software Development Kit 11 SP4 | All versions | 1.7.12.4-0.17.1 |
| `git` | SUSE:Linux Enterprise Software Development Kit 12 SP1 | All versions | 2.12.3-26.1 |
| `git` | SUSE:Linux Enterprise Software Development Kit 12 SP2 | All versions | 2.12.3-26.1 |
| `git` | SUSE:Studio Onsite 1.3 | All versions | 1.7.12.4-0.17.1 |

Products: Canonical Ubuntu Linux, Debian Debian Linux, Fedoraproject Fedora, Git Git-Shell, Opensuse Leap.

## How do I fix CVE-2017-8386?

Upgrade to a fixed version.

## Is CVE-2017-8386 being exploited?

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

Public exploit code:

- PoC for CVE-2017-8386 Git-Shell sandbox bypass vulnerability. (github_poc): https://github.com/suz1n/WHS3_vulhub

## Other vulnerabilities in Canonical Ubuntu Linux

- [CVE-2020-11651](https://insights.sbomify.com/CVE-2020-11651/): SaltStack Salt Authentication Bypass (critical 9.8, exploited in the wild)
- [CVE-2020-7247](https://insights.sbomify.com/CVE-2020-7247/): OpenSMTPD Remote Code Execution (critical 9.8, exploited in the wild)
- [CVE-2019-16928](https://insights.sbomify.com/CVE-2019-16928/): Exim Out-of-bounds Write (critical 9.8, exploited in the wild)
- [CVE-2018-6789](https://insights.sbomify.com/CVE-2018-6789/): Exim Buffer Overflow (critical 9.8, exploited in the wild)
- [CVE-2015-2590](https://insights.sbomify.com/CVE-2015-2590/): Oracle Java SE and Java SE Embedded Remote Code Execution (critical 9.8, exploited in the wild)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2017-8386 and fix it if it is affected.

What it is: CVE-2017-8386 is a high-severity command injection vulnerability in Canonical Ubuntu Linux, published on 1 Jun 2017. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2017-8386 in the wild and no public exploit code.

Affected product: Canonical Ubuntu Linux. 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-2017-8386/ (Markdown: https://insights.sbomify.com/CVE-2017-8386/index.md)
```

## Sources

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

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