dbcve.org
Server Platform ServicesApplication · Intel

CVE-2019-0089

MEDIUM · 6.7 CVSS v3.0 Published 2019-05-17
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
69/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 data sanitization vulnerability in subsystem in Intel(R) SPS before versions SPS_E5_04.00.04.381.0, SPS_E3_04.01.04.054.0, SPS_SoC-A_04.00.04.181.0, and SPS_SoC-X_04.00.04.086.0 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

Improper data sanitization in a subsystem of Intel Server Platform Services (SPS) firmware allows a privileged local user to potentially escalate privileges. The vulnerability affects SPS_E5, SPS_E3, SPS_SoC-A, and SPS_SoC-X versions prior to their respective patched releases.

MitigationUpdate Intel SPS firmware to version SPS_E5_04.00.04.381.0, SPS_E3_04.01.04.054.0, SPS_SoC-A_04.00.04.181.0, SPS_SoC-X_04.00.04.086.0 or later.

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 ServicesApplication
Affected:< sps_e5_04.00.04.381.0< sps_e3_04.01.04.054.0< sps_soc-a_04.00.04.181.0< sps_soc-x_04.00.04.086.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
High
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.0/AV:L/AC:L/PR:H/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 if Intel SPS firmware is present
    Check the server's BMC (Baseboard Management Controller) for Intel Server Platform Services firmware. This can be done via IPMI: `ipmitool -I lanplus -H <bmc_ip> -U admin -P <password> fru print` or check BIOS/UEFI firmware information during boot. SPS firmware typically appears as a separate firmware component from the main BIOS.
    Affected if Intel SPS firmware is not installed or the system does not have an Intel Server Platform Services module, then this CVE does not apply.
  2. Retrieve SPS firmware version
    Use IPMI to query the SPS firmware version. Common command: `ipmitool -I lanplus -H <bmc_ip> -U admin -P <password> raw 0x30 0x03 0x00` or check via BMC web interface under Firmware/Software inventory. The output will show a version string such as 04.00.04.xxx or 04.01.04.xxx.
    Affected if The command fails to return a version or shows no SPS firmware, then SPS may not be present.
  3. Compare version for SPS_E5
    If the SPS firmware is for the E5 platform (check via `ipmitool fru print` or BMC inventory showing 'SPS' or 'Server Platform Services'), compare the full version string against 04.00.04.381.0. Versions like 04.00.04.200, 04.00.03.100, or any version starting with 04.00.04.xxx where the last number is less than 381 are affected.
    Affected if The installed SPS_E5 version is less than 04.00.04.381.0, the system is vulnerable.
  4. Compare version for SPS_E3
    For SPS_E3 firmware, compare the version string against 04.01.04.054.0. Versions such as 04.01.03.200 or 04.01.04.020 are vulnerable if the last number is less than 054.
    Affected if The installed SPS_E3 version is less than 04.01.04.054.0, the system is vulnerable.
  5. Compare version for SPS_SoC-A
    For SPS_SoC-A firmware (System-on-Chip variant A), compare against 04.00.04.181.0. Any version below this threshold is affected.
    Affected if The installed SPS_SoC-A version is less than 04.00.04.181.0, the system is vulnerable.
  6. Compare version for SPS_SoC-X
    For SPS_SoC-X firmware (System-on-Chip variant X), compare against 04.00.04.086.0. Any version below this threshold is affected.
    Affected if The installed SPS_SoC-X version is less than 04.00.04.086.0, the system is vulnerable.

A system is affected if it runs any Intel SPS firmware version (E5, E3, SoC-A, or SoC-X) that is numerically lower than the respective patched release version for that platform.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update Intel SPS firmware to version SPS_E5_04.00.04.381.0, SPS_E3_04.01.04.054.0, SPS_SoC-A_04.00.04.181.0, SPS_SoC-X_04.00.04.086.0 or later.

Fix this in Server Platform Services Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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