dbcve.org
Megarac SpxApplication · Ami

CVE-2023-34335

CRITICAL · 9.1 CVSS v3.1 Published 2023-06-12
Fix available
A fix is available. Upgrade to 12.7 / 13.5 or later.
See remediation →
100/100
Remediation priority · Urgent
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
AMI BMC contains a vulnerability in the IPMI handler, where an unauthenticated host is allowed to write to a host SPI flash, bypassing secure boot protections. An exploitation of this vulnerability may lead to a loss of integrity or denial of service.  

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

AMI BMC contains a vulnerability in the IPMI handler where an unauthenticated remote host can write to host SPI flash, bypassing secure boot protections. This allows attackers to modify firmware content, potentially植入恶意代码或完全绕过启动链验证。

MitigationApply vendor-provided BMC firmware patches to address the IPMI handler vulnerability. After patching, verify secure boot protections are properly enforced and consider network segmentation to limit IPMI exposure.

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
Megarac SpxApplication
Affected:>= 12.0, < 12.7>= 13.0, < 13.5

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/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. Identify BMC software vendor and product
    Access BMC web interface or run 'ipmitool -I open mc info' to identify the BMC firmware vendor and product name. Look for 'Ami Megarac SPX' or similar AMI BMC software.
    Affected if The BMC software is not Ami Megarac SPx, then this CVE does not apply.
  2. Check installed BMC firmware version
    Run 'ipmitool -I lanplus -H <BMC_IP> -U admin -P admin mc info' or check the firmware version in the BMC web interface under 'Firmware Information' or 'BMC Information'.
    Affected if Version is >= 12.0 and < 12.7, OR >= 13.0 and < 13.5.
  3. Determine if IPMI over LAN is enabled
    Run 'ipmitool -I lanplus -H <BMC_IP> -U admin -P admin raw 0x30 0x70 0x0c 0x00' to check IPMI over LAN status, or check 'IPMI over LAN' setting in BMC web interface under 'IPMI Settings' or 'Network Settings'.
    Affected if IPMI over LAN is enabled and the BMC is network-accessible.
  4. Verify BMC network exposure
    Check if the BMC management port is accessible from untrusted networks. Review network firewall rules, VLAN segmentation, and ACLs restricting access to the BMC IP address on ports 623 (UDP) for IPMI.
    Affected if BMC is reachable from untrusted network segments without proper access controls.

Environment is affected if the BMC runs Ami Megarac SPx firmware versions 12.0-12.6 or 13.0-13.4 AND IPMI over LAN is enabled with the BMC exposed to accessible network segments.

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 12.7 / 13.5 or later
Fixed in 12.713.5
Interim mitigation

Apply vendor-provided BMC firmware patches to address the IPMI handler vulnerability. After patching, verify secure boot protections are properly enforced and consider network segmentation to limit IPMI exposure.

Recommended fix High confidence

Megarac SPX 12.7 or later; Megarac SPX 13.5 or later

  1. Identify the current Megarac SPX firmware version running on the BMC using the BMC web interface or IPMI commands
  2. If running version 12.0-12.6, upgrade to version 12.7 or later
  3. If running version 13.0-13.4, upgrade to version 13.5 or later
  4. Obtain the firmware from the vendor (AMI/Megarac) through official channels or the BMC vendor support portal
  5. Upload and apply the firmware update through the BMC web interface or IPMI firmware update commands
  6. Verify the upgrade was successful by checking the new firmware version
  7. After upgrade, verify that IPMI handler now properly authenticates before allowing SPI flash write operations
Caveat Firmware updates to BMC typically require a reboot of the BMC; ensure proper maintenance window and verify compatibility with host system

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

Fix this in Megarac Spx Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing6.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,980
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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