kea vulnerabilities and fixes
Recent CVEs affecting kea, with upgrade or downgrade steps. 4 tracked.
kea has 4 tracked vulnerabilities, 0 critical. A fixed release or vendor patch exists for 3. Most recent: 2019-10-16. Highest priority: CVE-2018-5739 (score 43/100).
- CVE-2019-6474 MEDIUM 5.7 UPGRADE A missing check on incoming client requests can be exploited to cause a situation where the Kea server's lease
- CVE-2019-6473 MEDIUM 6.5 UPGRADE An invalid hostname option can trigger an assertion failure in the Kea DHCPv4 server process (kea-dhcp4), caus
- CVE-2019-6472 MEDIUM 6.5 UPGRADE A packet containing a malformed DUID can cause the Kea DHCPv6 server process (kea-dhcp6) to exit due to an ass
- CVE-2018-5739 MEDIUM 6.5 DOWNGRADE An extension to hooks capabilities which debuted in Kea 1.4.0 introduced a memory leak for operators who are u
FAQ
How do I fix kea vulnerabilities?
Open the CVE for your version, check the affected range, then follow the listed action: upgrade to the fixed release, or downgrade or mitigate if no fix exists yet. Commands for each OS are shown on every CVE page.
Is kea being exploited right now?
None of the tracked kea CVEs are on the CISA Known Exploited Vulnerabilities list at the moment. This is checked every 20 minutes.
Which kea CVE should I patch first?
CVE-2018-5739 currently ranks highest (43/100): An extension to hooks capabilities which debuted in Kea 1.4.0 introduced a memory leak for operators who are u.