Vulnerabilities · 2021 · Isc
CVE-2021-25217
Isc Dhcp vulnerability
In ISC DHCP 4.1-ESV-R1 -> 4.1-ESV-R16, ISC DHCP 4.4.0 -> 4.4.2 (Other branches of ISC DHCP (i.e., releases in the 4.0.x series or lower and releases in the 4.3.x series) are beyond their End-of-Life (EOL) and no longer supported by ISC. From inspection it is clear that the defect is also present in releases from those series, but they have not been officially tested for the vulnerability), The outcome of encountering the defect while reading a lease that will trigger it varies, according to: the component being affected (i.e., dhclient or dhcpd) whether the package was built as a 32-bit or 64-bit binary whether the compiler flag -fstack-protection-strong was used when compiling In dhclient, ISC has not successfully reproduced the error on a 64-bit system. However, on a 32-bit system it is possible to cause dhclient to crash when reading an improper lease, which could cause network connectivity problems for an affected system due to the absence of a running DHCP client process. In dhcpd, when run in DHCPv4 or DHCPv6 mode: if the dhcpd server binary was built for a 32-bit architecture AND the -fstack-protection-strong flag was specified to the compiler, dhcpd may exit while parsing a lease file containing an objectionable lease, resulting in lack of service to clients. Additionally, the offending lease and the lease immediately following it in the lease database may be improperly deleted. if the dhcpd server binary was built for a 64-bit architecture OR if the -fstack-protection-strong compiler flag was NOT specified, the crash will not occur, but it is possible for the offending lease and the lease which immediately followed it to be improperly deleted.
Affected products
Dhcp, Fedora, Debian Linux, Ruggedcom Rox Rx1400 Firmware, Ruggedcom Rox Rx1500 Firmware, Ruggedcom Rox Rx1501 Firmware, Ruggedcom Rox Rx1510 Firmware, Ruggedcom Rox Rx1511 Firmware, Ruggedcom Rox Rx1512 Firmware, Ruggedcom Rox Rx1524 Firmware and more. The exact versions are in the references.
What to do now
- Check your exposureFind out whether Isc Dhcp runs anywhere in your environment, including systems of suppliers.
- UpdateInstall the version in which the vendor fixed the vulnerability. The references lead to the advisory.
- Set the orderSystems that can be reached from the internet come first, then the rest.
References
- kb.isc.org/docs/cve-2021-25217 · Exploit
- www.openwall.com/lists/oss-security/2021/05/26/6 · Patch
- cert-portal.siemens.com/productcert/pdf/ssa-406691.pdf · Patch
- cert-portal.siemens.com/productcert/pdf/ssa-637483.pdf · Patch
- lists.debian.org/debian-lts-announce/2021/06/msg00002.html · Third Party Advisory
- security.netapp.com/advisory/ntap-20220325-0011/ · Third Party Advisory
- lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/5
- lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/Z
- nvd.nist.gov/vuln/detail/CVE-2021-25217
- cve.org/CVERecord?id=CVE-2021-25217
More vulnerabilities in Isc products
Data: CVE list and the NVD. This product uses data from the NVD API but is not endorsed or certified by the NVD.