# CVE-2019-17270: Command injection in n/a

> Unauthenticated attackers can execute arbitrary OS commands via the systemcall.php endpoint, leading to full system compromise.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/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:** No
- **Published:** 10 Dec 2019
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-g83g-x6pg-6c84

## What is CVE-2019-17270?

CVE-2019-17270 is a critical command injection vulnerability in n/a, published on 10 Dec 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Yachtcontrol through 2019-10-06: It's possible to perform direct Operating System commands as an unauthenticated user via the "/pages/systemcall.php?command={COMMAND}" page and parameter, where {COMMAND} will be executed and returning the results to the client. Affects Yachtcontrol webservers disclosed via Dutch GPRS/4G mobile IP-ranges. IP addresses vary due to DHCP client leasing of telco's.

Weakness: CWE-78 (Improper Neutralization of Special Elements used in an OS Command)

## Which versions are affected by CVE-2019-17270?

It affects 1 product.


Products: Yachtcontrol Yachtcontrol.

## How do I fix CVE-2019-17270?

No fix has been published for CVE-2019-17270 yet. Limit exposure of the affected software until one is available.

## Is CVE-2019-17270 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2019-17270 exists.

Public exploit code:

- Yachtcontrol Webapplication 1.0 - Remote Command Injection (nuclei): http/cves/2019/CVE-2019-17270.yaml

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2019-17270 and fix it if it is affected.

What it is: CVE-2019-17270 is a critical command injection vulnerability in n/a, published on 10 Dec 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2019-17270 exists.

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

## Sources

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

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