dbcve.org
Megarac Sp XApplication · Ami

CVE-2023-34336

HIGH · 8.8 CVSS v3.1 Published 2023-06-12
Fix available
A fix is available. Upgrade to 12.7 / 13.5 or later.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable 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 attacker with the required privileges can cause a buffer overflow, which may lead to code execution, denial of service, or escalation of privileges.  

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

Buffer overflow vulnerability in the IPMI handler of AMI BMC firmware allows an authenticated attacker with required privileges to overflow a buffer, potentially achieving code execution, denial of service, or privilege escalation.

MitigationApply vendor-supplied firmware patches from AMI through the BMC vendor; restrict network access to the IPMI/BMC management interface to trusted networks until patched.

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 Sp XApplication
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
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/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 firmware version
    Use IPMI command 'mc info' via ipmitool (e.g., ipmitool -I lanplus -H <bmc_host> -U <admin> -P <password> mc info) or query the BMC via Redfish API endpoint /redfish/v1/Managers/Self to retrieve the firmware version string
    Affected if Version is not displayed or inaccessible - the system may not be an AMI BMC
  2. Confirm product is Ami Megarac SP X
    Locate the firmware version string from step 1 and verify it corresponds to the Ami Megarac SP X product line; this may be visible in the mc info output or BMC web interface under firmware information
    Affected if The BMC firmware is not from the Ami Megarac SP X product line
  3. Compare installed version to affected ranges
    Parse the firmware version number from step 1 and compare against: 12.0 <= version < 12.7 OR 13.0 <= version < 13.5
    Affected if The installed version falls within either of the two affected ranges (12.x before 12.7 or 13.x before 13.5)
  4. Verify IPMI handler is accessible
    Confirm the IPMI over LAN (IPMI handler) interface is enabled and network-accessible; check BMC configuration for IPMI over LAN status or attempt a connection to port 623/UDP
    Affected if IPMI interface is enabled and reachable - the vulnerability requires interaction with the IPMI handler

If the BMC runs Ami Megarac SP X firmware versions 12.0-12.6 or 13.0-13.4 with IPMI over LAN enabled, the environment is affected by this vulnerability.

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-supplied firmware patches from AMI through the BMC vendor; restrict network access to the IPMI/BMC management interface to trusted networks until patched.

Recommended fix Moderate confidence

Megarac SP X version 12.7 or later (for 12.x line); version 13.5 or later (for 13.x line)

  1. 1. Identify the current installed version of Megarac SP X by checking the BMC firmware version through the web interface or IPMI.
  2. 2. If current version is >= 12.0 and < 12.7, plan upgrade to version 12.7 or later in the 12.x stable release line.
  3. 3. If current version is >= 13.0 and < 13.5, plan upgrade to version 13.5 or later in the 13.x stable release line.
  4. 4. Obtain the firmware update from the vendor's official support portal or through your authorized support channel.
  5. 5. Follow vendor procedures to apply the BMC firmware update, which typically involves uploading the firmware through the BMC web interface or using the flashutil command via IPMI.
  6. 6. After update completion, verify the new firmware version is >= 12.7 or >= 13.5 as applicable.
  7. 7. Validate that IPMI functionality continues to work properly after the update.

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

Fix this in Megarac Sp X 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 the upgrade done

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-34336 — 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-34336 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