Skip to main content
Mallory
CriticalPublic exploitVulnerability

CVE-2019-11766: Buffer Over-read in dhcpcd D6_OPTION_PD_EXCLUDE

Published May 5, 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.
CVSS9.8Critical · v3.1
EPSS2.0%82nd percentile
CISA KEVNoNot listed
In the wildNonePublic exploit, no exploitation reported
Vendors
Debian ProjectDhcpcd Project
IdentifiersCVE-2019-11766CWE-126

A buffer over-read vulnerability exists in dhcpcd (Dynamic Host Configuration Protocol client daemon) in the dhcp6.c file, affecting versions before 6.11.7 and 7.x before 7.2.2. The issue is present in the handling of the D6_OPTION_PD_EXCLUDE feature, where improper bounds checking can lead to reading beyond the allocated buffer.

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.

An attacker could exploit this vulnerability to read sensitive information from adjacent memory, potentially leading to information disclosure. The impact is limited to the context in which dhcpcd is running, but could expose configuration or other sensitive data processed by the daemon.

Mitigation

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

If immediate upgrade is not possible, disable the D6_OPTION_PD_EXCLUDE feature if not required, and restrict untrusted DHCPv6 traffic to the affected system to reduce exposure.

Remediation

Patch, then assume compromise.

Upgrade dhcpcd to version 6.11.7, 7.2.2, or later, where the buffer over-read issue in the D6_OPTION_PD_EXCLUDE feature has been fixed.

Public exploits

Exploits

1 exploit validated by Mallory's analysis.

View more in app →
echo-dot-3-doebrite-researchThis is a standalone security-research collection, not a framework module. The inventory contains 90 files: 67 Python scripts, two Bash scripts, 18 Markdown documents, a public setup certificate, LICENSE, and .gitignore. README.md introduces the assessment; disclosure/ contains the vendor report; docs/ contains ten topical chapters; evidence/ contains six technical research records. scripts/analysis/ provides LAN scanning, SOCKS probing/fuzzing, Spotify handshake experiments, and availability monitoring. scripts/ble/ contains iterative WhisperJoin clients alongside HTTP/OOBE fuzzers, including the main exploit in deep2.py. scripts/oobe/ contains provisioning clients, a mock server, static-image inspection, and field/race tests. scripts/pi/ supplies malicious DHCP/DNS/NTP servers, IPv6 RA and discovery fuzzers, OTA impersonation tests, and a transparent traffic relay. Several OOBE scripts are duplicated across directories. The strongest supported exploit is the CVE-2019-0205-style Thrift recursion DoS. deep2.py sends valid nested Thrift-JSON records to the unauthenticated setup endpoint and increases their depth. The repository reports that depth 20,000, producing 280,017 bytes, terminates oobed while leaving the Wi-Fi AP running. The documented oneshot service configuration prevents automatic restart, so the provisioning outage persists until recovery, normally a power cycle. This is stack exhaustion, not demonstrated instruction-pointer control. Despite README statements that no exploit code is published, this script contains an actual crash-triggering payload. Additional documented findings are restricted getLinkCode SSRF/loopback reachability, unauthenticated Spotify owner-display-name disclosure, and two latent hardening concerns involving a root SOCKS service and unquoted firewall variables. The SOCKS tools do not demonstrate a bypass: CONNECT requests reportedly receive nonstandard refusal code 0x09. The firewall pattern is explicitly described as not currently exploitable through the observed remote-address input. Spotify getInfo exposes identity metadata and a public key, not demonstrated private/session-secret disclosure. The addUser experiment does not establish successful login, memory corruption, or code execution. The other listed CVEs are experimental targets, not confirmed Echo vulnerabilities: the DHCPv6 harness attempts CVE-2019-11577 and CVE-2019-11766 patterns, while the dnsmasq harness explores CVE-2015-3294-related behavior. Historical evidence contains corrected product/version assumptions and failed harnesses. BLE tools implement discovery, protobuf/zigzag encoding, provisioning startup, command framing, and chunked responses; the reported cloud authentication barrier remains intact. OTA and NTP tools test trust and time handling but demonstrate no unsigned installation. tap.py forwards encrypted TLS unchanged and records observable metadata rather than decrypting it. Operational quality is uneven. Earlier wjcmd clients access UUID attributes unavailable in Python's standard uuid.UUID, while later clients use integer conversion. Both oobe_race.py copies pass an unsupported timeout keyword to race_pair and therefore stop before subsequent tests. Several experiments use incorrect or historical argument layouts. TCP-connect-only liveness checks cannot independently establish a healthy RPC service, and no tests were executed for this analysis. Portions of the supplied files are truncated, some referenced artifacts are absent, and bootloader evidence includes an Octave-derived image despite the final Doebrite focus. Accordingly, the repository's absolute claim that over-the-air firmware replacement is impossible exceeds what these materials independently prove; the supported result is that no such path was demonstrated. Repository URL, git reference, and archive size were not supplied; empty strings and zero represent unavailable metadata.cgarrot · Disclosed Oct 22, 2026 · python · bash · network · wireless · bluetoothOperational
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
Debian ProjectDebian Linuxoperating_system
Dhcpcd ProjectDhcpcdapplication
FAQ

Frequently asked questions

Is CVE-2019-11766 exploited in the wild?
As of Oct 16, 2026, Mallory has no reports of CVE-2019-11766 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2019-11766?
Yes. Mallory tracks 1 public exploit or proof of concept for CVE-2019-11766, the earliest disclosed Oct 22, 2026.
Is there a patch for CVE-2019-11766?
Upgrade dhcpcd to version 6.11.7, 7.2.2, or later, where the buffer over-read issue in the D6_OPTION_PD_EXCLUDE feature has been fixed.
What products are affected by CVE-2019-11766?
Dhcpcd Project Dhcpcd and Debian Project Debian Linux.
How severe is CVE-2019-11766?
CVE-2019-11766 has a CVSS v3.1 score of 9.8 (Critical) and an EPSS score of 2.0% (82nd 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.