Skip to main content
Mallory
HighPublic exploitVulnerability

CVE-2019-10999: Stack-based Buffer Overflow in D-Link DCS Series Wi-Fi Cameras (alphapd)

Published May 6, 2019 · Updated 1 month ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 daysNo mention activity in the last 30 days.
CVSS8.8High · v3
EPSS3.6%90th percentile
CISA KEVNoNot listed
In the wildNonePublic exploit, no exploitation reported
Vendor
D-Link
IdentifiersCVE-2019-10999CWE-121

A stack-based buffer overflow exists in the alphapd web server component of multiple D-Link DCS series Wi-Fi cameras. The vulnerability is triggered when a remote, authenticated attacker sends an overly long string in the WEPEncryption parameter to the wireless.htm endpoint. This allows for overwriting of stack memory, potentially leading to arbitrary code execution. Affected models 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).

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

Impact, mitigation & remediation

What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation allows a remote, authenticated attacker to execute arbitrary code on the device, potentially gaining full control of the camera, accessing video streams, or pivoting to other devices on the network. This can lead to compromise of privacy, surveillance, and further network intrusion.

Mitigation

If you can’t patch tonight, do this now.

Restrict access to the camera's web interface to trusted networks only. Use strong, unique passwords for device authentication. Where possible, disable remote access and monitor device logs for suspicious activity until firmware can be updated.

Remediation

Patch, then assume compromise.

Upgrade the firmware of affected D-Link DCS camera models to a version above those listed as vulnerable. D-Link has released patched firmware versions for these models. Ensure all devices are running the latest available firmware.

Exposure surface

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
D-LinkDcs-5009l Firmwareoperating_system
D-LinkDcs-5010l Firmwareoperating_system
D-LinkDcs-5020l Firmwareoperating_system
D-LinkDcs-5025l Firmwareoperating_system
D-LinkDcs-5030l Firmwareoperating_system
D-LinkDcs-930l Firmwareoperating_system
D-LinkDcs-931l Firmwareoperating_system
D-LinkDcs-932l Firmwareoperating_system
D-LinkDcs-933l Firmwareoperating_system
D-LinkDcs-934l Firmwareoperating_system
FAQ

Frequently asked questions

Is CVE-2019-10999 exploited in the wild?
As of Oct 16, 2026, Mallory has no reports of CVE-2019-10999 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2019-10999?
Yes. Mallory tracks 1 public exploit or proof of concept for CVE-2019-10999, the earliest disclosed Jan 23, 2019.
Is there a patch for CVE-2019-10999?
Upgrade the firmware of affected D-Link DCS camera models to a version above those listed as vulnerable. D-Link has released patched firmware versions for these models.
What products are affected by CVE-2019-10999?
D-Link Dcs-5009l Firmware, D-Link Dcs-5010l Firmware, D-Link Dcs-5020l Firmware, D-Link Dcs-5025l Firmware, D-Link Dcs-5030l Firmware, and 5 more.
How severe is CVE-2019-10999?
CVE-2019-10999 has a CVSS v3 score of 8.8 (High) and an EPSS score of 3.6% (90th percentile) as of Oct 16, 2026.
Activity feed

Recent activity

No public activity tracked yet. Mallory keeps watching.

View more in app →

No public activity observed for this vulnerability.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidenceEvery report linking this CVE to a named adversary.
Associated malwareMalware families linked to this CVE, with evidence and IOCs.
Detection signaturesYARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activityCommunity discussion across Reddit, Mastodon, and other social sources.