Safeguard
Vulnerability Analysis•

CVE-2023-31189: Medium Auth Flaw in Intel OpenBMC Firmware

CVE-2023-31189 is a medium (CVSS 5.2) improper authentication flaw in Intel server OpenBMC firmware before egs-1.09. Update the firmware as Intel advises.

Safeguard Security Team
3 min read

CVE-2023-31189 is a medium severity improper authentication flaw, scored 5.2, in some Intel server product OpenBMC firmware before version egs-1.09. An authenticated local user may escalate privileges. Intel advisory INTEL-SA-00922 covers it, so update the BMC firmware to egs-1.09 or later.

What's affected

The NVD record says improper authentication (CWE-287) in some Intel Server Product OpenBMC firmware before version egs-1.09 may allow an authenticated user to enable escalation of privilege through local access. The record is dated 2024-02-14 and the vector is CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:N.

The record's product list names the OpenBMC firmware and three Intel Xeon models: Bronze 3408U, Gold 5403N and Gold 5411N. That list is what NVD matched, not necessarily every platform Intel covers. Intel's advisory page was not retrievable when this post was prepared, because it returned an access error to an automated request. Read INTEL-SA-00922 directly for the exact list of affected products and for the fixed version for your board.

The fixed version, taken from the record description, is egs-1.09. If the advisory names a different build for your platform, follow the advisory.

How to check if you're exposed

A baseboard management controller has its own firmware, separate from the BIOS and the operating system. Find the version in the BMC web interface or through your server vendor's management tool, and compare it with egs-1.09.

If you buy servers from an OEM, the OEM often repackages Intel's firmware under its own version numbers. In that case use the OEM's security notice to map its release to Intel's fix. Check the Intel advisory for any listed mitigations and steps.

Also list who can log in to the BMC and to the host at an authenticated level, because the flaw needs a login to start.

What to do now

  1. Inventory servers with an OpenBMC based management controller and record the BMC firmware version.
  2. Read INTEL-SA-00922 and the notice from your server vendor.
  3. Schedule the firmware update to egs-1.09 or later during a maintenance window, since BMC updates can involve a controller restart.
  4. Keep BMC network ports on an isolated management network, not on the general or public network.
  5. Review BMC accounts and remove ones that are unused.

Why it matters

The class is CWE-287, where a check that should prove who a caller is does not do its job fully. Here the attacker must already hold a login and local access, which is why the score is medium.

Even so, the controller sits below the operating system. A flaw that raises privileges on it matters more than its number suggests, because the BMC can power cycle hosts and mount media. The scope flag in the vector is changed, meaning impact can reach beyond the component itself. Firmware like this rarely shows up in a dependency scan, so keep a hardware and firmware list next to your software inventory.

Quick check

Is there a confirmed fix?

Per the record, the issue affects firmware before egs-1.09, so egs-1.09 or later is the fixed line. Confirm the exact build for your platform in Intel advisory INTEL-SA-00922.

Can someone exploit this from the internet?

The vector is local access (AV:L) with a low privilege login, so it is not described as remotely exploitable. Keep BMC interfaces off untrusted networks anyway.

Sources

Last reviewed: 19 October 2026.

Never miss an update

Weekly insights on software supply chain security, delivered to your inbox.

We email you a link to confirm, and only then add you to the list. Unsubscribe in one click. Privacy

Self-healing security runs on Safeguard.

Your first fix PR is minutes away.

No sales call required, even your agent can complete the purchase over MCP.