CyberSecBulletin
CVE-2024-0161NVD status: Analyzed

Dell PowerEdge Server BIOS and Dell Precision Rack BIOS contain an Improper SMM communication…

CVE-2024-0161 is a high-severity improper input validation vulnerability in PowerEdge Platform from Dell, with a CVSS 3.1 base score of 8.4 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. The record lists versions 1.1.1, 1.13.2, 1.14.1 as the first without the flaw, so updating PowerEdge Platform to one of those releases or later removes the exposure. There is no confirmed exploitation so far. EPSS estimates a 0.2% 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 Platform to 1.1.1 or 1.13.2 or 1.14.1 or 1.9.1, whichever matches your release line, or a later version.
  2. Update Poweredge T360 Firmware to 1.1.1 or a later version.
  3. Update Poweredge R360 Firmware to 1.1.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 Platformbefore 1.1.1; before 1.13.2; before 1.14.1; before 1.9.1; before 2.21.2; before 2.21.1; before 2.21.0; before 2.19.0; and 3 more ranges1.1.1, 1.13.2, 1.14.1, 1.9.1, 2.21.2, 2.21.1
DellPoweredge T360 Firmwarebefore 1.1.11.1.1
DellPoweredge R360 Firmwarebefore 1.1.11.1.1
DellPoweredge R650 Firmwarebefore 1.13.21.13.2
DellPoweredge R750 Firmwarebefore 1.13.21.13.2
DellPoweredge R750xa Firmwarebefore 1.13.21.13.2
DellPoweredge C6520 Firmwarebefore 1.13.21.13.2
DellPoweredge Mx750c Firmwarebefore 1.13.21.13.2
DellPoweredge R550 Firmwarebefore 1.13.21.13.2
DellPoweredge R450 Firmwarebefore 1.13.21.13.2
DellPoweredge R650xs Firmwarebefore 1.13.21.13.2
DellPoweredge R750xs Firmwarebefore 1.13.21.13.2
DellPoweredge T550 Firmwarebefore 1.13.21.13.2
DellPoweredge Xr11 Firmwarebefore 1.13.21.13.2
DellPoweredge Xr12 Firmwarebefore 1.13.21.13.2
DellPoweredge Xr4510c Firmwarebefore 1.14.11.14.1
DellPoweredge Xr4520c Firmwarebefore 1.14.11.14.1
DellPoweredge T150 Firmwarebefore 1.9.11.9.1
DellPoweredge T350 Firmwarebefore 1.9.11.9.1
DellPoweredge R250 Firmwarebefore 1.9.11.9.1
DellPoweredge R350 Firmwarebefore 1.9.11.9.1
DellPoweredge R740 Firmwarebefore 2.21.22.21.2
DellPoweredge R740xd Firmwarebefore 2.21.22.21.2
DellPoweredge R640 Firmwarebefore 2.21.22.21.2
DellPoweredge R940 Firmwarebefore 2.21.22.21.2

Version data comes from the organisation that assigned the CVE; 35 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
ChangedThe attack can reach beyond the vulnerable component into other systems.
Confidentiality
NoneNo data is disclosed.
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:C/C:N/I:H/A:H. Scored by NVD.

Scoring systemScoreSeverityScored by
CVSS 3.17.2HighCNA (emc.com)
CVSS 3.18.4HighNVD

Official description

Dell PowerEdge Server BIOS and Dell Precision Rack BIOS contain an Improper SMM communication buffer verification vulnerability. A local low privileged attacker could potentially exploit this vulnerability leading to arbitrary writes to SMRAM.

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

The underlying weakness: Improper Input Validation

The product receives input or data, but it does not validate or incorrectly validates that the input has the properties that are required to process the data safely and correctly.

How developers prevent this class of flaw

  • Consider using language-theoretic security (LangSec) techniques that characterize inputs using a formal language and build recognizers for that language. This effectively requires parsing to be a distinct layer that effectively enforces a boundary between raw input and internal data representations, instead of allowing parser code to be scattered throughout the program, where it could be subject to errors or inconsistencies that create weaknesses.
  • Use an input validation framework such as Struts or the OWASP ESAPI Validation API. Note that using a framework does not automatically address all input validation problems; be mindful of weaknesses that could arise from misusing the framework itself (CWE-1173).
  • Understand all the potential areas where untrusted inputs can enter the product, including but not limited to: parameters or arguments, cookies, anything read from the network, environment variables, reverse DNS lookups, query results, request headers, URL components, e-mail, files, filenames, databases, and any external systems that provide data to the application. Remember that such inputs may be obtained indirectly through API calls.

More Improper Input Validation vulnerabilities (CWE-20)

Timeline

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

References

Other vulnerabilities in PowerEdge Platform

All PowerEdge Platform vulnerabilities

Recent Improper Input Validation vulnerabilities

Spotted an error? Tell us.