CyberSecBulletin
CVE-2023-25537NVD status: Modified

PowerEdge Platform: Out-of-bounds Write

Published Updated By the CyberSecBulletin desk

CVE-2023-25537 is a high-severity out-of-bounds write vulnerability in PowerEdge Platform from Dell, with a CVSS 3.1 base score of 7.8 out of 10. It can be exploited with local access to the system by an attacker with a low-privileged account, without any action from a user. Affected PowerEdge Platform versions: Versions prior to 2.18.1. The record does not name a fixed version, so check the vendor advisory. There is no confirmed exploitation so far. EPSS estimates a 0.18% chance of exploitation within 30 days, which is low compared with other CVEs.

Next patch cycle

High severity with no evidence of exploitation so far.

What to do

  1. Update Poweredge R740 Firmware to 2.18.1 or a later version.
  2. Update Poweredge R740xd Firmware to 2.18.1 or a later version.
  3. Update Poweredge R640 Firmware to 2.18.1 or a later version.
  4. Read the advisory on dell.com for workarounds and exact fixed builds.

Affected products and versions

VendorProductAffected versionsFixed in
DellPowerEdge PlatformVersions prior to 2.18.1Not stated
DellPoweredge R740 Firmwarebefore 2.18.12.18.1
DellPoweredge R740xd Firmwarebefore 2.18.12.18.1
DellPoweredge R640 Firmwarebefore 2.18.12.18.1
DellPoweredge R940 Firmwarebefore 2.18.12.18.1
DellPoweredge R540 Firmwarebefore 2.18.12.18.1
DellPoweredge R440 Firmwarebefore 2.18.12.18.1
DellPoweredge T440 Firmwarebefore 2.18.12.18.1
DellPoweredge Xr2 Firmwarebefore 2.18.12.18.1
DellPoweredge R740xd2 Firmwarebefore 2.18.12.18.1
DellPoweredge R840 Firmwarebefore 2.18.12.18.1
DellPoweredge R940xa Firmwarebefore 2.18.12.18.1
DellPoweredge T640 Firmwarebefore 2.18.12.18.1
DellPoweredge C6420 Firmwarebefore 2.18.12.18.1
DellPoweredge Fc640 Firmwarebefore 2.18.12.18.1
DellPoweredge M640 Firmwarebefore 2.18.12.18.1
DellPoweredge Mx740c Firmwarebefore 2.18.12.18.1
DellPoweredge Mx840c Firmwarebefore 2.18.12.18.1
DellPoweredge C4140 Firmwarebefore 2.18.12.18.1
DellDss 8440 Firmwarebefore 2.18.12.18.1
DellPoweredge Xe2420 Firmwarebefore 2.18.12.18.1
DellPoweredge Xe7420 Firmwarebefore 2.18.12.18.1
DellPoweredge Xe7440 Firmwarebefore 2.18.12.18.1
DellEmc Storage Nx3240 Firmwarebefore 2.18.12.18.1
DellEmc Storage Nx3340 Firmwarebefore 2.18.12.18.1

Version data comes from the organisation that assigned the CVE; 6 further products are omitted here. Confirm against the vendor advisory before deciding you are unaffected.

How the severity score breaks down

Attack vector
LocalThe attacker needs local access or must trick a user into running something.
Attack complexity
LowNo special conditions are needed; the attack works reliably.
Privileges required
LowA basic user account is enough.
User interaction
NoneNo action by a victim is required.
Scope
UnchangedImpact stays within the vulnerable component.
Confidentiality
HighAll data handled by the component can be read.
Integrity
HighData or code can be modified at will.
Availability
HighThe component can be taken down completely.

Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H. Scored by NVD.

Scoring systemScoreSeverityScored by
CVSS 3.16.1MediumCNA (emc.com)
CVSS 3.17.8HighNVD

Official description

Dell PowerEdge 14G server BIOS versions prior to 2.18.1 and Dell Precision BIOS versions prior to 2.18.2, contain an Out of Bounds write vulnerability. A local attacker with low privileges could potentially exploit this vulnerability leading to exposure of some SMRAM stack/data/code in System Management Mode, leading to arbitrary code execution or escalation of privilege.

Source: the CVE record as published by its numbering authority, via NVD and CVE.org.

The underlying weakness: Out-of-bounds Write

The product writes data past the end, or before the beginning, of the intended buffer.

How developers prevent this class of flaw

  • Use a language that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid. For example, many languages that perform their own memory management, such as Java and Perl, are not subject to buffer overflows. Other languages, such as Ada and C#, typically provide overflow protection, but the protection can be disabled by the programmer. Be wary that a language's interface to native code may still be subject to overflows, even if the language itself is theoretically safe.
  • Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid. Examples include the Safe C String Library (SafeStr) by Messier and Viega, and the Strsafe.h library from Microsoft. These libraries provide safer versions of overflow-prone string-handling functions.
  • Use automatic buffer overflow detection mechanisms that are offered by certain compilers or compiler extensions. Examples include: the Microsoft Visual Studio /GS flag, Fedora/Red Hat FORTIFY_SOURCE GCC flag, StackGuard, and ProPolice, which provide various mechanisms including canary-based detection and range/index checking. D3-SFCV (Stack Frame Canary Validation) from D3FEND discusses canary-based detection in detail.

More Out-of-bounds Write vulnerabilities (CWE-787)

Timeline

  1. CVE record published.
  2. CISA published its SSVC assessment (exploitation: none, automatable: no, technical impact: total).
  3. Record last changed materially (score, affected products, status or references).

References

Other vulnerabilities in PowerEdge Platform

All PowerEdge Platform vulnerabilities

Recent Out-of-bounds Write vulnerabilities

Spotted an error? Tell us.