CVE-2023-4857
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 · uneditedAn authentication bypass vulnerability was identified in SMM/SMM2 and FPC that could allow an authenticated user to execute certain IPMI calls that could lead to exposure of limited system information.
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 confidenceAn authentication bypass vulnerability in SMM/SMM2 and FPC (Flexible Port Controller) components allows authenticated users to execute certain IPMI calls that could expose limited system information. This affects the out-of-band management interface used for remote server hardware control.
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
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
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.
-
Confirm IPMI/BMC management interface is in useCheck if the server has an active out-of-band management interface (IPMI, iLO, iDRAC, IMM, etc.) by reviewing hardware documentation or checking for BMC network listeners on ports 623/664Affected if IPMI/BMC interface is enabled and accessible on the network
-
Identify SMM/SMM2 or FPC component versionsAccess the BMC web interface or use IPMI commands (e.g., 'ipmitool -I lanplus -H <bmc_ip> -U <user> -P <pass> raw commands) to query firmware versions for Server Management Module (SMM/SMM2) or Flexible Port Controller (FPC) componentsAffected if SMM/SMM2 or FPC firmware version cannot be verified or is unknown/unpatched
-
Verify IPMI user access controlsList IPMI users with 'ipmitool -I lanplus -H <bmc_ip> -U <admin> -P <pass> user list' and review which users have operator/administrator privilegesAffected if Multiple authenticated users exist with IPMI access beyond what is strictly required
-
Check for unauthorized IPMI command executionReview BMC/IPMI event logs for any unexpected or anomalous IPMI commands executed, using 'ipmitool -I lanplus -H <bmc_ip> -U <admin> -P <pass> sel list'Affected if Unfamiliar IPMI commands appear in system event logs
-
Assess network isolation of management interfaceVerify the BMC IP address is on an isolated management network VLAN, not directly exposed on production or public networksAffected if BMC management interface is accessible from untrusted network segments
Environment is affected if SMM/SMM2 or FPC components with an IPMI management interface are present and the firmware version cannot be confirmed as patched or the management interface is accessible from untrusted networks.
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 dataApply vendor-provided firmware updates for SMM/SMM2 and FPC components. Review IPMI access controls and ensure management interfaces are on isolated networks.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-4857 — 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-4857 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