CVE-2021-25217
- Assigned byThe organization (CNA) that assigned this CVE ID and published the record, usually the vendor.
- Internet Systems Consortium (ISC) (opens in new tab)
- Published
- Last modified
- NVD statusWhether NVD has reviewed the record. Until it has, scores and product data come from the reporting organization alone. About NVD's statuses
- Modified
Description
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.
Exploitation
Whether attackers are exploiting this vulnerability, and how likely they are to try in the next 30 days.
FIRST Exploit Prediction Scoring System (EPSS)About EPSS (opens in new tab)
FIRST's estimate of the chance attackers try to exploit this vulnerability in the next 30 days.
- Probability of exploitationIt predicts attempts, not success, and is updated daily.
- 6.118%
- Compared with other CVEs
- At or above 93.603% of scored CVEs
- Scored
Affected products
The products and versions with the vulnerability.
Listed by CNA
The products and versions affected, according to the organization that published this CVE.
| Vendor | Product | Affected versions |
|---|---|---|
| ISC | ISC DHCP |
|
Listed by NVD
The CPE names vulnerability scanners match, including products that bundle the affected software.
| Vendor | Product | Type | Vulnerable versions |
|---|---|---|---|
| debian | debian linux | Operating system |
|
| fedoraproject | fedora | Operating system |
|
| isc | dhcp | Application |
|
| netapp | ontap select deploy administration utility | Application |
|
| netapp | solidfire & hci management node | Application |
|
| siemens | ruggedcom rox mx5000 firmware | Operating system |
|
| siemens | ruggedcom rox rx1400 firmware | Operating system |
|
| siemens | ruggedcom rox rx1500 firmware | Operating system |
|
| siemens | ruggedcom rox rx1501 firmware | Operating system |
|
| siemens | ruggedcom rox rx1510 firmware | Operating system |
|
Recommended actions
How to fix the vulnerability, or reduce the risk until you can.
Solutions
From Internet Systems Consortium (ISC), which published this CVE.
Upgrade to the patched release most closely related to your current version of ISC DHCP:
ISC DHCP 4.1-ESV-R16-P1
ISC DHCP 4.4.2-P1
Workarounds
From Internet Systems Consortium (ISC), which published this CVE.
None known.
Patches, advisories and mitigations
Tagged by NVD.
- Patch
- Third Party Advisory
- Patch
- Third Party Advisory
- Patch
- Third Party Advisory
Severity
How serious the vulnerability is if exploited, scored from 0 to 10 with the CVSS standard (opens in new tab).
- 3.3 LowCVSS 2.0 · PrimaryPrimary scores are NVD's own. Secondary scores come from the organization that published the CVE, or from CISA. · Scored by NVD (opens in new tab)
- Attack vectorWhere the attacker has to be. Network is the widest: anywhere on the Internet.
- Adjacent network
- Attack complexityWhether the attack depends on conditions the attacker doesn't control.
- Low
- AuthenticationHow many times the attacker has to sign in.
- None
- ConfidentialityHow much data the attacker can read.
- None
- IntegrityHow much data the attacker can change.
- None
- AvailabilityHow much the attacker can disrupt the system or service.
- Partial
AV:A/View in NVD's calculator (opens in new tab)AC:L/ Au:N/ C:N/ I:N/ A:P - 7.4 HighCVSS 3.1 · SecondaryPrimary scores are NVD's own. Secondary scores come from the organization that published the CVE, or from CISA. · Scored by Internet Systems Consortium (ISC) (opens in new tab)
- Attack vectorWhere the attacker has to be. Network is the widest: anywhere on the Internet.
- Adjacent network
- Attack complexityWhether the attack depends on conditions the attacker doesn't control.
- Low
- Privileges requiredThe access the attacker needs before attacking.
- None
- User interactionWhether someone other than the attacker has to do something, like open a link.
- None
- ScopeWhether the attack can reach beyond the vulnerable component.
- Changed
- ConfidentialityHow much data the attacker can read.
- None
- IntegrityHow much data the attacker can change.
- None
- AvailabilityHow much the attacker can disrupt the system or service.
- High
CVSS:3.1/View in FIRST's calculator (opens in new tab)AV:A/ AC:L/ PR:N/ UI:N/ S:C/ C:N/ I:N/ A:H - 7.4 HighCVSS 3.1 · SecondaryPrimary scores are NVD's own. Secondary scores come from the organization that published the CVE, or from CISA. · Scored by NVD (opens in new tab)
- Attack vectorWhere the attacker has to be. Network is the widest: anywhere on the Internet.
- Adjacent network
- Attack complexityWhether the attack depends on conditions the attacker doesn't control.
- Low
- Privileges requiredThe access the attacker needs before attacking.
- None
- User interactionWhether someone other than the attacker has to do something, like open a link.
- None
- ScopeWhether the attack can reach beyond the vulnerable component.
- Changed
- ConfidentialityHow much data the attacker can read.
- None
- IntegrityHow much data the attacker can change.
- None
- AvailabilityHow much the attacker can disrupt the system or service.
- High
CVSS:3.1/View in FIRST's calculator (opens in new tab)AV:A/ AC:L/ PR:N/ UI:N/ S:C/ C:N/ I:N/ A:H
Weaknesses and attack patterns
The type of bug behind the vulnerability, and how attackers exploit that type.
Improper Restriction of Operations within the Bounds of a Memory Buffer · CWE-119 (opens in new tab)
The product performs operations on a memory buffer, but it reads from or writes to a memory location outside the buffer's intended boundary.
- Likelihood of exploitHow likely MITRE rates attacks on this type of weakness, in general rather than for this vulnerability.
- High
- AbstractionHow specific this weakness type is in MITRE's hierarchy, from broad pillars to specific variants. About MITRE's abstractions
- Class
- Mapping guidanceWhether MITRE recommends citing this weakness type for a single vulnerability. Broad types are discouraged in favor of more specific ones. About MITRE's mapping guidance
- Discouraged
- Part ofThe broader weakness types this one belongs to. About MITRE's hierarchy
References
Advisories, patches, exploits and more about this vulnerability.
- Patch
- Third Party Advisory
- Patch
- Third Party Advisory
- Patch
- Third Party Advisory
- Vendor Advisory
- Exploit
- Third Party Advisory
- Mailing List
- Third Party Advisory
- View on NVD (opens in new tab)Last changed
- View on CVE.org (opens in new tab)Last changed
This product uses the NVD API but is not endorsed or certified by the NVD (opens in new tab). CVE records from the CVE List (opens in new tab), weakness types from MITRE's CWE (opens in new tab)™ and attack patterns from its CAPEC (opens in new tab)™ are © The MITRE Corporation, used under the CVE (opens in new tab), CWE (opens in new tab) and CAPEC (opens in new tab) terms of use. Known exploited vulnerabilities and SSVC assessments are from CISA. Exploit predictions are from FIRST's EPSS (opens in new tab). About this data