BlackTreeIndependent security intelligence
← Back to the CVE catalogue
Full vulnerability report · 2021
CVE-2021-25217High confidence

A buffer overrun in lease file parsing code can be used to exploit a common vulnerability shared by dhcpd and dhclient

ISC · ISC DHCP

7.4HighCVSS 3.1
Recommended action
Within 7 days

High technical severity with public exploit material referenced by a structured source; prioritise exposed affected systems while verifying vendor guidance.

Patch available
Direct vendor intelligence

Authoritative vendor CSAF and VEX advisories

Structured product status and remediation from the issuing vendor. Product-state explanations are always visible; large lists can be searched or downloaded.

4 current
SCA-2025-0011 · CSAF 2.0 · revision 1.0.0 · finalSICK PSIRTVulnerabilities affecting Endress+Hauser SSG-E210GC
1 known affected

The vendor explicitly identifies these products as affected by this CVE.

  • Endress+Hauser SSG-E210GC all Firmware versions
Summary
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.
Remediation
Please make sure that only trusted entities have access to the device. Furthermore, you should apply the following General Security Measures when operating the product to mitigate the associated security risk. The collected resources "SICK Operating Guidelines" and "ICS-CERT recommended practices on Industrial Security" could help to implement the general security practices.
SCA-2025-0009 · CSAF 2.0 · revision 1 · finalSICK PSIRTVulnerabilities affecting SICK TDC-E210GC
1 known affected

The vendor explicitly identifies these products as affected by this CVE.

  • SICK TDC-E210GC all Firmware versions
Summary
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.
Remediation
Please make sure that only trusted entities have access to the device. Furthermore, you should apply the following General Security Measures when operating the product to mitigate the associated security risk. The collected resources "SICK Operating Guidelines" and "ICS-CERT recommended practices on Industrial Security" could help to implement the general security practices.
SSA-637483 · CSAF 2.0 · revision 1 · finalSiemens ProductCERTSSA-637483 Third-Party Component Vulnerabilities in SINEC INS before V1.0 SP2
1 known affected

The vendor explicitly identifies these products as affected by this CVE.

  • SINEC INS
Summary
The affected products contain the third party component, ISC DHCP, that possesses a vulnerability if used as a DHCP client or server. The vulnerability affects the DHCP package when storing and reading DHCP lease information containing particular option information. An attacker could exploit this vulnerability to affect the availability of the DHCP client or server, or in the worst case affect the confidentiality or integrity of device through a buffer overflow or cause a remote-code execution.
Remediation
Update to V1.0 SP2 or later version
SSA-406691 · CSAF 2.0 · revision 1 · finalSiemens ProductCERTSSA-406691: Buffer Vulnerabilities in DHCP function of RUGGEDCOM ROX products
10 known affected

The vendor explicitly identifies these products as affected by this CVE.

  • RUGGEDCOM ROX MX5000
  • RUGGEDCOM ROX RX1400
  • RUGGEDCOM ROX RX1500
  • RUGGEDCOM ROX RX1501
  • RUGGEDCOM ROX RX1510
  • RUGGEDCOM ROX RX1511
  • RUGGEDCOM ROX RX1512
  • RUGGEDCOM ROX RX1524
  • RUGGEDCOM ROX RX1536
  • RUGGEDCOM ROX RX5000
Summary
The affected products contain the third party component, ISC DHCP, that possesses a vulnerability if used as a DHCP client or server. The vulnerability affects the DHCP package when storing and reading DHCP lease information containing particular option information. An attacker could exploit this vulnerability to affect the availability of the DHCP client or server, or in the worst case affect the confidentiality or integrity of device through a buffer overflow or cause a remote-code execution.
Remediation
Update to V2.15.0 or later version
Optional official sources

National CERT insights
?CERT means Computer Emergency Response Team; CSIRT is the closely related term Computer Security Incident Response Team.

Select the national-authority views to include. The exact source language is shown on each matched advisory. Your choice is remembered on this device and encoded in the shareable URL.

Official European source

ENISA European Vulnerability Database

Official EUVD identifiers, advisory evidence and known-exploited context. Missing fields are not treated as evidence of low risk.

