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

> Attackers can execute arbitrary code via unsanitized URLs in myrepos webcheckout, affecting developers using this version control tool.

- **Severity:** High 7.5 (`CVSS:3.0/AV:N/AC:H/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:** 14 Feb 2018
- **Updated:** 16 Sep 2024
- **Also known as:** ALPINE-CVE-2018-7032, DEBIAN-CVE-2018-7032, GHSA-cxq4-c3j7-c5jv, UBUNTU-CVE-2018-7032, openSUSE-SU-2024:11063-1

## What is CVE-2018-7032?

CVE-2018-7032 is a high-severity command injection vulnerability in n/a, published on 14 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

webcheckout in myrepos through 1.20171231 does not sanitize URLs that are passed to git clone, allowing a malicious website operator or a MitM attacker to take advantage of it for arbitrary code execution, as demonstrated by an "ext::sh -c" attack or an option injection attack.

Weakness: CWE-74 (Improper Neutralization of Special Elements in Output Used by a Downstream Component)

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

It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `mr` | openSUSE:Tumbleweed | All versions | 1.20180726-1.5 |

Products: Myrepos Project Myrepos.

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

Upgrade to a fixed version.

## Is CVE-2018-7032 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2018-7032 is a high-severity command injection vulnerability in n/a, published on 14 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-7032 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-7032/ (Markdown: https://insights.sbomify.com/CVE-2018-7032/index.md)
```

## Sources

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

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