CVE-2023-35191
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 · uneditedUncontrolled resource consumption for some Intel(R) SPS firmware versions may allow a privileged user to potentially enable denial of service via network 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 · moderate confidenceIntel Server Platform Services (SPS) firmware contains an uncontrolled resource consumption vulnerability that allows a privileged user to exhaust system resources via network access, leading to denial of service. The vulnerability stems from insufficient resource limit enforcement in the SPS firmware when processing network requests from authenticated privileged users.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
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
- Network
- Complexity
- Low
- Privileges
- High
- User interaction
- None
- Scope
- Changed
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/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 checksWork through these to decide whether this CVE applies to you.
-
Identify if Intel SPS firmware is presentCheck system firmware/inventory for Intel Server Platform Services (SPS) firmware module. On Intel servers, this can often be found via BMC/IPMI interfaces, BIOS setup, or by running: 'dmidecode -t bios' or checking BMC firmware inventoryAffected if SPS firmware is present on the system
-
Determine SPS firmware versionAccess the BMC/IPMI interface or Intel System Management Software to retrieve the installed SPS firmware version number. Consult Intel's security advisory for the specific fixed versionAffected if Installed SPS version is older than the fixed version listed in Intel's security advisory
-
Verify network access to SPS management interfaceCheck if the BMC/IPMI network interface is enabled and accessible. Review network configuration for the management port: 'ipmitool lan print' or check BMC web interface network settingsAffected if BMC network interface is enabled and the SPS management plane is accessible over the network
-
Confirm privileged user accounts existReview BMC/IPMI user accounts to determine if privileged administrative users are configured. Use: 'ipmitool user list' or check BMC user managementAffected if One or more privileged (administrator-level) BMC users are configured
If Intel SPS firmware is present, the installed version is unpatched, the BMC network interface is accessible, and privileged users exist, the system is vulnerable to resource exhaustion via network requests from those privileged users.
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 a version that addresses the uncontrolled resource consumption as specified in Intel's official security advisory. Prioritize patching systems exposed to network access.
- Consultation3.0 h
- Implementation4.0 h
- Testing2.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,168.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-35191 — 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-2023-35191 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