dbcve.org
Megarac Sp XOperating system · Ami

CVE-2023-34332

HIGH · 7.8 CVSS v3.1 Published 2024-01-09
Fix available
A fix is available. Upgrade to 12.7 / 13.6 or later.
See remediation →
80/100
Remediation priority · High
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 an untrusted pointer to dereference by a local 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 · high confidence

AMI SPx contains an untrusted pointer dereference vulnerability in the Baseboard Management Controller (BMC) firmware that can be exploited by an attacker on the local network. Successful exploitation allows the attacker to potentially compromise confidentiality, integrity, and availability of the affected system.

MitigationApply the vendor-supplied firmware update for AMI SPx BMC to patch the untrusted pointer dereference vulnerability. Verify BMC functionality and IPMI/SOL access after patching.

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

CVSS:3.1/AV:L/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 type
    Run 'ipmitool -I openmcpi mc info' or check the BMC web interface under Firmware/BIOS information to identify if the Baseboard Management Controller is running AMI Megarac SPx firmware
    Affected if The BMC is not using AMI Megarac SPx firmware - this CVE does not apply
  2. Retrieve installed BMC firmware version
    Execute 'ipmitool -I openmcpi mc info' and locate the firmware version field, or check the BMC web interface firmware version display
    Affected if Unable to retrieve firmware version - cannot determine vulnerability status
  3. Compare version against affected ranges
    Check if the installed version starts with 12.x or 13.x. For 12.x versions: confirm version is >=12 and <12.7. For 13.x versions: confirm version is >=13 and <13.6
    Affected if Version falls within >=12 <12.7 or >=13 <13.6 - system is potentially affected

A system is affected if it uses AMI Megarac SPx BMC firmware version 12.x below 12.7, or version 13.x below 13.6.

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 update for AMI SPx BMC to patch the untrusted pointer dereference vulnerability. Verify BMC functionality and IPMI/SOL access after patching.

Recommended fix High confidence

MegaRAC SPx firmware version 12.7 or later for 12.x branch; version 13.6 or later for 13.x branch

  1. 1. Identify the current MegaRAC SPx firmware version running on the BMC by accessing the BMC web interface or using IPMI commands such as 'ipmi-fru' or 'bmc-info'
  2. 2. Determine which version branch (12.x or 13.x) is currently deployed based on the identified version
  3. 3. Obtain the appropriate fixed firmware version: upgrade to version 12.7 or later if on the 12.x branch, or upgrade to version 13.6 or later if on the 13.x branch
  4. 4. Download the firmware update from the hardware vendor (the OEM/ODM that uses AMI MegaRAC SPx) - contact the server manufacturer for the specific firmware image
  5. 5. Apply the firmware update through the BMC web interface, IPMI firmware update command, or vendor-provided update utility following their documented procedure
  6. 6. After reboot, verify the BMC is running the fixed version (12.7+ or 13.6+)
  7. 7. Confirm the vulnerability is remediated by reviewing the BMC firmware changelog or release notes for CVE-2023-34332 inclusion
Caveat BMC firmware upgrades carry risk of rendering the device unusable if interrupted; ensure stable power and follow vendor update procedures exactly; some configurations may need to be re-applied after firmware 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-34332 — 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-34332 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