dbcve.org
Server Platform Services FirmwareOperating system · Intel

CVE-2022-29466

MEDIUM · 5.5 CVSS v3.1 Published 2022-11-11
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
Improper input validation in firmware for Intel(R) SPS before version SPS_E3_04.01.04.700.0 may allow an authenticated user to potentially enable denial of service 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

Intel Server Platform Services (SPS) firmware before version SPS_E3_04.01.04.700.0 contains an improper input validation vulnerability. An authenticated user with local access could potentially exploit this to cause a denial of service condition.

MitigationUpdate Intel SPS firmware to version SPS_E3_04.01.04.700.0 or later. Since this requires local access, ensure physical or console access controls are in place until the patch can be applied.

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
Server Platform Services FirmwareOperating system
Affected:< sps_e3_04.01.04.700.0

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

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/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. Confirm Intel SPS firmware is present
    On Linux, run `dmidecode -t bios` or check BMC web interface for SPS firmware information. On Windows, use system information tools or Intel utilities to locate SPS component.
    Affected if Intel Server Platform Services firmware is listed in system firmware/bios information
  2. Retrieve SPS firmware version
    Use Intel tools (Intel System Debugger, Intel Management Engine firmware tools) or access BMC/UEFI firmware settings to locate the SPS firmware version field. The version typically appears as SPS_E3_XX.XX.XX.XXXX.X format.
    Affected if A version number in the SPS_E3_XXXX format is displayed
  3. Compare version against vulnerability threshold
    Compare your installed SPS firmware version string to the vulnerable threshold: SPS_E3_04.01.04.700.0. Versions numerically lower than 04.01.04.700.0 in the third octet or earlier are affected.
    Affected if Installed version is less than SPS_E3_04.01.04.700.0 (for example, 04.01.04.600.0 or earlier)
  4. Verify local access is possible
    Review system access controls: check if console access, physical access to server, or BMC remote management interfaces are accessible to authenticated users.
    Affected if Local or console authentication is enabled and users can interact with SPS firmware interfaces

System is affected if Intel SPS firmware is installed and the version is lower than SPS_E3_04.01.04.700.0, and the system allows authenticated local access to SPS interfaces.

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

Update Intel SPS firmware to version SPS_E3_04.01.04.700.0 or later. Since this requires local access, ensure physical or console access controls are in place until the patch can be applied.

Recommended fix High confidence

SPS_E3_04.01.04.700.0

  1. Obtain the fixed Intel SPS firmware version SPS_E3_04.01.04.700.0 or later from Intel's support website or your system vendor
  2. Download the appropriate SPS firmware update package for your specific Intel server platform
  3. Follow Intel's standard firmware update procedure - typically this involves running the firmware update utility or using Intel's Deployment Toolkit
  4. Ensure the system is powered appropriately during the update process (usually AC power)
  5. After update completes, verify the SPS firmware version has been updated to SPS_E3_04.01.04.700.0 or later

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

Fix this in Server Platform Services Firmware Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
13.0 hours of engineering $2,280
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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