CVE-2023-34330
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 · uneditedAMI SPx contains a vulnerability in the BMC where a user may inject code which could be executed via a Dynamic Redfish Extension interface. A successful exploit of this vulnerability may lead to a loss of confidentiality, integrity, and 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 confidenceAMI SPx Baseboard Management Controller (BMC) firmware contains a code injection vulnerability in the Dynamic Redfish Extension interface. An authenticated user can inject malicious code through this API extension point, which is then executed with BMC-level privileges, potentially compromising the entire server management plane.
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= 12= 13CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Check BMC firmware versionAccess the BMC web interface or use Redfish API (GET /redfish/v1/Managers/1) or IPMI command 'ipmitool mc info' to retrieve the firmware version. Look for version numbers in the firmware revision field.Affected if The firmware version matches 12.x or 13.x (specifically Ami Megarac SPx versions 12 or 13)
-
Verify Dynamic Redfish Extension is enabledQuery the BMC via Redfish API at /redfish/v1/Managers/1/RemoteRedfishService or check for the presence of the Dynamic Redfish Extension API endpoint. This may also appear as a custom OEM extension in the Redfish ServiceRoot (/redfish/v1/).Affected if The Dynamic Redfish Extension interface is present and enabled on the BMC
-
Confirm Redfish API authentication stateCheck if the Redfish API accepts authentication (even with low-privilege credentials). Attempt to authenticate to /redfish/v1/SessionService/Sessions and verify a session token can be obtained.Affected if An authenticated user session can be established with the BMC Redfish interface
-
Assess network exposure of BMCReview firewall rules, network segmentation, or access control lists that govern access to the BMC management IP address on ports 443 (HTTPS) or 623 (IPMI). Check if the BMC is directly internet-accessible.Affected if The BMC management interface is accessible from untrusted networks without proper access restrictions
You are affected if your BMC runs Ami Megarac SPx firmware version 12 or 13, the Dynamic Redfish Extension is enabled, and an attacker can reach the BMC with valid credentials or existing session access.
Generated from the published advisory. Verify against your own configuration.
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.
From vendor dataApply the vendor-supplied BMC firmware patch from AMI or the server OEM. Restrict network access to the BMC management interface to minimize exposure until the patch can be deployed.
- Consultation3.0 h
- Implementation6.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-34330 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2023-34330 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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