CVE-2021-25217
Public on
Last Modified:
Description
A flaw was found in the Dynamic Host Configuration Protocol (DHCP). There is a discrepancy between the code that handles encapsulated option information in leases transmitted "on the wire" and the code which reads and parses lease information after it has been written to disk storage. This flaw allows an attacker to deliberately cause a situation where dhcpd while running in DHCPv4 or DHCPv6 mode, or the dhclient attempts to read a stored lease that contains option information, to trigger a stack-based buffer overflow in the option parsing code for colon-separated hex digits values. The highest threat from this vulnerability is to data confidentiality and integrity as well as service availability.
Statement
To abuse this flaw an attacker has to be on the same local sub-net of the victim machine. An attacker may send crafted DHCP messages with long lease statements that, when stored locally on file and then re-read by dhclient or dhcpd, might trigger the bug.
Additional Information
- This content is not included.Bugzilla 1963258: dhcp: stack-based buffer overflow when parsing statements with colon-separated hex digits in config or lease files in dhcpd and dhclient
- Content from cwe.mitre.org is not included.CWE-119: Improper Restriction of Operations within the Bounds of a Memory Buffer
- FAQ: Frequently asked questions about CVE-2021-25217
- Offline Security Data data is available for integration with other systems. See Offline Security Data API to get started.
External References
Content from www.cve.org is not included.https://www.cve.org/CVERecord?id=CVE-2021-25217
Content from nvd.nist.gov is not included.https://nvd.nist.gov/vuln/detail/CVE-2021-25217
Content from kb.isc.org is not included.https://kb.isc.org/docs/cve-2021-25217
Affected Packages and Issued Red Hat Security Errata
| Products / Services | Components | State | Errata |
|---|---|---|---|
| Red Hat Enterprise Linux 6 Extended Lifecycle Support | dhcp | Fixed | RHSA-2021:2419 |
| Red Hat Enterprise Linux 7 | dhcp | Fixed | RHSA-2021:2357 |
| Red Hat Enterprise Linux 7.2 Advanced Update Support | dhcp | Fixed | RHSA-2021:2418 |
| Red Hat Enterprise Linux 7.3 Advanced Update Support | dhcp | Fixed | RHSA-2021:2415 |
| Red Hat Enterprise Linux 7.4 Advanced Update Support | dhcp | Fixed | RHSA-2021:2414 |
| Red Hat Enterprise Linux 7.4 Telco Extended Update Support | dhcp | Fixed | RHSA-2021:2414 |
| Red Hat Enterprise Linux 7.4 Update Services for SAP Solutions | dhcp | Fixed | RHSA-2021:2414 |
| Red Hat Enterprise Linux 7.6 Advanced Update Support(Disable again in 2026 - SPRHEL-7118) | dhcp | Fixed | RHSA-2021:2469 |
| Red Hat Enterprise Linux 7.6 Telco Extended Update Support | dhcp | Fixed | RHSA-2021:2469 |
| Red Hat Enterprise Linux 7.6 Update Services for SAP Solutions | dhcp | Fixed | RHSA-2021:2469 |
| Red Hat Enterprise Linux 7.7 Extended Update Support | dhcp | Fixed | RHSA-2021:2405 |
| Red Hat Enterprise Linux 8 | dhcp | Fixed | RHSA-2021:2359 |
| Red Hat Enterprise Linux 8.1 Extended Update Support | dhcp | Fixed | RHSA-2021:2416 |
| Red Hat Enterprise Linux 8.2 Extended Update Support | dhcp | Fixed | RHSA-2021:2420 |
| Red Hat Enterprise Linux 9 | dhcp | Not affected | |
| Red Hat OpenShift Container Platform 4.7 | cri-o | Fixed | RHSA-2021:2555 |
| Red Hat OpenShift Container Platform 4.7 | dhcp | Fixed | RHSA-2021:2555 |
| Red Hat OpenShift Container Platform 4.7 | openshift-clients | Fixed | RHSA-2021:2555 |
| Red Hat OpenShift Container Platform 4.7 | openshift-kuryr | Fixed | RHSA-2021:2555 |
| Red Hat OpenShift Container Platform 4.7 | polkit | Fixed | RHSA-2021:2555 |
| Red Hat Virtualization 4 for Red Hat Enterprise Linux 7 | redhat-virtualization-host | Fixed | RHSA-2021:2519 |
Common Vulnerability Scoring System (CVSS) Score Details
Important note
CVSS scores for open source components depend on vendor-specific factors (e.g. version or build chain). Therefore, Red Hat's score and impact rating can be different from NVD and other vendors. Red Hat remains the authoritative CVE Naming Authorities (CNA) source for its products and services (see Red Hat classifications ).
| CVSS v3 Score Breakdown | Red Hat | NVD |
|---|---|---|
| CVSS v3 Base Score | 8.8 | 7.4 |
| Attack Vector | Adjacent Network | Adjacent Network |
| Attack Complexity | Low | Low |
| Privileges Required | None | None |
| User Interaction | None | None |
| Scope | Unchanged | Changed |
| Confidentiality Impact | High | None |
| Integrity Impact | High | None |
| Availability Impact | High | High |
CVSS v3 Vector
Red Hat CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
NVD CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:C/C:N/I:N/A:H
Red Hat CVSS v3 Score Explanation
Confidentiality, Integrity and Availability all set to High (C:H/I:H/A:H) due to the stack-based buffer overflow nature of the bug. In practice we were not able to overwrite any valuable data on the stack, but we do not exclude it might be possible to get code execution in some cases.
Frequently Asked Questions
Why is Red Hat's CVSS v3 score or Impact different from other vendors?
For more information, see https://access.redhat.com/solutions/762393.
My product is listed as "Under investigation" or "Affected", when will Red Hat release a fix for this vulnerability?
- "Under investigation" doesn't necessarily mean that the product is affected by this vulnerability. It only means that our Analysis Team is still working on determining whether the product is affected and how it is affected.
- "Affected" means that our Analysis Team has determined that this product is affected by this vulnerability and might release a fix to address this in the near future.
What can I do if my product is listed as "Will not fix"?
Available options depend mostly on the Impact of the vulnerability and the current Life Cycle phase of your product. Overall, you have the following options:
- Upgrade to a supported product version that includes a fix for this vulnerability (recommended).
- Apply a mitigation (if one exists).
- Open a This content is not included.support case to request a prioritization of releasing a fix for this vulnerability.
What can I do if my product is listed as "Fix deferred"?
Available options depend mostly on the Impact of the vulnerability and the current Life Cycle phase of your product. Overall, you have the following options:
- Apply a mitigation (if one exists).
- Open a This content is not included.support case to request a prioritization of releasing a fix for this vulnerability.
- Red Hat Engineering focuses on addressing high-priority issues based on their complexity or limited lifecycle support. Therefore, lower-priority issues will not receive immediate fixes.
What is a mitigation?
I have a Red Hat product but it is not in the above list, is it affected?
Why is my security scanner reporting my product as vulnerable to this vulnerability even though my product version is fixed or not affected?
Not sure what something means? Check out our Security Glossary.