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

> Attackers can execute arbitrary commands via the rsync module in Gitolite if rsync is enabled in the configuration.

- **Severity:** High 8.1 (`CVSS:3.0/AV:N/AC:H/PR:N/UI:N/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:** Not needed
- **Fix available:** Yes
- **Published:** 10 Jan 2019
- **Updated:** 5 Aug 2024
- **Also known as:** ALPINE-CVE-2018-20683, DEBIAN-CVE-2018-20683, GHSA-rx5g-g97h-39pr, MGASA-2019-0058, UBUNTU-CVE-2018-20683, openSUSE-SU-2019:0054-1

## What is CVE-2018-20683?

CVE-2018-20683 is a high-severity command injection vulnerability in n/a, published on 10 Jan 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

commands/rsync in Gitolite before 3.6.11, if .gitolite.rc enables rsync, mishandles the rsync command line, which allows attackers to have a "bad" impact by triggering use of an option other than -v, -n, -q, or -P.

Weakness: CWE-20 (Improper Input Validation)

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

It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `gitolite` | SUSE:Package Hub 15 | All versions | 3.6.11-bp150.3.6.1 |
| `gitolite` | openSUSE:Leap 15.0 | All versions | 3.6.11-bp150.3.6.1 |

Products: Gitolite Gitolite.

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

Upgrade to a fixed version.

## Is CVE-2018-20683 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2010-2447](https://insights.sbomify.com/CVE-2010-2447/): Path traversal in n/a (critical 9.8)
- [CVE-2013-4451](https://insights.sbomify.com/CVE-2013-4451/): Misconfiguration in n/a (critical 9.8)
- [CVE-2018-16976](https://insights.sbomify.com/CVE-2018-16976/): Race condition in n/a (high 8.1)
- [CVE-2011-1572](https://insights.sbomify.com/CVE-2011-1572/): Path traversal in n/a (medium 6.8)
- [CVE-2013-7203](https://insights.sbomify.com/CVE-2013-7203/): Information disclosure in n/a (medium 5.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2018-20683 is a high-severity command injection vulnerability in n/a, published on 10 Jan 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2018-20683 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-20683/ (Markdown: https://insights.sbomify.com/CVE-2018-20683/index.md)
```

## Sources

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

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