dbcve.org
Megarac Sp XApplication · Ami

CVE-2023-34343

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 through the API, potentially achieving code execution, denial of service, information disclosure, or data tampering.

MitigationApply vendor-supplied firmware patch for AMI BMC SPX systems; until patch available, restrict API access to trusted networks/accounts and monitor for suspicious API activity.

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
    Locate the Baseboard Management Controller (BMC) firmware information through the BMC web interface, IPMI command, or system information page. Confirm the product is Ami Megarac Sp X.
    Affected if The product is not Ami Megarac Sp X, then this CVE does not apply.
  2. Determine the installed firmware version
    Retrieve the current BMC firmware version from the system info or version display within the BMC interface or via IPMI command. Compare your version number against the affected ranges: 12.0 through 12.6.x, and 13.0 through 13.4.x.
    Affected if The installed version falls within 12.0 to less than 12.7, or within 13.0 to less than 13.5, then the system is in an affected version range.
  3. Verify SPX REST API is enabled
    Check the BMC configuration or feature settings to determine if the SPX REST API service is currently enabled or accessible on the system.
    Affected if The SPX REST API is enabled and accessible, then this vulnerability is potentially exploitable.
  4. Review API user accounts and privileges
    Examine the BMC user account configuration to identify accounts that have API access or elevated privileges permitted to use the SPX REST API endpoints.
    Affected if There are user accounts configured with API access privileges, then an authenticated attacker could potentially exploit this vulnerability.

A system is affected if it is running Ami Megarac Sp X firmware in version 12.0-12.6.x or 13.0-13.4.x, has the SPX REST API enabled, and contains user accounts with API access privileges.

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 patch for AMI BMC SPX systems; until patch available, restrict API access to trusted networks/accounts and monitor for suspicious API activity.

Recommended fix Moderate confidence

Megarac SPX firmware version 12.7 or later (for 12.x branch); version 13.5 or later (for 13.x branch)

  1. 1. Identify the current Megarac SPX firmware version by accessing the BMC web interface or using IPMI commands
  2. 2. Download the appropriate fixed firmware version (12.7 or later for 12.x branch, 13.5 or later for 13.x branch) from the official MegaRAC vendor support portal
  3. 3. Verify the firmware integrity using checksums provided by the vendor
  4. 4. Access the BMC firmware update interface (typically found under Maintenance or Firmware Update in the web UI)
  5. 5. Upload and apply the firmware update. This process may take several minutes and will automatically reboot the BMC
  6. 6. After the update completes, verify the new firmware version is installed correctly
  7. 7. Validate that the SPX REST API functions normally with the updated version
Caveat Firmware updates to BMC/Baseboard Management Controllers can occasionally cause temporary service interruption; ensure appropriate change management procedures are followed and have a rollback plan

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

Fix this in Megarac Sp X Scoped from the published advisory
  • Consultation8.0 h
  • Implementation12.0 h
  • Testing8.0 h
  • Review / QA4.0 h
32.0 hours of engineering $5,680
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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