CyberSecBulletin
CVE-2022-33894NVD status: Modified

Improper input validation in the BIOS firmware for some Intel(R) Processors may allow a…

Published Updated By the CyberSecBulletin desk

CVE-2022-33894 is a high-severity improper input validation vulnerability in Intel(R) Processors, 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 Intel(R) Processors versions: See references. The record does not name a fixed version, so check the vendor advisory. There is no confirmed exploitation so far. EPSS estimates a 0.25% 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. Check which version of Intel(R) Processors you run against the affected versions below, and install the vendor's latest release.
  2. Read the advisory on intel.com for workarounds and exact fixed builds.

Affected products and versions

VendorProductAffected versionsFixed in
Intel(R) ProcessorsIntel(R) ProcessorsSee referencesNot stated
IntelXeon E-2314 FirmwareNot specified in the recordNot stated
IntelXeon E-2324g FirmwareNot specified in the recordNot stated
IntelXeon E-2334 FirmwareNot specified in the recordNot stated
IntelXeon E-2336 FirmwareNot specified in the recordNot stated
IntelXeon E-2356g FirmwareNot specified in the recordNot stated
IntelXeon E-2374g FirmwareNot specified in the recordNot stated
IntelXeon E-2378 FirmwareNot specified in the recordNot stated
IntelXeon E-2378g FirmwareNot specified in the recordNot stated
IntelXeon E-2386g FirmwareNot specified in the recordNot stated
IntelXeon E-2388g FirmwareNot specified in the recordNot stated
IntelXeon E-2226ge FirmwareNot specified in the recordNot stated
IntelXeon E-2254me FirmwareNot specified in the recordNot stated
IntelXeon E-2254ml FirmwareNot specified in the recordNot stated
IntelXeon E-2276me FirmwareNot specified in the recordNot stated
IntelXeon E-2276ml FirmwareNot specified in the recordNot stated
IntelXeon E-2278ge FirmwareNot specified in the recordNot stated
IntelXeon E-2278gel FirmwareNot specified in the recordNot stated
IntelXeon E-2224 FirmwareNot specified in the recordNot stated
IntelXeon E-2224g FirmwareNot specified in the recordNot stated
IntelXeon E-2226g FirmwareNot specified in the recordNot stated
IntelXeon E-2234 FirmwareNot specified in the recordNot stated
IntelXeon E-2236 FirmwareNot specified in the recordNot stated
IntelXeon E-2244g FirmwareNot specified in the recordNot stated
IntelXeon E-2246g FirmwareNot specified in the recordNot stated

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 (intel.com)
CVSS 3.17.8HighNVD

Official description

Improper input validation in the BIOS firmware for some Intel(R) Processors may allow a privileged user to potentially enable escalation of privilege via local access.

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 Intel(R) Processors

All Intel(R) Processors vulnerabilities

Recent Improper Input Validation vulnerabilities

Spotted an error? Tell us.