dbcve.org
Megarac Sp XApplication · Ami

CVE-2023-34341

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 SPX REST API, where an attacker with the required privileges can read and write to arbitrary locations within the memory context of the IPMI server process, which may lead to code execution, denial of service, information disclosure, or data tampering.

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 firmware contains a memory corruption vulnerability in the SPX REST API component. An authenticated attacker with the required privileges can perform arbitrary memory read/write operations within the IPMI server process context, enabling code execution, DoS, information disclosure, or data manipulation.

MitigationApply vendor-supplied BMC firmware patches from AMI to address the SPX REST API vulnerability. Restrict access to privileged management interfaces and follow least-privilege principles for IPMI/BMC user accounts.

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 the BMC firmware version
    Access the BMC web interface and navigate to the Firmware Information or Settings page, or use IPMI command: ipmitool -I lanplus -H <bmc_ip> -U <user> -P <pass> fru print, or use Redfish: GET /redfish/v1/Managers/1/Attributes
    Affected if The firmware version matches Ami Megarac Sp X in versions 12.0 to 12.6, or 13.0 to 13.4
  2. Confirm the product is Ami Megarac Sp X
    Check the BMC firmware information for the product name or vendor identification. This may be visible in the web interface header, in IPMI fru data, or via Redfish at /redfish/v1/Managers/1
    Affected if The product is identified as Ami Megarac Sp X (or SPX) and the version falls within the affected ranges
  3. Determine if the SPX REST API is accessible
    Attempt to reach the REST API endpoint on the BMC, typically at https://<bmc_ip>/api/spx or /api, or check via Redfish: GET /redfish/v1. Check if HTTP/HTTPS ports for the API are listening
    Affected if The SPX REST API endpoints respond to requests, indicating the component is enabled and exposed
  4. Review privileged IPMI/BMC user accounts
    List all configured BMC users with administrative or operator privileges using: ipmitool -I lanplus -H <bmc_ip> -U <user> -P <pass> user list, or via Redfish: GET /redfish/v1/Managers/1/Accounts
    Affected if There are user accounts with administrative or elevated privileges configured, which would satisfy the authentication requirement for exploitation

The environment is affected if the BMC runs Ami Megarac Sp X firmware version 12.0 through 12.6 or 13.0 through 13.4, and the SPX REST API component is enabled and accessible to authenticated privileged users.

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 BMC firmware patches from AMI to address the SPX REST API vulnerability. Restrict access to privileged management interfaces and follow least-privilege principles for IPMI/BMC user accounts.

Recommended fix Moderate confidence

MegaRAC SPX firmware 12.7 or later (12.x branch); 13.5 or later (13.x branch)

  1. Obtain the fixed firmware version from MegaRAC vendor (12.7 or later for the 12.x branch, 13.5 or later for the 13.x branch)
  2. Access the BMC web interface or use IPMI tooling to navigate to the firmware update section
  3. Upload the new firmware image file
  4. Apply the firmware update and allow the BMC to reboot
  5. Verify the firmware version has been updated to a fixed release
  6. Confirm the SPX REST API vulnerability is resolved through testing or vendor verification
Caveat Firmware updates may cause brief downtime; ensure proper backup of BMC configuration and verify hardware compatibility before applying

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 / QA4.0 h
22.0 hours of engineering $3,860
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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