CVE-2011-4868 json
The logging functionality in dhcpd in ISC DHCP before 4.2.3-P2, when using Dynamic DNS (DDNS) and issuing IPv6 addresses, does not properly…
published 2012-01-15 14 y ago modified 2026-06-16 4 mo ago also EUVD-2011-4785
- cvss
- 6.1
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 3.4%
- EPSS 3.4% chance of exploitation in 30 days, percentile 88%
- public exploits
- 0
- none known
Summary
The logging functionality in dhcpd in ISC DHCP before 4.2.3-P2, when using Dynamic DNS (DDNS) and issuing IPv6 addresses, does not properly handle the DHCPv6 lease structure, which allows remote attackers to cause a denial of service (NULL pointer dereference and daemon crash) via crafted packets related to a lease-status update.
Patch / fix
- isc-dhcp Debian 13, Debian 12 4.2.2.dfsg.1-5
debian advisories DEBIAN-CVE-2011-4868
- dhcp openSUSE Tumbleweed 4.3.3.P1-3.1
opensuse advisories openSUSE-SU-2024:10358-1
Vendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2011-4868 updated cvss 5.0
dhcp: error in DDNS processing of DHCPv6 leases can cause ISC dhcpd crash
-
Red Hat Enterprise Linux 4 dhcp Red Hat Enterprise Linux 5 dhcp Red Hat Enterprise Linux 6 dhcp, dhclient, dhcp-commonnot affected: vulnerable code not present
Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf
Exploit prediction
3.41% chance of exploitation in the next 30 days, higher than 88% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 2.0 | 6.1 | AV:A/AC:L/Au:N/C:N/I:N/A:C |
Classification
- Weakness
-
- CWE-399 Resource Management Errors
References
Sources
- CVE List CVE-2011-4868
- NVD CVE-2011-4868
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.