CVE-2019-0099
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 · uneditedInsufficient access control vulnerability in subsystem in Intel(R) SPS before version SPS_E3_05.00.04.027.0 may allow an unauthenticated user to potentially enable escalation of privilege via physical 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 confidenceInsufficient access control in Intel Server Platform Services (SPS) firmware allows an unauthenticated user with physical access to the server to escalate privileges. The vulnerability exists in the SPS subsystem and affects versions prior to SPS_E3_05.00.04.027.0, enabling a local attacker to potentially gain elevated system privileges through physical access.
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< sps_e3_05.00.04.027.0CVSS 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
- Physical
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:P/AC:L/PR:N/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 checksWork through these to decide whether this CVE applies to you.
-
Identify if Intel SPS firmware is presentCheck system firmware/BIOS information for Intel Server Platform Services. On Linux, try: `dmidecode -s bios-version` or check BMC/IPMI interface for SPS firmware version. Intel SPS is typically found on server platforms with Intel Xeon processors.Affected if System uses Intel Server Platform Services firmware and the SPS version cannot be determined or is earlier than SPS_E3_05.00.04.027.0
-
Retrieve SPS firmware versionAccess the BMC/IPMI web interface or use IPMI commands: `ipmitool -I lanplus -H <bmc_ip> -U <user> -P <pass> raw` to read SPS firmware version, or check within BIOS/UEFI setup under 'Server Management' or 'SPS Firmware' information screen.Affected if Installed SPS firmware version is below sps_e3_05.00.04.027.0
-
Check BIOS/UEFI firmware versionRun `dmidecode -t bios` or check BIOS setup screen. Look for SPS-related firmware entries in system firmware inventory. Intel SPS may appear as 'SPS Firmware' or 'Intel SPS' in version strings.Affected if BIOS or main system firmware is from an Intel server platform that bundles SPS, and the SPS component version shown is prior to 05.00.04.027.0
-
Verify physical access threat modelConfirm server is in an environment where unauthenticated physical access is possible. Check physical security controls on server room or rack.Affected if Server is physically accessible to unauthorized users and SPS firmware version is vulnerable
A system is affected if it runs Intel Server Platform Services firmware with a version earlier than sps_e3_05.00.04.027.0 and the attacker has physical access to the server.
Generated from the published advisory. Verify against your own configuration.
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 dataUpdate Intel SPS firmware to version SPS_E3_05.00.04.027.0 or later. Restrict physical access to servers hosting vulnerable SPS components and ensure servers are in secured facilities.
- Consultation3.0 h
- Implementation6.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-0099 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2019-0099 in production — separate from our analysis above.
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.
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.
- 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