CVE-2023-4855
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 · uneditedA command injection vulnerability was identified in SMM/SMM2 and FPC that could allow an authenticated user with elevated privileges to execute unauthorized commands via IPMI.
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 confidenceCommand injection vulnerability in SMM/SMM2 and FPC components allows an authenticated user with elevated privileges to execute unauthorized arbitrary commands through the IPMI (Intelligent Platform Management Interface) interface.
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
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/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 checksWork through these to decide whether this CVE applies to you.
-
Verify IPMI interface is enabledCheck the baseboard management controller (BMC) configuration via IPMItool: 'ipmitool mc info' or check BIOS/UEFI settings for IPMI/KVM/Redfish enablement statusAffected if IPMI interface is active and network-accessible
-
Identify SMM/SMM2 firmware versionQuery the BMC for SMM module information using IPMI commands such as 'ipmitool raw' or check vendor management console for Service Processor/SMM firmware versionAffected if SMM or SMM2 firmware version matches the vulnerable version range (compare against vendor advisories)
-
Identify FPC firmware versionQuery the BMC for FPC (Front Panel Controller) firmware version via IPMItool: 'ipmitool fru print' or check vendor management interface for FPC component versionAffected if FPC firmware version matches the vulnerable version range (compare against vendor advisories)
-
Check IPMI user privilegesReview IPMI user list and privilege levels using 'ipmitool user list' or BMC web interface to identify users with ADMINISTRATOR or elevated privilegesAffected if Multiple users exist with elevated (privilege level 4 or higher) IPMI access
-
Confirm network exposure of IPMIReview firewall rules and network segmentation for UDP/TCP ports 623 (IPMI) and 664 (RMCP+) to determine if IPMI is exposed beyond trusted management networkAffected if IPMI is accessible from untrusted network segments or the internet
Your environment is affected if IPMI is enabled and you have SMM/SMM2 or FPC firmware versions that match the vulnerable ranges specified in vendor security advisories for this CVE.
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 dataRestrict IPMI access to trusted administrative users only, disable unnecessary IPMI functionality, and apply vendor-supplied firmware patches for SMM/SMM2 and FPC when available.
- 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-2023-4855 — 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-4855 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