1 current
ENISA EUVD identifier

EUVD-2021-12128

No EUVD known-exploited evidence

ENISA has published the identifier mapping but no EUVD description has been stored yet.

EUVD state
Present in the current official mapping
Known exploitation
Not present in the current ENISA EUVD known-exploited dataset. This is not proof of no exploitation.
ENISA score
Not supplied in the stored EUVD record
Advisory evidence
No linked advisory details stored yet
Recommended actionWithin 7 days

High technical severity with public exploit material referenced by a structured source; prioritise exposed affected systems while verifying vendor guidance.

Patch available
01

What, why and how

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.

What

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.

Why

The product performs operations on a memory buffer, but it reads from or writes to a memory location outside the buffer's intended boundary. This may result in read or write operations on unexpected memory locations that could be linked to other variables, data structures, or internal program data.

How

An attacker operating through an adjacent network may attempt exploitation without authentication or user interaction. If successful, the issue may disrupt the affected service.

What

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.

Why

The product performs operations on a memory buffer, but it reads from or writes to a memory location outside the buffer's intended boundary. This may result in read or write operations on unexpected memory locations that could be linked to other variables, data structures, or internal program data.

How

An attacker operating through an adjacent network may attempt exploitation without authentication or user interaction. If successful, the issue may disrupt the affected service.

02

Exploit reality and attack path

CVSS severity, EPSS forecast probability, public exploit material and CISA-confirmed exploitation are separate signals.

Observed exploitation
?Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.
No confirmed evidence

No CISA KEV match was present at the last successful refresh. This means no confirmation from that source, not proof of no exploitation.

Public PoC / exploit material
?Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.
Reference recorded

A structured CVE source labels at least one public reference as exploit material. BlackTree has not independently validated that it is safe, reliable or weaponised.

Likely attack path
an adjacent network → Improper Restriction of Operations within the Bounds of a Memory Buffer → disrupt the affected service
Attack surface
Adjacent
Privileges required
None: unauthenticated exploitation is possible
User interaction
None
Attack complexity
Low: no specialised conditions are recorded
Security boundary
Changed: exploitation can affect a different security authority
Weakness
?CWE means Common Weakness Enumeration: a standard category for the underlying weakness.
CWE-119 ↗

CWE-119: Improper Restriction of Operations within the Bounds of a Memory Buffer. The product performs operations on a memory buffer, but it reads from or writes to a memory location outside the buffer's intended boundary. This may result in read or write operations on unexpected memory locations that could be linked to other variables, data structures, or internal program data.

CVSS vector
?CVSS means Common Vulnerability Scoring System. The vector records the metric values used to calculate technical severity.
CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:C/C:N/I:N/A:H

Common Vulnerability Scoring System 3.1: the compact vector below is decoded into plain language.

AVAdjacentAttack vector: The attacker must be on an adjacent or logically close network.ACLowAttack complexity: No specialised conditions are required beyond attacker-controlled input.PRNonePrivileges required: The attacker does not need an account or existing privileges.UINoneUser interaction: No action by another user is required.SChangedScope: The attack can affect a component governed by a different security authority.CNoneConfidentiality impact: No direct loss is represented by this metric.INoneIntegrity impact: No direct loss is represented by this metric.AHighAvailability impact: A successful attack can cause a major loss.
Post-exploitation / living off the land
No specific living-off-the-land technique is confirmed in the structured sources. Monitor normal administration tools for activity inconsistent with the affected service's baseline.
UnauthenticatedDenial of serviceCWE-119Public exploit reference
A

Official authority intelligence

Only matched European and national findings are included. Language selectors and unavailable sources are omitted.

BSI · German · WID-SEC-W-2023-0063Juniper Junos Space: Mehrere Schwachstellen

Ein Angreifer aus dem angrenzenden Netzwerk oder ein entfernter anonymer, authentisierter oder lokaler Angreifer kann mehrere Schwachstellen in Juniper Junos Space ausnutzen, um Sicherheitsmaßnahmen zu umgehen, vertrauliche Informationen offenzulegen, einen Denial-of-Service-Zustand auszulösen, beliebigen Code auszuführen und seine Privilegien zu erweitern.

