dbcve.org
Megarac Sp XApplication · Ami

CVE-2023-34342

CRITICAL · 9.1 CVSS v3.1 Published 2023-06-12
Fix available
A fix is available. Upgrade to 12.7 / 13.5 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable 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 BMC contains a vulnerability in the IPMI handler, where an attacker can upload and download arbitrary files under certain circumstances, which may lead to denial of service, escalation of privileges, 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 vulnerability in the IPMI handler that allows an attacker to upload and download arbitrary files under certain conditions. This file operation weakness in the IPMI subsystem can be chained with other issues to achieve privilege escalation, cause denial of service, expose sensitive information, or tamper with data.

MitigationRestrict network access to the BMC/IPMI interface to trusted networks only, disable IPMI if not required, and apply vendor firmware updates from AMI when available. Consider out-of-band network segmentation for management interfaces.

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N

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 product and firmware version
    Access the BMC web interface or use IPMI commands (e.g., ipmitool -I lanplus -H <BMC_IP> -U <user> -P <pass> raw commands or dmidecode on the host) to retrieve the firmware version and product name. Look for 'Ami Megarac Sp X' in the product identification.
    Affected if The product is Ami Megarac Sp X and the firmware version falls within 12.0 to 12.6 or 13.0 to 13.4.
  2. Confirm IPMI interface is enabled
    Verify that the IPMI over LAN (IPMI interface) is enabled on the BMC. This can be checked via the BMC web interface under 'IPMI' or 'Network' settings, or by using ipmitool: 'ipmitool -I lanplus -H <BMC_IP> -U <user> chassis status' or checking the IPMI configuration.
    Affected if IPMI over LAN is enabled and accessible from the network.
  3. Check for IPMI file transfer functionality
    Inspect whether IPMI file transfer handlers (like IPMI file upload/download or SEL/FRU operations) are exposed. This may be visible in BMC logs, IPMI configuration, or through attempted file operations via IPMI protocols if you have administrative access.
    Affected if The IPMI handler exposes file operation capabilities that can be triggered by an attacker.

You are affected if your BMC runs Ami Megarac Sp X firmware version 12.0-12.6 or 13.0-13.4 and has IPMI over LAN enabled, allowing remote attackers to exploit file operation weaknesses in the IPMI subsystem.

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

Restrict network access to the BMC/IPMI interface to trusted networks only, disable IPMI if not required, and apply vendor firmware updates from AMI when available. Consider out-of-band network segmentation for management interfaces.

Recommended fix Low confidence

Megarac SP X version 12.7 or later, or version 13.5 or later (depending on which branch is in use)

  1. Identify the current installed version of Megarac SP X BMC firmware
  2. If running version 12.0 through 12.6.x, upgrade to version 12.7 or later
  3. If running version 13.0 through 13.4.x, upgrade to version 13.5 or later
  4. Verify the upgrade was successful and the vulnerability is remediated
  5. Following upgrade, review and validate IPMI handler configurations for security

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
  • Implementation16.0 h
  • Testing12.0 h
  • Review / QA6.0 h
42.0 hours of engineering $7,360
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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