dbcve.org
Megarac Sp XOperating system · Ami

CVE-2023-37293

HIGH · 8.8 CVSS v3.1 Published 2024-01-09
Fix available
A fix is available. Upgrade to 12.7 / 13.6 or later.
See remediation →
93/100
Remediation priority · Urgent
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’s SPx contains a vulnerability in the BMC where an Attacker may cause a stack-based buffer overflow via an adjacent network. A successful exploitation of this vulnerability may lead to a loss of confidentiality, integrity, and/or availability.

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 SPx Baseboard Management Controller (BMC) firmware contains a stack-based buffer overflow vulnerability that can be exploited by an attacker with adjacent network access to the BMC's network interface, potentially allowing remote code execution and complete compromise of the BMC.

MitigationApply the vendor-supplied firmware patch for SPx when available. Until then, restrict BMC network access to trusted management networks, disable unnecessary management protocols, and monitor for indicators of compromise.

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 XOperating system
Affected:>= 12, < 12.7>= 13, < 13.6

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
Adjacent
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:A/AC:L/PR:N/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 product
    Access the BMC web interface or use IPMI commands to retrieve the firmware product name (check system information or firmware details page)
    Affected if Product is not Ami Megarac Sp X - not affected
  2. Check BMC firmware version
    Retrieve the exact firmware version number from the BMC web interface system information page or via IPMI command (such as 'ipmiutil ver' or 'ipmiutil fru')
    Affected if Version is 12.x where x is less than 7, OR version is 13.x where x is less than 6 - version falls within affected range
  3. Assess BMC network exposure
    Review network configuration to determine if the BMC management interface is accessible from untrusted or adjacent networks (check IP address assignment, subnet, firewall rules, and VLAN configuration)
    Affected if BMC is directly accessible from untrusted adjacent network segments - exploitation is possible
  4. Review management protocols
    Check BMC settings for enabled management protocols (HTTP, HTTPS, SSH, IPMI, Redfish, SNMP) and identify which are active
    Affected if Multiple management protocols are enabled and accessible - attack surface exists if BMC is network-exposed

System is affected if it uses Ami Megarac Sp X firmware versions 12.x (before 12.7) or 13.x (before 13.6) and the BMC network interface is reachable from adjacent networks

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.6 or later
Fixed in 12.713.6
Interim mitigation

Apply the vendor-supplied firmware patch for SPx when available. Until then, restrict BMC network access to trusted management networks, disable unnecessary management protocols, and monitor for indicators of compromise.

Recommended fix High confidence

Megarac SP X version 12.7 or later (for 12.x branch); Megarac SP X version 13.6 or later (for 13.x branch)

  1. 1. Identify the current installed version of Megarac SP X by accessing the BMC web interface or using IPMI commands.
  2. 2. If running version 12.x (>=12 and <12.7): Plan to upgrade to version 12.7 or later.
  3. 3. If running version 13.x (>=13 and <13.6): Plan to upgrade to version 13.6 or later.
  4. 4. Download the appropriate firmware update from the vendor's support site.
  5. 5. Apply the firmware update following the vendor's standard BMC firmware update procedure (typically via the BMC web interface or firmware update tool).
  6. 6. After update completion, verify the new firmware version is installed and the BMC is operational.
Caveat Review vendor release notes for any potential compatibility issues or known issues with the new firmware version before upgrading

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
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
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,120.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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