dbcve.org
Heap-based Buffer OverflowWeakness · CWE-122

CVE-2023-31276

HIGH · 8.2 CVSS v3.1 Published 2025-02-12
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
84/100
Remediation priority · High
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
Heap-based buffer overflow in BMC Firmware for the Intel(R) Server Board S2600WF, Intel(R) Server Board S2600ST, Intel(R) Server Board S2600BP, before version 02.01.0017 and Intel(R) Server Board M50CYP and Intel(R) Server Board D50TNP before version R01.01.0009 may allow a privileged user to 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 · moderate confidence

Heap-based buffer overflow vulnerability in BMC (Baseboard Management Controller) firmware affecting Intel server boards S2600WF, S2600ST, S2600BP (versions before 02.01.0017) and M50CYP, D50TNP (versions before R01.01.0009). A privileged local user can exploit this memory corruption flaw to escalate privileges.

MitigationUpdate BMC firmware to version 02.01.0017 or later for S2600-series boards, and R01.01.0009 or later for M50CYP/D50TNP boards. Restrict local access to only necessary personnel and follow least-privilege principles.

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
Local
Complexity
Low
Privileges
High
User interaction
None
Scope
Changed
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:C/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 the server board model
    Check the server board model via IPMI: `ipmitool fru print` or check the system label/serial number. Look for model numbers S2600WF, S2600ST, S2600BP, M50CYP, or D50TNP.
    Affected if The board model is one of S2600WF, S2600ST, S2600BP, M50CYP, or D50TNP.
  2. Retrieve the BMC firmware version
    Run `ipmitool mc info` or access the BMC web interface to view the firmware version. Record the firmware revision number displayed.
    Affected if A BMC firmware version is returned from the command or interface.
  3. Compare version for S2600-series boards
    If the board is S2600WF, S2600ST, or S2600BP, compare the firmware version to 02.01.0017. Versions before 02.01.0017 are affected.
    Affected if Board is S2600WF, S2600ST, or S2600BP AND firmware version is earlier than 02.01.0017.
  4. Compare version for M50CYP/D50TNP boards
    If the board is M50CYP or D50TNP, compare the firmware version to R01.01.0009. Versions before R01.01.0009 are affected.
    Affected if Board is M50CYP or D50TNP AND firmware version is earlier than R01.01.0009.

A system is affected if it is an Intel S2600WF/ST/BP or M50CYP/D50TNP board running BMC firmware versions before 02.01.0017 or R01.01.0009 respectively.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update BMC firmware to version 02.01.0017 or later for S2600-series boards, and R01.01.0009 or later for M50CYP/D50TNP boards. Restrict local access to only necessary personnel and follow least-privilege principles.

Recommended fix High confidence

Intel Server Board S2600WF/S2600ST/S2600BP: BMC Firmware version 02.01.0017; Intel Server Board M50CYP/D50TNP: BMC Firmware version R01.01.0009

  1. Identify the current BMC firmware version on the affected Intel Server Board via the BMC web interface or IPMI command
  2. Navigate to Intel's support website and locate the BMC firmware download page for your specific server board model (S2600WF, S2600ST, S2600BP, M50CYP, or D50TNP)
  3. Download the BMC firmware update package version 02.01.0017 (for S2600WF/ST/BP) or version R01.01.0009 (for M50CYP/D50TNP)
  4. Review the firmware update instructions in the accompanying readme or release notes
  5. Apply the firmware update through the BMC web interface (Firmware Update section) or using Intel Deployment Toolkit/IPMI firmware update commands
  6. After updating, verify the new firmware version is correctly installed and the BMC is operational
  7. Restart the BMC if not automatically done by the update process
Caveat Firmware updates carry inherent risk of rendering the device inoperable if interrupted; ensure stable power and follow Intel's update procedure exactly

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,480
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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