Official advisory
BSI · German · WID-SEC-W-2023-1261Internet Systems Consortium DHCP: Schwachstelle ermöglicht Denial of Service

Ein Angreifer aus dem benachbarten Netzwerk kann eine Schwachstelle in Internet Systems Consortium DHCP ausnutzen, um einen Denial of Service Angriff durchzuführen.

Official advisory
CERT-FR · French · CERTFR-2025-AVI-0969Multiples vulnérabilités dans les produits VMware

/CVERecord?id=CVE-2021-2161 Référence CVE CVE-2021-2163 https://www.cve.org/CVERecord?id=CVE-2021-2163 Référence CVE CVE-2021-23177 https://www.cve.org/CVERecord?id=CVE-2021-23177 Référence CVE CVE-2021-23215 https://www.cve.org/CVERecord?id=CVE-2021-23215 Référence CVE CVE-2021-2341 https://www.cve.org/CVERecord?id=CVE-2021-2341 Référence CVE CVE-2021-2369 https://www.cve.org/CVERecord?id=CVE-2021-2369 Référence CVE CVE-2021-2388 https://www.cve.org/CVERecord?id=CVE-2021-2388 Référence CVE CVE-2021-24031 https://www.cve.org/CVERecord?id=CVE-2021-24031 Référence CVE CVE-2021-24032 https://www.cve.org/CVERecord?id=CVE-2021-24032 Référence CVE CVE-2021-25217 https://www.cve.org/CVERecord?id=CVE-2021-25217 Référence CVE CVE-2021-26260 https://www.cve.org/CVERecord?id=CVE-2021-26260 Référence CVE CVE-2021-26720 https://www.cve.org/CVERecord?id=CVE-2021-26720 Référence CVE CVE-2021-26945 https://www.cve.org/CVERecord?id=CVE-2021-26945 Référence CVE CVE-2021-27645 https://www.cve.org/CVERecord?id=CVE-2021-27645 Référence CVE CVE-2021-28544 https://www.cve.org/CVERecord?id=CVE-2021-28544 Référence CVE CVE-2021-28861 https://www.cve.org/CVERecord?id=CVE-2021-28861 Référence CVE CVE-2021-29921 https://www.cve.org/CVERecord?id=CVE-2021-29921 Référence CVE CVE-2021-29923 https://www.cve.org/CVERecord?id=

Official advisory
CERT-FR · French · CERTFR-2023-AVI-0051Multiples vulnérabilités dans les produits Juniper

.org/CVERecord?id=CVE-2021-2369 Référence CVE CVE-2021-2372 https://www.cve.org/CVERecord?id=CVE-2021-2372 Référence CVE CVE-2021-23840 https://www.cve.org/CVERecord?id=CVE-2021-23840 Référence CVE CVE-2021-23841 https://www.cve.org/CVERecord?id=CVE-2021-23841 Référence CVE CVE-2021-2385 https://www.cve.org/CVERecord?id=CVE-2021-2385 Référence CVE CVE-2021-2388 https://www.cve.org/CVERecord?id=CVE-2021-2388 Référence CVE CVE-2021-2389 https://www.cve.org/CVERecord?id=CVE-2021-2389 Référence CVE CVE-2021-2390 https://www.cve.org/CVERecord?id=CVE-2021-2390 Référence CVE CVE-2021-2432 https://www.cve.org/CVERecord?id=CVE-2021-2432 Référence CVE CVE-2021-25217 https://www.cve.org/CVERecord?id=CVE-2021-25217 Référence CVE CVE-2021-26691 https://www.cve.org/CVERecord?id=CVE-2021-26691 Référence CVE CVE-2021-27219 https://www.cve.org/CVERecord?id=CVE-2021-27219 Référence CVE CVE-2021-27363 https://www.cve.org/CVERecord?id=CVE-2021-27363 Référence CVE CVE-2021-27364 https://www.cve.org/CVERecord?id=CVE-2021-27364 Référence CVE CVE-2021-27365 https://www.cve.org/CVERecord?id=CVE-2021-27365 Référence CVE CVE-2021-28950 https://www.cve.org/CVERecord?id=CVE-2021-28950 Référence CVE CVE-2021-29154 https://www.cve.org/CVERecord?id=CVE-2021-29154 Référence CVE CVE-2021-29650 https://www.cve.org/CVERecord?id=

