CVE-2023-34473
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 valid user may cause a use of hard-coded credentials. 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 firmware contains hard-coded credentials embedded in the BMC (Baseboard Management Controller). A valid authenticated user can leverage these credentials to gain unauthorized access or perform privileged operations, potentially compromising confidentiality, integrity, and availability of the managed system.
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.
-
Identify the BMC firmware vendor and modelAccess the BMC web interface or use IPMI commands (e.g., 'ipmitool -I lanplus -H <BMC_IP> -U <user> -P <pass> raw' or check BIOS/UEFI settings) to identify the firmware vendor. Look for 'AMI' or 'American Megatrends' and 'Megarac SP' in the BMC information.Affected if The BMC is identified as AMI Megarac SP or SPx firmware
-
Check the installed BMC firmware versionVia BMC web interface (usually under 'Maintenance' or 'Firmware Information'), or via IPMI: 'ipmitool -I lanplus -H <BMC_IP> -U <user> -P <pass> raw 0x06 0x01' or similar version query command. Alternatively, check within the BIOS/UEFI setup under BMC configuration.Affected if The firmware version reported is 12 or 13 (exact version number matching the affected range)
-
Verify if remote BMC management is accessibleCheck if the BMC network interface is enabled and reachable. Use 'ipmitool -I lanplus -H <BMC_IP> -U <user> -P <pass> channel info' or attempt to access the BMC web interface remotely over HTTPS/HTTP on ports 443/80. Verify VLAN configuration if used.Affected if Remote access to BMC is enabled and the BMC is network-accessible
-
Inspect BMC user accounts for default or unknown accountsList all BMC users via IPMI: 'ipmitool -I lanplus -H <BMC_IP> -U <user> -P <pass> user list' or through the BMC web interface under 'User Management'. Compare against known legitimate user accounts for your organization.Affected if There are additional, unrecognized user accounts, or default/standard AMI accounts not previously configured by your organization
Your environment is affected if the BMC runs AMI Megarac SPx firmware version 12 or 13, is remotely accessible, and may contain unauthorized accounts from the hardcoded credential exposure.
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 vendor-provided firmware updates for AMI SPx when available; change any default credentials immediately; restrict BMC network access through firewalls or VLAN segmentation; disable remote management protocols not in use.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.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 $5,600.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-34473 — 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-34473 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