dbcve.org
Megarac Sp XApplication · Ami

CVE-2023-34334

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 inject arbitrary shell commands, 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 · moderate confidence

AMI BMC contains a command injection vulnerability in the SPX REST API where an authenticated attacker with required privileges can inject arbitrary shell commands, potentially leading to code execution, denial of service, information disclosure, or data tampering.

MitigationApply the vendor-supplied firmware patch for the AMI BMC when available. Until then, restrict network access to the BMC management interface and enforce least-privilege access controls for the SPX REST API.

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 product
    Query the BMC for product identification - typically via IPMI command, web UI, or REST API endpoint such as /api/session or /api/system to retrieve the product name and firmware version
    Affected if The product is not Ami Megarac Sp X (or SPX)
  2. Check installed firmware version
    Retrieve the BMC firmware version through the web interface, IPMI command (e.g., ipmitool -I lanplus -H <bmc_ip> -U <user> -P <pass> mc info), or REST API endpoint that exposes version information
    Affected if Version is >= 12.0 and < 12.7, OR >= 13.0 and < 13.5
  3. Verify SPX REST API is accessible
    Attempt to reach the SPX REST API endpoints (typically at /api or /redfish/v1) on the BMC management interface over HTTPS/HTTP
    Affected if The SPX REST API endpoint responds and is network-accessible
  4. Confirm authentication configuration
    Review BMC user privileges and confirm whether accounts with REST API access exist - the vulnerability requires an authenticated attacker with required privileges to exploit the command injection
    Affected if There are user accounts configured with REST API access privileges

A user is affected if the BMC runs Ami Megarac Sp X with firmware version in the ranges 12.0-12.6 or 13.0-13.4, and the SPX REST API is accessible with valid authentication credentials.

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 the vendor-supplied firmware patch for the AMI BMC when available. Until then, restrict network access to the BMC management interface and enforce least-privilege access controls for the SPX REST API.

Recommended fix Moderate confidence

Upgrade to Megarac SP X version 12.7 (for 12.x branch) or version 13.5 (for 13.x branch) or later

  1. Identify the current version of Megarac SP X by checking the BMC firmware version through the web interface or API
  2. If running version 12.0 <= version < 12.7, upgrade the firmware to version 12.7 or later (preferably latest 12.x stable release)
  3. If running version 13.0 <= version < 13.5, upgrade the firmware to version 13.5 or later (preferably latest 13.x stable release)
  4. After upgrade, verify the new version is running and confirm the vulnerability is resolved
  5. Restrict API access to trusted users only, as the vulnerability requires authenticated privileges
Caveat Review release notes for any breaking changes between current and target version; test upgrade in staging environment first if possible

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