CVE-2019-6470: dhcpd: use-after-free error leads crash in IPv6 mode when using mismatched BIND libraries

Published Apr 19, 2018
·
Updated

dhcpd: use-after-free error leads crash in IPv6 mode when using mismatched BIND libraries

Other sources

Double-deletion of the released addresses in the dhcpv6 code leading to crash and possible DoS. This issue was introduced by a commit which fixes a bug in the ISC heap library.

Red Hat

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.

MITRE

Affected Software

72 affected componentsFixes available
redhat/dhcp<4.4.1
4.4.1
ISC BIND>=9.11.2
ISC dhcpd<4.4.1
redhat Enterprise Linux Desktop=7.0
redhat Enterprise Linux Server=7.0
redhat Enterprise Linux Workstation=7.0
openSUSE Leap=15.0
openSUSE Leap=15.1
Microsoft azl3 bind 9.20.5-4<9.16.44-2
9.16.44-2
Microsoft python3-bind-9.19.21-1.azl3.noarch.rpm<9.19.21-1
9.19.21-1
Microsoft cm1 bind 9.16.15-1<9.16.15-1
9.16.15-1
Microsoft azl3 bind 9.16.44-2<9.16.44-2
9.16.44-2
Microsoft bind-utils-9.19.21-1.azl3.aarch64.rpm<9.19.21-1
9.19.21-1
Microsoft cbl2 bind 9.16.15-3<9.16.15-3
9.16.15-3
Microsoft bind-pkcs11-utils-9.16.15-4.cm2.aarch64.rpm<9.16.15-4
9.16.15-4
Microsoft bind-chroot-9.19.21-1.azl3.aarch64.rpm<9.19.21-1
9.19.21-1
Microsoft bind-dnssec-doc-9.19.21-1.azl3.noarch.rpm<9.19.21-1
9.19.21-1
Microsoft bind-dnssec-utils-9.19.21-1.azl3.aarch64.rpm<9.19.21-1
9.19.21-1
Microsoft bind-license-9.19.21-1.azl3.noarch.rpm<9.19.21-1
9.19.21-1
Microsoft bind-devel-9.19.21-1.azl3.aarch64.rpm<9.19.21-1
9.19.21-1
Microsoft bind-libs-9.19.21-1.azl3.aarch64.rpm<9.19.21-1
9.19.21-1
Microsoft bind-dlz-ldap-9.19.21-1.azl3.aarch64.rpm<9.19.21-1
9.19.21-1
Microsoft bind-dnssec-utils-9.19.21-1.azl3.x86_64.rpm<9.19.21-1
9.19.21-1
Microsoft bind-9.19.21-1.azl3.aarch64.rpm<9.19.21-1
9.19.21-1
Microsoft bind-dlz-filesystem-9.19.21-1.azl3.aarch64.rpm<9.19.21-1
9.19.21-1
Microsoft bind-dlz-sqlite3-9.19.21-1.azl3.aarch64.rpm<9.19.21-1
9.19.21-1
Microsoft bind-utils-9.19.21-1.azl3.x86_64.rpm<9.19.21-1
9.19.21-1
Microsoft bind-devel-9.19.21-1.azl3.x86_64.rpm<9.19.21-1
9.19.21-1
Microsoft bind-dlz-mysql-9.19.21-1.azl3.aarch64.rpm<9.19.21-1
9.19.21-1
Microsoft bind-dlz-sqlite3-9.19.21-1.azl3.x86_64.rpm<9.19.21-1
9.19.21-1
Microsoft bind-chroot-9.19.21-1.azl3.x86_64.rpm<9.19.21-1
9.19.21-1
Microsoft bind-dlz-mysql-9.19.21-1.azl3.x86_64.rpm<9.19.21-1
9.19.21-1
Microsoft bind-dlz-ldap-9.19.21-1.azl3.x86_64.rpm<9.19.21-1
9.19.21-1
Microsoft bind-libs-9.19.21-1.azl3.x86_64.rpm<9.19.21-1
9.19.21-1
Microsoft bind-debuginfo-9.16.15-4.cm2.aarch64.rpm<9.16.15-4
9.16.15-4
Microsoft bind-utils-9.16.15-4.cm2.aarch64.rpm<9.16.15-4
9.16.15-4
Microsoft python3-bind-9.16.15-4.cm2.noarch.rpm<9.16.15-4
9.16.15-4
Microsoft bind-dnssec-utils-9.16.15-4.cm2.aarch64.rpm<9.16.15-4
9.16.15-4
Microsoft bind-devel-9.16.15-4.cm2.aarch64.rpm<9.16.15-4
9.16.15-4
Microsoft bind-chroot-9.16.15-4.cm2.aarch64.rpm<9.16.15-4
9.16.15-4
Microsoft bind-9.19.21-1.azl3.x86_64.rpm<9.19.21-1
9.19.21-1
Microsoft bind-dlz-filesystem-9.19.21-1.azl3.x86_64.rpm<9.19.21-1
9.19.21-1
Microsoft bind-dnssec-doc-9.16.15-4.cm2.noarch.rpm<9.16.15-4
9.16.15-4
Microsoft bind-libs-9.16.15-4.cm2.aarch64.rpm<9.16.15-4
9.16.15-4
Microsoft bind-license-9.16.15-4.cm2.noarch.rpm<9.16.15-4
9.16.15-4
Microsoft bind-pkcs11-devel-9.16.15-4.cm2.aarch64.rpm<9.16.15-4
9.16.15-4
Microsoft bind-pkcs11-libs-9.16.15-4.cm2.aarch64.rpm<9.16.15-4
9.16.15-4
Microsoft bind-dlz-ldap-9.16.15-4.cm2.aarch64.rpm<9.16.15-4
9.16.15-4
Microsoft bind-dlz-filesystem-9.16.15-4.cm2.aarch64.rpm<9.16.15-4
9.16.15-4
Microsoft bind-pkcs11-9.16.15-4.cm2.aarch64.rpm<9.16.15-4
9.16.15-4
Microsoft bind-9.16.15-4.cm2.aarch64.rpm<9.16.15-4
9.16.15-4
Microsoft bind-dlz-sqlite3-9.16.15-4.cm2.aarch64.rpm<9.16.15-4
9.16.15-4
Microsoft bind-debuginfo-9.16.15-4.cm2.x86_64.rpm<9.16.15-4
9.16.15-4
Microsoft bind-utils-9.16.15-4.cm2.x86_64.rpm<9.16.15-4
9.16.15-4
Microsoft bind-dlz-mysql-9.16.15-4.cm2.aarch64.rpm<9.16.15-4
9.16.15-4
Microsoft bind-dnssec-utils-9.16.15-4.cm2.x86_64.rpm<9.16.15-4
9.16.15-4
Microsoft bind-pkcs11-devel-9.16.15-4.cm2.x86_64.rpm<9.16.15-4
9.16.15-4
Microsoft bind-devel-9.16.15-4.cm2.x86_64.rpm<9.16.15-4
9.16.15-4
Microsoft bind-chroot-9.16.15-4.cm2.x86_64.rpm<9.16.15-4
9.16.15-4
Microsoft bind-pkcs11-libs-9.16.15-4.cm2.x86_64.rpm<9.16.15-4
9.16.15-4
Microsoft bind-pkcs11-9.16.15-4.cm2.x86_64.rpm<9.16.15-4
9.16.15-4
Microsoft bind-libs-9.16.15-4.cm2.x86_64.rpm<9.16.15-4
9.16.15-4
Microsoft bind-dlz-sqlite3-9.16.15-4.cm2.x86_64.rpm<9.16.15-4
9.16.15-4
Microsoft bind-pkcs11-utils-9.16.15-4.cm2.x86_64.rpm<9.16.15-4
9.16.15-4
Microsoft bind-dlz-mysql-9.16.15-4.cm2.x86_64.rpm<9.16.15-4
9.16.15-4
Microsoft bind-dlz-ldap-9.16.15-4.cm2.x86_64.rpm<9.16.15-4
9.16.15-4
Microsoft bind-dlz-filesystem-9.16.15-4.cm2.x86_64.rpm<9.16.15-4
9.16.15-4
Microsoft bind-9.16.15-4.cm2.x86_64.rpm<9.16.15-4
9.16.15-4
Microsoft bind-debuginfo-9.16.15-1.cm1.aarch64.rpm<9.16.15-1
9.16.15-1
Microsoft bind-debuginfo-9.16.15-1.cm1.x86_64.rpm<9.16.15-1
9.16.15-1
Microsoft bind-utils-9.16.15-1.cm1.aarch64.rpm<9.16.15-1
9.16.15-1
Microsoft bind-utils-9.16.15-1.cm1.x86_64.rpm<9.16.15-1
9.16.15-1

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade redhat/dhcp to a version that resolves this vulnerability.

    Fixed in 4.4.1
  2. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 9.16.44-2
  3. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 9.16.15-1
  4. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 9.19.21-1
  5. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 9.16.15-4
  6. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 9.16.15-3
  7. Upgrade

    Upgrade dhcpd to a version that resolves this vulnerability.

    Fixed in 4.4.1

