dbcve.org
OpenbmcApplication · Openbmc Project

CVE-2022-35729

HIGH · 7.5 CVSS v3.1 Published 2023-02-16
Fix available
A fix is available. Upgrade to 0.72 or later.
See remediation →
84/100
Remediation priority · High
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
Out of bounds read in firmware for OpenBMC in some Intel(R) platforms before version 0.72 may allow unauthenticated user to potentially enable denial of service 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 · high confidence

Out-of-bounds read vulnerability in OpenBMC firmware on Intel platforms before version 0.72 allows unauthenticated remote attackers to potentially cause denial of service via network access by reading beyond allocated memory boundaries.

MitigationUpgrade OpenBMC firmware to version 0.72 or later on all affected Intel platforms. If immediate patching is not possible, restrict network access to the BMC management interfaces.

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
OpenbmcApplication
Affected:< 0.72

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/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. Confirm OpenBMC is in use on an Intel platform
    Check the BMC web interface footer, or run 'cat /etc/os-release' or 'obmcutil --property /org/openbmc/control/system0/field_replaceable' via IPMI to identify the BMC firmware and platform type.
    Affected if The system uses OpenBMC firmware on Intel hardware.
  2. Determine the installed OpenBMC version
    Access the BMC web interface and look at the version information in the footer or system status page, or run 'obmcutil --property /org/openbmc/inventory/system/chassis/misc/field_mode' via IPMI to retrieve the firmware version string.
    Affected if The installed version is below 0.72.
  3. Verify if BMC network management interfaces are accessible
    Check if the BMC IP address is reachable on the network and port 443 or 80 is open. Use 'ipmitool lan print 1' or similar tools to confirm the BMC has an active network configuration with an assigned IP address.
    Affected if The BMC management interface is network-accessible and the version is below 0.72.

The environment is affected if OpenBMC firmware version is below 0.72 on an Intel platform and the BMC network management interface is accessible to unauthenticated attackers.

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
Upgrade available Upgrade to 0.72 or later
Fixed in 0.72
Interim mitigation

Upgrade OpenBMC firmware to version 0.72 or later on all affected Intel platforms. If immediate patching is not possible, restrict network access to the BMC management interfaces.

Recommended fix Moderate confidence

OpenBMC 0.72

  1. Verify current OpenBMC version using the BMC web interface or via IPMI command: ipmitool mc info
  2. Download the OpenBMC 0.72 firmware image from Intel's official support website for your specific Intel platform
  3. Follow Intel's standard BMC firmware update procedure for your platform, typically using the BMC web interface (Firmware Update > Upload and Activate)
  4. Alternatively, use the command line: ipmitool -H <bmc_ip> -U admin -P <password> firmware upload <path_to_firmware>
  5. After update, verify the BMC is running version 0.72 using: ipmitool mc info or via the web interface
  6. Restart the BMC and host system as recommended by the update process to ensure all components are running with the new firmware

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

Fix this in Openbmc Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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