CyberSecBulletin
CVE-2022-32485NVD status: Modified

Dell BIOS contains an improper input validation vulnerability.

CVE-2022-32485 is a high-severity improper input validation vulnerability in CPG BIOS 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. The record lists version 2.3 as the first without the flaw, so updating CPG BIOS to that release or later removes the exposure. There is no confirmed exploitation so far. EPSS estimates a 0.22% 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 CPG BIOS to 2.3 or a later version.
  2. Update Alienware Area 51m R1 Firmware to 1.21.0 or a later version.
  3. Update Alienware Area 51m R2 Firmware to 1.18.0 or a later version.
  4. Read the advisory on dell.com for workarounds and exact fixed builds.

Affected products and versions

VendorProductAffected versionsFixed in
DellCPG BIOSbefore 2.32.3
DellAlienware Area 51m R1 Firmwarebefore 1.21.01.21.0
DellAlienware Area 51m R2 Firmwarebefore 1.18.01.18.0
DellAlienware Aurora R11 Firmwarebefore 1.0.161.0.16
DellAlienware Aurora R12 Firmwarebefore 1.1.161.1.16
DellAlienware Aurora R13 Firmwarebefore 1.5.01.5.0
DellAlienware Aurora R10 Firmwarebefore 2.3.12.3.1
DellAlienware Aurora R8 Firmwarebefore 1.0.231.0.23
DellAlienware Aurora R9 Firmwarebefore 1.0.201.0.20
DellAlienware M15 R1 Firmwarebefore 2.14.02.14.0
DellAlienware M15 R2 Firmwarebefore 1.17.01.17.0
DellAlienware M15 R3 Firmwarebefore 1.19.01.19.0
DellAlienware M15 R4 Firmwarebefore 1.13.01.13.0
DellAlienware M17 R1 Firmwarebefore 2.14.02.14.0
DellAlienware M17 R2 Firmwarebefore 1.17.01.17.0
DellAlienware M17 R3 Firmwarebefore 1.19.01.19.0
DellAlienware M17 R4 Firmwarebefore 1.13.01.13.0
DellAlienware X14 Firmwarebefore 1.5.01.5.0
DellAlienware X15 R1 Firmwarebefore 1.11.01.11.0
DellAlienware X15 R2 Firmwarebefore 1.7.01.7.0
DellAlienware X17 R1 Firmwarebefore 1.11.01.11.0
DellAlienware X17 R2 Firmwarebefore 1.7.01.7.0
DellChengming 3980 Firmwarebefore 2.24.02.24.0
DellChengming 3988 Firmwarebefore 1.11.01.11.0
DellChengming 3990 Firmwarebefore 1.14.01.14.0

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
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.17.5HighCNA (emc.com)
CVSS 3.17.8HighNVD

Official description

Dell BIOS contains an improper input validation vulnerability. A local authenticated malicious user may potentially exploit this vulnerability by using an SMI to gain arbitrary code execution in 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: total).
  3. Record last changed materially (score, affected products, status or references).

References

Other vulnerabilities in CPG BIOS

All CPG BIOS vulnerabilities

Recent Improper Input Validation vulnerabilities

Spotted an error? Tell us.