Official advisory
CERT-FR · French · CERTFR-2022-AVI-814Multiples vulnérabilités dans les produits SIEMENS

rt/html/ssa-638652.html Référence CVE CVE-2016-0701 https://www.cve.org/CVERecord?id=CVE-2016-0701 Référence CVE CVE-2020-12762 https://www.cve.org/CVERecord?id=CVE-2020-12762 Référence CVE CVE-2020-28168 https://www.cve.org/CVERecord?id=CVE-2020-28168 Référence CVE CVE-2020-28500 https://www.cve.org/CVERecord?id=CVE-2020-28500 Référence CVE CVE-2020-7793 https://www.cve.org/CVERecord?id=CVE-2020-7793 Référence CVE CVE-2021-23337 https://www.cve.org/CVERecord?id=CVE-2021-23337 Référence CVE CVE-2021-23839 https://www.cve.org/CVERecord?id=CVE-2021-23839 Référence CVE CVE-2021-23841 https://www.cve.org/CVERecord?id=CVE-2021-23841 Référence CVE CVE-2021-25217 https://www.cve.org/CVERecord?id=CVE-2021-25217 Référence CVE CVE-2021-25220 https://www.cve.org/CVERecord?id=CVE-2021-25220 Référence CVE CVE-2021-3749 https://www.cve.org/CVERecord?id=CVE-2021-3749 Référence CVE CVE-2021-4160 https://www.cve.org/CVERecord?id=CVE-2021-4160 Référence CVE CVE-2022-0155 https://www.cve.org/CVERecord?id=CVE-2022-0155 Référence CVE CVE-2022-0235 https://www.cve.org/CVERecord?id=CVE-2022-0235 Référence CVE CVE-2022-0396 https://www.cve.org/CVERecord?id=CVE-2022-0396 Référence CVE CVE-2022-37011 https://www.cve.org/CVERecord?id=CVE-2022-37011 Référence CVE CVE-2022-38466 https://www.cve.org/CVERecord?id=CVE-2022-3

Official advisory
CERT-FR · French · CERTFR-2022-AVI-216Multiples vulnérabilités dans les produits Siemens

d?id=CVE-2021-25173 Référence CVE CVE-2021-25174 https://www.cve.org/CVERecord?id=CVE-2021-25174 Référence CVE CVE-2021-25175 https://www.cve.org/CVERecord?id=CVE-2021-25175 Référence CVE CVE-2021-25176 https://www.cve.org/CVERecord?id=CVE-2021-25176 Référence CVE CVE-2021-25177 https://www.cve.org/CVERecord?id=CVE-2021-25177 Référence CVE CVE-2021-25178 https://www.cve.org/CVERecord?id=CVE-2021-25178 Référence CVE CVE-2021-25214 https://www.cve.org/CVERecord?id=CVE-2021-25214 Référence CVE CVE-2021-25215 https://www.cve.org/CVERecord?id=CVE-2021-25215 Référence CVE CVE-2021-25216 https://www.cve.org/CVERecord?id=CVE-2021-25216 Référence CVE CVE-2021-25217 https://www.cve.org/CVERecord?id=CVE-2021-25217 Référence CVE CVE-2021-25219 https://www.cve.org/CVERecord?id=CVE-2021-25219 Référence CVE CVE-2021-27290 https://www.cve.org/CVERecord?id=CVE-2021-27290 Référence CVE CVE-2021-31344 https://www.cve.org/CVERecord?id=CVE-2021-31344 Référence CVE CVE-2021-31346 https://www.cve.org/CVERecord?id=CVE-2021-31346 Référence CVE CVE-2021-31784 https://www.cve.org/CVERecord?id=CVE-2021-31784 Référence CVE CVE-2021-31889 https://www.cve.org/CVERecord?id=CVE-2021-31889 Référence CVE CVE-2021-31890 https://www.cve.org/CVERecord?id=CVE-2021-31890 Référence CVE CVE-2021-32803 https://www.cve.org/CVERecord?id=

