dbcve.org
Improper Access ControlWeakness · CWE-284

CVE-2023-29164

HIGH · 7.3 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 →
75/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
Improper access control 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 an authenticated 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 · high confidence

This is an improper access control vulnerability in the BMC (Baseboard Management Controller) firmware for multiple Intel server board models. An authenticated user with local access can escalate their privileges due to insufficient access control enforcement in the BMC firmware.

MitigationUpdate the BMC firmware to version 02.01.0017 or later for S2600WF/ST/BP boards, and version R01.01.0009 or later for M50CYP and D50TNP boards. Since local access is required for exploitation, ensure physical access controls are enforced and monitor for unauthorized local access.

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

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:L/I:H/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify the Intel server board model
    Check the server chassis, motherboard label, or use IPMI command 'ipmitool raw 0x06 0x01' or access BMC web interface to view system information. Common affected models include S2600WF, S2600ST, S2600BP, M50CYP, and D50TNP.
    Affected if The server board is one of these models: S2600WF, S2600ST, S2600BP, M50CYP, or D50TNP.
  2. Access the BMC firmware version
    Use IPMI command 'ipmitool mc info' or access the BMC web interface under 'BMC Settings' or 'Firmware Information' to retrieve the current BMC firmware version.
    Affected if The BMC firmware version is returned by the command or interface.
  3. Compare firmware version for S2600WF/ST/BP boards
    If the board is S2600WF, S2600ST, or S2600BP, compare the installed version against 02.01.0017. Versions below 02.01.0017 are affected.
    Affected if Board model is S2600WF/ST/BP AND BMC firmware version is earlier than 02.01.0017.
  4. Compare firmware version for M50CYP and D50TNP boards
    If the board is M50CYP or D50TNP, compare the installed version against R01.01.0009. Versions below R01.01.0009 are affected.
    Affected if Board model is M50CYP or D50TNP AND BMC firmware version is earlier than R01.01.0009.
  5. Verify local access capability exists
    Review physical access controls and user accounts on the BMC. Check for local user accounts configured via IPMI or BMC web interface under 'User Management'.
    Affected if Local user accounts exist on the BMC and physical access to the server is not strictly controlled.

The environment is affected if the Intel server board is an S2600WF/ST/BP model with BMC firmware below 02.01.0017, or an M50CYP/D50TNP model with BMC firmware below R01.01.0009, and local authenticated access is possible.

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 the BMC firmware to version 02.01.0017 or later for S2600WF/ST/BP boards, and version R01.01.0009 or later for M50CYP and D50TNP boards. Since local access is required for exploitation, ensure physical access controls are enforced and monitor for unauthorized local access.

Recommended fix High confidence

Intel Server Board S2600WF/S2600ST/S2600BP to BMC firmware version 02.01.0017 or later; Intel Server Board M50CYP/D50TNP to BMC firmware version R01.01.0009 or later

  1. Identify the exact Intel Server Board model (S2600WF, S2600ST, S2600BP, M50CYP, or D50TNP) from the system label or BIOS/BMC information
  2. Download the latest BMC firmware for the specific board from the Intel Support website (downloadcenter.intel.com) or your system integrator
  3. Review the firmware release notes to confirm version 02.01.0017 (for S2600x family) or R01.01.0009 (for M50CYP/D50TNP) includes the security fix
  4. Follow the standard BMC firmware update procedure: typically requires logging into the BMC web interface or using tools like Intel BMC Utility, IPMItool, or BIOS update utilities
  5. Ensure stable power during the firmware update process - do not interrupt the flashing operation
  6. After update, verify the BMC firmware version reflects the patched release
  7. Confirm the fix by reviewing the BMC security settings and verifying the access control vulnerability is resolved
Caveat BMC firmware updates are generally irreversible; ensure backup of critical configuration and verify hardware compatibility before applying

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

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation3.0 h
  • Testing3.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,150
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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