CVE-2019-6474: A packet containing a malformed DUID can cause the kea-dhcp6 server to terminate
Noroxi assessment
Priority: Monitor (action score 26/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.71% (FIRST EPSS); higher than 54.1% of all records.
- Someone on the same network segment can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: kea (Alpine:v3.11) 1.7.2-r0; isc-kea (Debian:12) 1.7.5-1.
Low priority for now. Upgrade to kea (Alpine:v3.11) 1.7.2-r0; isc-kea (Debian:12) 1.7.5-1 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
A missing check on incoming client requests can be exploited to cause a situation where the Kea server's lease storage contains leases which are rejected as invalid when the server tries to load leases from storage on restart. If the number of such leases exceeds a hard-coded limit in the Kea code, a server trying to restart will conclude that there is a problem with its lease store and give up. Versions affected: 1.4.0 to 1.5.0, 1.6.0-beta1, and 1.6.0-beta2
- Published
- Oct 16, 2019
- Updated
- Jun 16, 2026
- EPSS
- 0.7% · 54th percentile
- CWE
- CWE-772
Report tools
Action score
26
Low priority for now.
- CVSS
- 26 / 40 · 6.5 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.7%
CNA vs NVD score
- NVD
- 6.5
- CNA · isc
- 5.7
- 0.8 point gap
CVSS:3.1/AV:A/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| isc | kea | cpe:2.3:a:isc:kea |
Versions reported by the vendor
Affected version ranges reported by the assigning authority (isc). Independent of NVD's CPE analysis and usually ahead of it.
ISC Kea
- 1.4.0 to 1.5.0, 1.6.0-beta1, 1.6.0-beta2affected
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- isc kea1.4.0 and later · up to 1.5.0 inclusive
- isc kea1.6.0
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Alpine:v3.11 | kea | from 1.4.0 · before 1.7.2-r0 | 1.7.2-r0 |
| Debian:12 | isc-kea | before 1.7.5-1 | 1.7.5-1 |
Same product
isc: all recordsOther highest-scoring records for the same primary product.
- CVE-2025-32801Loading a malicious hook library can lead to local privilege escalation31Monitor
- CVE-2018-5739Failure to release memory may exhaust system resources31Monitor
- CVE-2026-3608Stack overflow in Kea daemons30Monitor
Published before and after this one in the same product
- ← EarlierCVE-2015-8373Dec 22, 2015 · The kea-dhcp4 and kea-dhcp6 servers 0.9.2 and 1.0.0-beta in ISC Kea, when certain debugging settings are used, allow remote attackers to…28Monitor
- ← EarlierCVE-2019-6472Oct 16, 2019 · A packet containing a malformed DUID can cause the kea-dhcp6 server to terminate26Monitor
- Later →CVE-2025-32802May 28, 2025 · Insecure handling of file paths allows multiple local attacks24Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| alpine:kea | 1.7.2-r0 · Alpine:v3.17 | Package registry (OSV) |
| debian:isc-kea | 1.7.5-1 · Debian:12 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
Not on record for this CVE: EPSS history · patch commit or PR link · researcher credit · variant or chain candidate · public bounty program.
Technical details
Attack conditions
- Someone on the same network segment can trigger it.
- No account or password is required.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- none
- Integrity
- none
- Availability
- high · the service can be disrupted
- Attack vector
- Adjacent
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- None
- Integrity impact
- None
- Availability impact
- High
Weakness class (CWE)
CWE-772 · Missing Release of Resource after Effective LifetimeCVSS vector
CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
ATT&CK techniques
Change log (1)
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Vendor advisories and official records. Exploit/PoC links are deliberately left out.