Official advisory
CERT-FR · French · CERTFR-2021-AVI-788Multiples vulnérabilités dans IBM Cloud Foundry Migration Runtime

De multiples vulnérabilités ont été découvertes dans IBM Cloud Foundry Migration Runtime. Certaines d'entre elles permettent à un attaquant de provoquer une exécution de code arbitraire, un déni de service à distance et un contournement de la politique de sécurité.

Official advisory
CERT-FR · French · CERTFR-2021-AVI-410Vulnérabilité dans ISC DHCP

Une vulnérabilité a été découverte dans ISC DHCP. Elle permet à un attaquant de provoquer un déni de service à distance.

Official advisory
03

Patch and workaround

Operational remediation based on structured source evidence.

Status
?Patch availability is based on structured fixed-version fields and authoritative update references. If no fix is verified, check the vendor advisory before making a change.
Patch available
Affected
Endress+Hauser SSG-E210GC all Firmware versions
Fixed
An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release.
Action
Review the linked authoritative reference and apply the recorded fixed release appropriate to the affected product branch.
Workaround
Please make sure that only trusted entities have access to the device. Furthermore, you should apply the following General Security Measures when operating the product to mitigate the associated security risk. The collected resources "SICK Operating Guidelines" and "ICS-CERT recommended practices on Industrial Security" could help to implement the general security practices.
04

Evidence and provenance

Published 26 May 2021 · Last source change 16 Sept 2024, 22:08 UTC · CWE-119 · Improper Restriction of Operations within the Bounds of a Memory Buffer

CVE recordCVE.org · 5.1
CVSS sourceCNA
EPSS source
?The date BlackTree first stored a score for this CVE from the daily FIRST EPSS feed.
FIRST · tracked since 2026-08-14
European sourceENISA EUVD · EUVD-2021-12128
Product sourceVendor CSAF · SICK PSIRT
Remediation sourceVendor CSAF · SICK PSIRT
CWE sourceNIST NVD
NVD statusNVD modified after enrichment

Core structured fields are present and their contributing authorities are shown above.

Material change intelligence

What changed after publication

View recent updates →
  1. Vendor guidanceAuthoritative vendor guidance changed from authoritative remediation link to authoritative remediation link.
    Before
    authoritative remediation link
    After
    authoritative remediation link
    SICK PSIRT ↗
  2. Vendor guidanceAuthoritative vendor guidance changed from authoritative remediation link to authoritative remediation link.
    Before
    authoritative remediation link
    After
    authoritative remediation link
    SICK PSIRT ↗
Material fields only · duplicate refreshes suppressed · history retained for the configured operational retention period
CVE published
Fixed release or patch reference recorded
ENISA EUVD · EUVD-2021-12128↗Vendor CSAF · SICK PSIRT↗Public exploit reference↗Patch or update reference↗Patch or update reference↗Patch or update reference↗Official CVE record (CNA and ADP data)↗NVD record↗
Technical terms and abbreviations used in this report
CVE
Common Vulnerabilities and Exposures: the public identifier for one disclosed vulnerability.
CVSS
Common Vulnerability Scoring System: a technical severity framework; it is not patching priority by itself.
EPSS
Exploit Prediction Scoring System: FIRST's estimate of the probability that exploitation activity will be observed in the next 30 days; it is a forecast, not confirmation.
CWE
Common Weakness Enumeration: the standard category describing the underlying software or hardware weakness.
CNA
CVE Numbering Authority: an organisation authorised to assign and publish CVE records.
CISA ADP
Cybersecurity and Infrastructure Security Agency Authorized Data Publisher: structured enrichment added to a CVE record.
NVD
National Vulnerability Database: NIST's enrichment service for CVE records.
CERT / CSIRT
A computer security incident response team that publishes warnings or coordinates incident response.
PoC
Proof of concept: public material that demonstrates or helps reproduce exploitation.
CSAF
Common Security Advisory Framework: a machine-readable format for security advisories.
LoTL
Living off the land: abuse of legitimate tools or system functions during an attack.
Free version - for non-commercial use only.CVE-2021-25217 · cve.blacktree.nl