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.
This vulnerability carries a HIGH severity rating with a CVSS v3.1 score of 7.4, indicating it requires adjacent network access with relatively low complexity without requiring user interaction and does not require pre-existing privileges . The vulnerability impacts and availability (service disruption) for affected systems. Impacting 26 products from isc, from fedoraproject, from debian and 23 others, organizations running these solutions should prioritize assessment and patching.
Reported in 2021, this vulnerability emerged during an era marked by increased sophistication in supply chain attacks, cloud infrastructure vulnerabilities, and software-as-a-service (SaaS) security challenges. Security practices during this period emphasized zero-trust architectures, container security, and API protection.
2021-05-26T22:15:07.947
2024-11-21T05:54:34.013
Modified
CVSSv3.1: 7.4 (HIGH)
AV:A/AC:L/Au:N/C:N/I:N/A:P
6.5
2.9
| Type | Vendor | Product | Version/Range | Vulnerable? |
|---|---|---|---|---|
| Application | isc | dhcp | ≤ 4.4.2 | Yes |
| Application | isc | dhcp | 4.1-esv | Yes |
| Application | isc | dhcp | 4.1-esv | Yes |
| Application | isc | dhcp | 4.1-esv | Yes |
| Application | isc | dhcp | 4.1-esv | Yes |
| Application | isc | dhcp | 4.1-esv | Yes |
| Application | isc | dhcp | 4.1-esv | Yes |
| Application | isc | dhcp | 4.1-esv | Yes |
| Application | isc | dhcp | 4.1-esv | Yes |
| Application | isc | dhcp | 4.1-esv | Yes |
| Application | isc | dhcp | 4.1-esv | Yes |
| Application | isc | dhcp | 4.1-esv | Yes |
| Application | isc | dhcp | 4.1-esv | Yes |
| Application | isc | dhcp | 4.1-esv | Yes |
| Application | isc | dhcp | 4.1-esv | Yes |
| Application | isc | dhcp | 4.1-esv | Yes |
| Application | isc | dhcp | 4.1-esv | Yes |
| Application | isc | dhcp | 4.1-esv | Yes |
| Application | isc | dhcp | 4.1-esv | Yes |
| Application | isc | dhcp | 4.1-esv | Yes |
| Application | isc | dhcp | 4.1-esv | Yes |
| Application | isc | dhcp | 4.1-esv | Yes |
| Application | isc | dhcp | 4.1-esv | Yes |
| Application | isc | dhcp | 4.1-esv | Yes |
| Application | isc | dhcp | 4.1-esv | Yes |
| Application | isc | dhcp | 4.1-esv | Yes |
| Application | isc | dhcp | 4.1-esv | Yes |
| Application | isc | dhcp | 4.1-esv | Yes |
| Application | isc | dhcp | 4.1-esv | Yes |
| Operating System | fedoraproject | fedora | 33 | Yes |
| Operating System | fedoraproject | fedora | 34 | Yes |
| Operating System | debian | debian_linux | 9.0 | Yes |
| Operating System | siemens | ruggedcom_rox_rx1400_firmware | < 2.15.0 | Yes |
| Hardware | siemens | ruggedcom_rox_rx1400 | - | No |
| Operating System | siemens | ruggedcom_rox_rx1500_firmware | < 2.15.0 | Yes |
| Hardware | siemens | ruggedcom_rox_rx1500 | - | No |
| Operating System | siemens | ruggedcom_rox_rx1501_firmware | < 2.15.0 | Yes |
| Hardware | siemens | ruggedcom_rox_rx1501 | - | No |
| Operating System | siemens | ruggedcom_rox_rx1510_firmware | < 2.15.0 | Yes |
| Hardware | siemens | ruggedcom_rox_rx1510 | - | No |
| Operating System | siemens | ruggedcom_rox_rx1511_firmware | < 2.15.0 | Yes |
| Hardware | siemens | ruggedcom_rox_rx1511 | - | No |
| Operating System | siemens | ruggedcom_rox_rx1512_firmware | < 2.15.0 | Yes |
| Hardware | siemens | ruggedcom_rox_rx1512 | - | No |
| Operating System | siemens | ruggedcom_rox_rx1524_firmware | < 2.15.0 | Yes |
| Hardware | siemens | ruggedcom_rox_rx1524 | - | No |
| Operating System | siemens | ruggedcom_rox_rx1536_firmware | < 2.15.0 | Yes |
| Hardware | siemens | ruggedcom_rox_rx1536 | - | No |
| Operating System | siemens | ruggedcom_rox_rx5000_firmware | < 2.15.0 | Yes |
| Hardware | siemens | ruggedcom_rox_rx5000 | - | No |
| Operating System | siemens | ruggedcom_rox_mx5000_firmware | < 2.15.0 | Yes |
| Hardware | siemens | ruggedcom_rox_mx5000 | - | No |
| Application | netapp | ontap_select_deploy_administration_utility | - | Yes |
| Application | netapp | solidfire_\&_hci_management_node | - | Yes |
| Application | siemens | sinec_ins | < 1.0 | Yes |
| Application | siemens | sinec_ins | 1.0 | Yes |
| Application | siemens | sinec_ins | 1.0 | Yes |
SecUtils normalizes and enriches National Vulnerability Database (NVD) records by standardizing vendor and product identifiers, aggregating vulnerability metadata from both NVD and MITRE sources, and providing structured context for security teams. For isc's affected products, we extract Common Platform Enumeration (CPE) data, Common Weakness Enumeration (CWE) classifications, CVSS severity metrics, and reference data to enable rapid vulnerability prioritization and asset correlation. This record contains no exploit code, proof-of-concept instructions, or attack methodologies—only defensive intelligence necessary for patch management, risk assessment, and security operations.