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

> Remote attackers can execute arbitrary code as root on D-Link DAP-1860 devices by injecting shell metacharacters into the HNAP_AUTH header without authentication.

- **Severity:** High 8.8 (`CVSS:3.1/AV:A/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:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 5 Dec 2019
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-3vwg-cxp6-wf3x

## What is CVE-2019-19597?

CVE-2019-19597 is a high-severity command injection vulnerability in n/a, published on 5 Dec 2019. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

D-Link DAP-1860 devices before v1.04b03 Beta allow arbitrary remote code execution as root without authentication via shell metacharacters within an HNAP_AUTH HTTP header.

Weakness: CWE-863 (Incorrect Authorization)

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

It affects 1 product.


Products: Dlink Dap-1860 Firmware.

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

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

## Is CVE-2019-19597 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2023-45208](https://insights.sbomify.com/CVE-2023-45208/): Command injection in n/a (high 8.8)
- [CVE-2020-27864](https://insights.sbomify.com/CVE-2020-27864/): Command injection in DAP-1860 (high 8.8)
- [CVE-2020-27865](https://insights.sbomify.com/CVE-2020-27865/): Auth bypass in DAP-1860 (high 8.8)
- [CVE-2019-19598](https://insights.sbomify.com/CVE-2019-19598/): Auth bypass in n/a (high 8.8)
- [CVE-2020-15631](https://insights.sbomify.com/CVE-2020-15631/): Command injection in DAP-1860 (high 8.0)

## Fix prompt for AI coding agents

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

What it is: CVE-2019-19597 is a high-severity command injection vulnerability in n/a, published on 5 Dec 2019. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2019-19597 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-19597/ (Markdown: https://insights.sbomify.com/CVE-2019-19597/index.md)
```

## Sources

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

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