dbcve.org
Xeon E 2314 FirmwareOperating system · Intel

CVE-2022-38087

MEDIUM · 5.5 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 →
57/100
Remediation priority · Elevated
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
Exposure of resource to wrong sphere in BIOS firmware for some Intel(R) Processors may allow a privileged user to potentially enable information disclosure 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

BIOS firmware vulnerability in Intel processors where resources are exposed to the wrong security sphere ('sphere' refers to security domains or privilege levels). A privileged local user may exploit this to obtain unauthorized information disclosure.

MitigationApply Intel-provided BIOS/firmware updates from the system manufacturer. Contact OEM vendors for patch availability and schedule firmware updates following vendor deployment procedures.

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
None
Availability
None

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

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 installed CPU model
    Run the command 'wmic cpu get Name,ProcessorId' on Windows or 'cat /proc/cpuinfo | grep "model name"' on Linux to retrieve the processor model name.
    Affected if The CPU model matches any of the following: 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 CPU family
    Run 'wmic cpu get Family' on Windows or 'lscpu | grep "CPU family"' on Linux to confirm the processor belongs to the Intel Xeon E family.
    Affected if The CPU family indicates a Xeon E series processor matching the affected SKUs.
  3. Check BIOS/firmware version
    Run 'wmic bios get SMBIOSBIOSVersion' on Windows, 'dmidecode -s bios-version' on Linux, or access the BIOS setup utility during boot to view the firmware version.
    Affected if The system uses one of the affected CPU models (all firmware versions are vulnerable).
  4. Determine local privilege context
    Review local user accounts and privilege assignments using 'whoami /all' on Windows or 'id' and 'sudo -l' on Linux to determine if standard users or untrusted accounts have elevated privileges.
    Affected if Multiple local users exist with administrative or root privileges, or untrusted accounts have elevated access, increasing the attack surface for this privilege-escalation-style flaw.

You are affected if your system uses any of the listed Intel Xeon E processor models (2314, 2324g, 2334, 2336, 2356g, 2374g, 2378, or 2378g) regardless of BIOS version, and untrusted local users have elevated privileges.

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 Intel-provided BIOS/firmware updates from the system manufacturer. Contact OEM vendors for patch availability and schedule firmware updates following vendor deployment procedures.

Recommended fix Moderate confidence

Contact Intel or your system OEM for the specific fixed BIOS/firmware release; Intel typically provides microcode/firmware updates through system vendors

  1. Check Intel's official security advisory for this vulnerability (INTEL-SA-00814 or similar) at www.intel.com for specific firmware version information
  2. Contact your Intel server/ workstation system vendor or OEM to obtain the latest BIOS/firmware update for your specific system
  3. Apply the vendor-provided BIOS/system firmware update that addresses this vulnerability
  4. Verify the firmware version has been updated after applying the patch
  5. Refer to Intel's security notice at security.netapp.com for any additional guidance on affected products
Caveat Firmware updates may require system downtime and should be tested in a non-production environment first

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

Fix this in Xeon E 2314 Firmware Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA3.0 h
21.0 hours of engineering $3,680
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-38087 — 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-38087 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