# CVE-2017-17831: GitHub Git LFS Arbitrary command execution vulnerability

> Remote attackers can execute arbitrary commands via a malicious .lfsconfig file in Git LFS repositories.

- **Severity:** High 8.8 (`CVSS:3.0/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:** 21 Dec 2017
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-w4xh-w33p-4v29, GO-2021-0073

## What is CVE-2017-17831?

CVE-2017-17831 is a high-severity command injection vulnerability in n/a, published on 21 Dec 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

GitHub Git LFS before 2.1.1 allows remote attackers to execute arbitrary commands via an ssh URL with an initial dash character in the hostname, located on a "url =" line in a .lfsconfig file within a repository.

Weakness: CWE-20 (Improper Input Validation)

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

3 open source packages ship an affected version, including github.com/git-lfs/git-lfs. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `github.com/git-lfs/git-lfs` | Go | All versions | 2.1.1-0.20170519163204-f913f5f9c7c6 |
| `github.com/git-lfs/git-lfs` | Go | All versions | 2.1.1-0.20170519163204-f913f5f9c7c6 |
| `github.com/git-lfs/git-lfs` | Go | All versions | 2.1.1-0.20170519163204-f913f5f9c7c6+incompatible |

Products: Git Large File Storage Project Git Large File Storage.

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

Upgrade github.com/git-lfs/git-lfs to a fixed version for your release line: 2.1.1-0.20170519163204-f913f5f9c7c6 or 2.1.1-0.20170519163204-f913f5f9c7c6+incompatible.

## Is CVE-2017-17831 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2022-24826](https://insights.sbomify.com/CVE-2022-24826/): Git LFS can execute a binary from the current directory on Windows (critical 9.8)
- [CVE-2020-27955](https://insights.sbomify.com/CVE-2020-27955/): Git LFS can execute a Git binary from the current directory (critical 9.8)
- [CVE-2021-21237](https://insights.sbomify.com/CVE-2021-21237/): Git LFS can execute a Git binary from the current directory on Windows (high 7.2)

## Fix prompt for AI coding agents

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

What it is: CVE-2017-17831 is a high-severity command injection vulnerability in n/a, published on 21 Dec 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-2017-17831 in the wild and no public exploit code.

Affected packages and fixed versions:
- github.com/git-lfs/git-lfs (Go): affected all versions; fixed in 2.1.1-0.20170519163204-f913f5f9c7c6
- github.com/git-lfs/git-lfs (Go): affected all versions; fixed in 2.1.1-0.20170519163204-f913f5f9c7c6
- github.com/git-lfs/git-lfs (Go): affected all versions; fixed in 2.1.1-0.20170519163204-f913f5f9c7c6+incompatible

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-17831/ (Markdown: https://insights.sbomify.com/CVE-2017-17831/index.md)
```

## Sources

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

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