dbcve.org
Xeon E 2314 FirmwareOperating system · Intel

CVE-2022-33894

HIGH · 7.8 CVSS v3.1 Published 2023-05-10
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
80/100
Remediation priority · High
Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

This vulnerability involves improper input validation in BIOS firmware for certain Intel processors. A privileged local user could exploit this flaw to achieve privilege escalation, effectively gaining higher-level system access beyond their current privileged user permissions.

MitigationApply the Intel-provided BIOS firmware update for affected processors. This typically requires coordination with the system OEM and careful planning due to the sensitive nature of BIOS updates.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Xeon E 2314 FirmwareOperating system
Affected:all versions
Xeon E 2324g FirmwareOperating system
Affected:all versions
Xeon E 2334 FirmwareOperating system
Affected:all versions
Xeon E 2336 FirmwareOperating system
Affected:all versions
Xeon E 2356g FirmwareOperating system
Affected:all versions
Xeon E 2374g FirmwareOperating system
Affected:all versions
Xeon E 2378 FirmwareOperating system
Affected:all versions
Xeon E 2378g FirmwareOperating system
Affected:all versions

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify the processor model
    Run 'dmidecode -t processor' or check system information to determine the exact CPU model number
    Affected if The CPU model is one of: Xeon E 2314, Xeon E 2324g, Xeon E 2334, Xeon E 2336, Xeon E 2356g, Xeon E 2374g, Xeon E 2378, or Xeon E 2378g
  2. Verify the BIOS firmware version
    Run 'dmidecode -s bios-version' to retrieve the current BIOS firmware version installed on the system
    Affected if The system uses one of the affected CPU models listed above and is running any BIOS firmware version that has not been updated to the Intel/OEM patched version
  3. Check for OEM BIOS update availability
    Consult the system OEM (Dell, HP, Lenovo, etc.) or Intel's product support pages for the specific Xeon E processor to determine if a BIOS firmware update addressing this vulnerability has been released
    Affected if No vendor-provided BIOS update has been applied to address this vulnerability for the specific processor model

A system is affected if it contains any of the listed Intel Xeon E processor models (2314, 2324g, 2334, 2336, 2356g, 2374g, 2378, 2378g) and the Intel/OEM BIOS firmware update for CVE-2022-33894 has not been applied.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply the Intel-provided BIOS firmware update for affected processors. This typically requires coordination with the system OEM and careful planning due to the sensitive nature of BIOS updates.

Recommended fix Moderate confidence

BIOS firmware version containing the security fix from Intel (contact Intel or your system vendor for the specific fixed version)

  1. Contact Intel or your system manufacturer to obtain the latest BIOS firmware update for your specific Xeon E processor model
  2. Download the BIOS firmware update from the official Intel website or your system vendor's support page
  3. Follow the manufacturer's instructions to update the BIOS firmware - typically this requires booting into the BIOS setup or using a firmware update utility
  4. Ensure the system is connected to a reliable power source during the firmware update process
  5. After the update completes, verify the BIOS version has been updated to the patched release
Caveat BIOS firmware updates can sometimes reset configuration settings to defaults; document current BIOS settings before updating

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Xeon E 2314 Firmware Scoped from the published advisory
  • Consultation8.0 h
  • Implementation4.0 h
  • Testing12.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,840
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,744.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-33894 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2022-33894 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data