Homepage

Out-of-Bounds Affecting dhclient package, versions <12:4.2.5-83.el7_9.1

Severity

 Recommended
0.0
high
0
10

Based on CentOS security rating.

Threat Intelligence

EPSS
0.28% (69th percentile)

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 IDSNYK-CENTOS7-DHCLIENT-2184519
  • published26 Jul 2021
  • disclosed26 May 2021
Report a new vulnerability Found a mistake?

Introduced: 26 May 2021

CVE-2021-25217  (opens in a new tab)
CWE-119  (opens in a new tab)

How to fix?

Upgrade Centos:7 dhclient to version 12:4.2.5-83.el7_9.1 or higher.

NVD Description

Note: Versions mentioned in the description apply only to the upstream dhclient package and not the dhclient package as distributed by Centos. See How to fix? for Centos:7 relevant fixed versions and status.

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.

References

CVSS Scores

version 3.1