Server Platform ServicesApplication · Intel

CVE-2022-36348

HIGH · 7.8 CVSS v3.1 Published 2023-02-16

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

NVD · unedited

Active debug code in some Intel (R) SPS firmware before version SPS_E5_04.04.04.300.0 may allow an authenticated user to potentially enable escalation of privilege via local access.

Technical summary

dbcve analysis · moderate confidence

Intel Server Platform Services (SPS) firmware contains active debug code that was not removed before production release. This debug functionality allows an authenticated local user to escalate privileges beyond their intended access level.

MitigationUpdate Intel SPS firmware to version SPS_E5_04.04.04.300.0 or later to remove the debug code.

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

Affected products & versions

NVD · CPE data

Server Platform ServicesApplication

Affected:< sps_e5_04.04.04.300.0

CVSS breakdown

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?

dbcve checks

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

Identify Intel SPS firmware version

Use Intel System Support Utility (Intel SSU) or access the SPS firmware through the BMC/IPMI interface (often via IPMItool command: ipmitool -I lanplus -H <BMC_IP> -U <user> -P <pass> raw commands or check firmware version in BIOS/UEFI settings under Server Management or Intel SPS firmware information)

Affected if The installed SPS firmware version is below 04.04.04.300.0 (for example, versions like 04.04.03.xxxx or earlier)
Locate SPS firmware version in system inventory

Check the Intel Server Platform Services firmware version displayed in the server's BMC web interface under Firmware Inventory or in the BIOS under Server Management > Intel SPS Firmware Info

Affected if The firmware version shown is less than sps_e5_04.04.04.300.0
Confirm SPS module is active

Verify that the Intel SPS firmware is running and accessible on the server. This is typically always active on Intel server platforms using SPS; confirm via BMC firmware status or running: ipmitool -I lanplus -H <BMC_IP> -U <user> -P <pass> mc info to check SPS management controller

Affected if The SPS firmware is present and running, indicating the debug code could potentially be present if version is vulnerable

You are affected if the Intel Server Platform Services firmware version installed on your server is below sps_e5_04.04.04.300.0 and the SPS firmware is active on the system.

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

Remediation

dbcve · scoped

Mitigation available No clean upgrade yet — mitigate in the meantime

Mitigation

Update Intel SPS firmware to version SPS_E5_04.04.04.300.0 or later to remove the debug code.

Recommended fix Moderate confidence

SPS_E5_04.04.04.300.0 or later

1. Identify the current Intel SPS firmware version installed on the server using Intel's system management tools or BIOS/UEFI interface
2. Navigate to Intel's support website and locate the SPS (Server Platform Services) firmware download page
3. Download the SPS firmware version SPS_E5_04.04.04.300.0 or later
4. Follow Intel's documented firmware update procedure for your specific server platform, typically involving a BIOS/UEFI update utility or Intel's Server Platform Services firmware update tool
5. Verify the firmware has been successfully applied by checking the SPS firmware version after update

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

Fix this in Server Platform Services Scoped from the published advisory

Consultation4.0 h
Implementation6.0 h
Testing4.0 h
Review / QA2.0 h

16.0 hours of engineering $2,840

Get help mitigating

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

Scan for this in your stack

Free · runs locally

dbcve dependency scanner

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

Primary sources

www.intel.comVendor Advisory
nvd.nist.govNVD record

Practitioner notes

Contributed

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

Notes0 Guidelines

Know something about CVE-2022-36348?

The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.

The version that genuinely resolved it — not the one the vendor claimed
A config change or rule that shut the vector down
A gotcha in the upgrade path that cost you an afternoon

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

At a glance

A fix existsA vendor remedy is published

Severity 7.8 High

Exploit likelihood EPSS, next 30 days 0.2%

Affects: Server Platform Services

Remediation

A high-priority fix

Fix this in Server Platform Services 16 hrs · Moderate

Typical engagement from $2,840

Get a fix See the full breakdown ↓

A high-priority vulnerability. Send your environment and a specialist will scope CVE-2022-36348 and return a fixed quote and timeline.

You’ll deal with our team directly and deploy the reviewed fix to staging first — never straight to production.

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.

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.

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.

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.

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.

Check your environment

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.

Scan for this in your stack

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

Practitioner notes

No notes yet

Official description

Technical summary

Affected products & versions

CVSS breakdown

Am I affected?

Remediation

References