# CVE-2019-6014: Command injection in DBA-1510P

> Attackers can execute arbitrary OS commands via the Web User Interface of the D-Link DBA-1510P device.

- **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:** 26 Dec 2019
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-jmjg-73wq-w8m5

## What is CVE-2019-6014?

CVE-2019-6014 is a high-severity command injection vulnerability in D-Link Japan K.K. DBA-1510P, published on 26 Dec 2019. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

DBA-1510P firmware 1.70b009 and earlier allows an attacker to execute arbitrary OS commands via Web User Interface.

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

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

It affects 1 product.


Products: Dlink Dba-1510p Firmware.

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

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

## Is CVE-2019-6014 being exploited?

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

## Other vulnerabilities in D-Link Japan K.K. DBA-1510P

- [CVE-2019-6013](https://insights.sbomify.com/CVE-2019-6013/): Command injection in DBA-1510P (medium 6.6)

## Fix prompt for AI coding agents

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

What it is: CVE-2019-6014 is a high-severity command injection vulnerability in D-Link Japan K.K. DBA-1510P, published on 26 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-6014 in the wild and no public exploit code.

Affected product: D-Link Japan K.K. DBA-1510P. 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-6014/ (Markdown: https://insights.sbomify.com/CVE-2019-6014/index.md)
```

## Sources

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

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