# CVE-2019-10999: Memory corruption in n/a

> A stack-based buffer overflow in D-Link Wi-Fi cameras allows authenticated attackers to execute arbitrary code via a long parameter in the web server.

- **Severity:** High 8.8 (`CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 6 May 2019
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-fc75-7wcg-rxg8

## What is CVE-2019-10999?

CVE-2019-10999 is a high-severity memory corruption vulnerability in n/a, published on 6 May 2019. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

The D-Link DCS series of Wi-Fi cameras contains a stack-based buffer overflow in alphapd, the camera's web server. The overflow allows a remotely authenticated attacker to execute arbitrary code by providing a long string in the WEPEncryption parameter when requesting wireless.htm. Vulnerable devices include DCS-5009L (1.08.11 and below), DCS-5010L (1.14.09 and below), DCS-5020L (1.15.12 and below), DCS-5025L (1.03.07 and below), DCS-5030L (1.04.10 and below), DCS-930L (2.16.01 and below), DCS-931L (1.14.11 and below), DCS-932L (2.17.01 and below), DCS-933L (1.14.11 and below), and DCS-934L (1.05.04 and below).

Weakness: CWE-787 (Out-of-bounds Write)

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

It affects 10 products.


Products: Dlink Dcs-5009l Firmware, Dlink Dcs-5010l Firmware, Dlink Dcs-5020l Firmware, Dlink Dcs-5025l Firmware, Dlink Dcs-5030l Firmware, Dlink Dcs-930l Firmware, Dlink Dcs-931l Firmware, Dlink Dcs-932l Firmware, Dlink Dcs-933l Firmware, Dlink Dcs-934l Firmware.

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

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

## Is CVE-2019-10999 being exploited?

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

Public exploit code:

- Full exploit for D-Link DCS-5020L, POC crash for others that are vulnerable as well.  (github_poc): https://github.com/tacnetsol/CVE-2019-10999
- https://github.com/qjh2333/CVE-2019-10999 (github_poc): https://github.com/qjh2333/CVE-2019-10999

## Fix prompt for AI coding agents

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

What it is: CVE-2019-10999 is a high-severity memory corruption vulnerability in n/a, published on 6 May 2019. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2019-10999 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-10999/ (Markdown: https://insights.sbomify.com/CVE-2019-10999/index.md)
```

## Sources

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

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