Homepage
About Snyk

CVE-2019-6470 Affecting isc-dhcp package, versions *

0.0
high

Snyk CVSS

    Attack Complexity Low
    Availability High

    Threat Intelligence

    EPSS 0.16% (53rd percentile)
Expand this section
NVD
7.5 high
Expand this section
SUSE
7.5 high
Expand this section
Red Hat
5.9 medium

Do your applications use this vulnerable package?

In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.

Test your applications
  • Snyk ID SNYK-DEBIAN8-ISCDHCP-345977
  • published 7 May 2019
  • disclosed 1 Nov 2019
Report a new vulnerability Found a mistake?

Introduced: 7 May 2019

CVE-2019-6470 Open this link in a new tab

How to fix?

There is no fixed version for Debian:8 isc-dhcp.

NVD Description

Note: Versions mentioned in the description apply only to the upstream isc-dhcp package and not the isc-dhcp package as distributed by Debian. See How to fix? for Debian:8 relevant fixed versions and status.

There had existed in one of the ISC BIND libraries a bug in a function that was used by dhcpd when operating in DHCPv6 mode. There was also a bug in dhcpd relating to the use of this function per its documentation, but the bug in the library function prevented this from causing any harm. All releases of dhcpd from ISC contain copies of this, and other, BIND libraries in combinations that have been tested prior to release and are known to not present issues like this. Some third-party packagers of ISC software have modified the dhcpd source, BIND source, or version matchup in ways that create the crash potential. Based on reports available to ISC, the crash probability is large and no analysis has been done on how, or even if, the probability can be manipulated by an attacker. Affects: Builds of dhcpd versions prior to version 4.4.1 when using BIND versions 9.11.2 or later, or BIND versions with specific bug fixes backported to them. ISC does not have access to comprehensive version lists for all repackagings of dhcpd that are vulnerable. In particular, builds from other vendors may also be affected. Operators are advised to consult their vendor documentation.