dbcve.org
Out-of-bounds ReadWeakness · CWE-125

CVE-2023-49144

MEDIUM · 6.7 CVSS v3.1 Published 2024-08-14
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
69/100
Remediation priority · Elevated
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
Out of bounds read in OpenBMC Firmware for some Intel(R) Server Platforms before versions egs-1.15-0, bhs-0.27 may allow a privileged user to potentially enable information disclosure 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

An out-of-bounds read vulnerability in OpenBMC firmware on certain Intel Server Platforms allows a privileged local user to read sensitive information from memory locations outside allocated buffers, potentially exposing system data.

MitigationUpdate OpenBMC firmware to versions egs-1.15-0, bhs-0.27 or later on affected Intel server platforms to remediate the vulnerability.

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

CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:C/C:H/I:L/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 OpenBMC firmware presence
    Check system documentation or BMC web interface for OpenBMC firmware identification. Run 'bmcweb --version' or check /etc/os-release if accessible via BMC console.
    Affected if The system does not run OpenBMC firmware, then the vulnerability does not apply
  2. Determine OpenBMC version
    Access BMC console (e.g., via IPMI or web UI) and retrieve firmware version information. Common commands: 'ipmitool mc info' or check BMC web interface firmware version display.
    Affected if Unable to retrieve version information or version predates the fixed releases (egs-1.15-0, bhs-0.27 and later)
  3. Confirm Intel Server Platform
    Verify the hardware platform is an Intel Server Platform by checking system inventory or BMC platform information: 'ipmitool fru print' or check server model via 'dmidecode' if accessible.
    Affected if System is not an Intel Server Platform, then this specific OpenBMC vulnerability does not apply
  4. Compare against fixed versions
    Compare your installed OpenBMC version against known fixed releases egs-1.15-0 and bhs-0.27 (and later versions). If version is lower than these fixed releases, the system may be vulnerable.
    Affected if Installed OpenBMC version is older than egs-1.15-0 or bhs-0.27, indicating potential vulnerability to out-of-bounds read

System is affected if it runs OpenBMC firmware on an Intel Server Platform with a version prior to egs-1.15-0 or bhs-0.27.

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 versions egs-1.15-0, bhs-0.27 or later on affected Intel server platforms to remediate the vulnerability.

Recommended fix Moderate confidence

OpenBMC Firmware egs-1.15-0 or bhs-0.27 (depending on platform series)

  1. Identify the specific Intel Server Platform model and current OpenBMC firmware version using the BMC web interface or IPMI command: `ipmi-fru` or `ipmi-dcmi get asset`
  2. Navigate to the Intel support website (www.intel.com) and locate the firmware download section for your specific server platform
  3. Download the OpenBMC firmware update package for version egs-1.15-0 or bhs-0.27 (depending on your platform series)
  4. Review the firmware update instructions provided by Intel for your specific platform
  5. Apply the firmware update via the BMC web interface, Redfish API, or IPMI command as documented in the platform-specific firmware update guide
  6. Verify the firmware version has been successfully updated after the update process completes
Caveat Firmware updates carry inherent risks; ensure power stability and follow Intel's update procedures to avoid bricking the BMC

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

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA2.0 h
20.0 hours of engineering $3,500
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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