Skip to content
Fencer Intel
medium 6.5

CVE-2019-6472 json

A packet containing a malformed DUID can cause the kea-dhcp6 server to terminate

published 7y ago modified 4mo ago also EUVD-2019-16032

cvss
6.5
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.8%
EPSS 0.8% chance of exploitation in 30 days, percentile 56%
public exploits
0
none known

Summary

A packet containing a malformed DUID can cause the Kea DHCPv6 server process (kea-dhcp6) to exit due to an assertion failure. Versions affected: 1.4.0 to 1.5.0, 1.6.0-beta1, and 1.6.0-beta2.

Patch / fix

  • isc-kea Debian 14, Debian 13, Debian 12 1.7.5-1

debian advisories DEBIAN-CVE-2019-6472

  • kea Alpine 3.24, Alpine 3.23, Alpine 3.22 +11 more 1.7.2-r0

alpine advisories ALPINE-CVE-2019-6472

Alpine secdb © Alpine Linux, from https://secdb.alpinelinux.org via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0

  • kea Arch Linux 1.8.0-1

arch linux advisories AVG-1032

Is CVE-2019-6472 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

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-2019-6472 updated cvss 6.5

kea: packet containing a malformed DUID

  • Red Hat All currently supported Red Hat products
    not 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

0.80% chance of exploitation in the next 30 days, higher than 56% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
CNA 3.1 6.5 CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
NVD 3.1 6.5 CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
NVD 2.0 3.3 AV:A/AC:L/Au:N/C:N/I:N/A:P

Affected products

  • ISC Kea

Classification

Weakness

References

Sources

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.