dbcve.org
OpenbmcOperating system · Intel

CVE-2023-32280

MEDIUM · 5.3 CVSS v3.1 Published 2024-02-14
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
62/100
Remediation priority · Elevated
Remotely reachable No privileges 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
Insufficiently protected credentials in some Intel(R) Server Product OpenBMC firmware before versions egs-1.05 may allow an unauthenticated user to enable information disclosure via network 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

Intel Server Product OpenBMC firmware versions before egs-1.05 contain insufficiently protected credentials, allowing unauthenticated users to potentially disclose sensitive information via network access.

MitigationUpdate OpenBMC firmware to version egs-1.05 or later. Additionally, restrict network access to the BMC management interface to trusted networks until the patch is applied.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
OpenbmcOperating system
Affected:< egs-1.05

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
Low
Integrity
None
Availability
None

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

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

  1. Confirm Intel OpenBMC is in use
    Access the BMC web interface, SSH to the BMC IP, or use ipmitool to identify the BMC firmware. Look for 'OpenBMC' or Intel server platform indicators in the system information.
    Affected if The system uses Intel OpenBMC firmware for baseboard management controller (BMC).
  2. Retrieve the installed BMC firmware version
    Via BMC web interface: navigate to 'System Information' or 'Firmware Update' page. Via command line: run 'ipmitool mc info' or SSH to BMC and run 'cat /etc/os-release' or check '/version' file if available. Via Redfish: GET /redfish/v1/Managers/1/
    Affected if The firmware version displayed is lower than egs-1.05.
  3. Verify network accessibility of the BMC
    Confirm the BMC management interface IP is reachable on the network. Check if the BMC web interface or IPMI ports (623 UDP, 80, 443 TCP) are exposed. Review network configuration to determine if BMC is on a trusted or restricted network.
    Affected if The BMC is network-accessible from untrusted networks, increasing exposure to unauthenticated credential disclosure.
  4. Check for default or weak BMC credentials
    Attempt to access the BMC web interface or IPMI interface using default credentials (e.g., admin/admin, ADMIN/ADMIN). If login succeeds without credential changes, credentials may be insufficiently protected.
    Affected if Default or weak credentials are in use, allowing potential unauthorized access per CVE description.

The environment is affected if Intel OpenBMC firmware version is below egs-1.05 and the BMC management interface is network-accessible.

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 OpenBMC firmware to version egs-1.05 or later. Additionally, restrict network access to the BMC management interface to trusted networks until the patch is applied.

Recommended fix High confidence

egs-1.05

  1. 1. Identify the Intel Server Board or system that is running OpenBMC firmware
  2. 2. Access the BMC management interface (web UI or IPMI)
  3. 3. Navigate to the firmware update or maintenance section
  4. 4. Download the OpenBMC firmware version egs-1.05 or later from Intel's official support website (intel.com)
  5. 5. Upload the firmware image through the BMC interface
  6. 6. Initiate the firmware update process and wait for completion
  7. 7. Verify the installed firmware version after the update
  8. 8. Restart the BMC if prompted or required

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

Fix this in Openbmc Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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