Event History

Apr 19, 2018
Data Sourced
via Debian·07:21 PM
SeverityAffected Software
Nov 1, 2019
CVE Published
via MITRE·10:15 PM
Data Sourced
via MITRE·10:15 PM
DescriptionSeverityWeakness
Sep 25, 2020
Data Sourced
via Microsoft·12:00 AM
DescriptionSeverityWeaknessAffected Software
Updated
via Microsoft·12:00 AM
Affected Software
Updated
via Microsoft·07:00 AM
SeverityAffected Software
Updated
via Microsoft·07:00 AM
DescriptionSeverityWeakness
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is CVE-2019-6470?

CVE-2019-6470 is a vulnerability in ISC BIND libraries that affects the dhcpd when operating in DHCPv6 mode.

2

What is the severity of CVE-2019-6470?

CVE-2019-6470 has a severity rating of 7.5 (high).

3

Which software is affected by CVE-2019-6470?

CVE-2019-6470 affects the ISC BIND, DHCPD, Redhat Enterprise Linux Desktop, Redhat Enterprise Linux Server, and openSUSE Leap.

4

How can I fix CVE-2019-6470?

To fix CVE-2019-6470, update your DHCP software to version 4.4.1 or apply the necessary patches provided by your vendor.

5

Where can I find more information about CVE-2019-6470?

You can find more information about CVE-2019-6470 at the ISC DHCP website, Debian Bug Tracker, and Red Hat Bugzilla.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203