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

> Attackers can execute arbitrary code as root via unsanitized input in license validation, affecting ASUSTOR NAS devices.

- **Severity:** High 8.1 (`CVSS:3.1/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:** No
- **Published:** 18 Mar 2020
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-mx8j-6j93-6rw8

## What is CVE-2019-11689?

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

### Official description

An issue was discovered in ASUSTOR exFAT Driver through 1.0.0.r20. When conducting license validation, exfat.cgi and exfatctl fail to properly validate server responses and pass unsanitized text to the system shell, resulting in code execution as root.

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

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

It affects 1 product.


Products: Asustor Exfat Driver.

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

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

## Is CVE-2019-11689 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2019-11688](https://insights.sbomify.com/CVE-2019-11688/): Security feature bypass in n/a (high 7.4)

## Fix prompt for AI coding agents

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

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

## Sources

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

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