CVE-2023-37294
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’s SPx contains a vulnerability in the BMC where an Attacker may cause a heap memory corruption 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 confidenceAMI SPx Baseboard Management Controller (BMC) firmware contains a heap memory corruption vulnerability exploitable by an attacker with adjacent network access. The flaw allows memory corruption which could enable remote code execution or denial of service, impacting confidentiality, integrity, and availability of the managed server.
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, < 12.7>= 13, < 13.6CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify BMC firmware versionQuery the BMC for its firmware version using IPMI (e.g., `ipmitool -I lanplus -H <bmc-ip> -U <user> fru print` or via the BMC web interface under Firmware/Version information)Affected if The displayed version falls within 12.0 to 12.6 or 13.0 to 13.5 (i.e., >= 12 but < 12.7, or >= 13 but < 13.6)
-
Confirm the BMC is network accessibleVerify that the BMC management interface (typically ports 443, 80, or 623 for IPMI) is reachable from the network by attempting to ping the BMC IP or checking open ports on the BMCAffected if The BMC is reachable from network segments beyond the trusted management VLAN, indicating adjacent network attack surface exists
-
Check for unauthorized BMC accountsList all BMC user accounts via IPMI (e.g., `ipmitool -I lanplus -H <bmc-ip> -U <user> user list`) or through the BMC web interface to detect any unexpected accounts that may indicate exploitationAffected if New or unauthorized accounts exist that were not provisioned by administrators, which could be a sign of post-exploitation activity
-
Review BMC event logs for anomaliesRetrieve BMC SEL (System Event Log) using IPMI (e.g., `ipmitool -I lanplus -H <bmc-ip> -U <user> sel elist`) or via Redfish API to look for unexpected resets, memory errors, or authentication failuresAffected if Logs contain unexplained BMC resets, heap corruption events, or mass authentication attempts aligned with the CVE disclosure date
A user is affected if their BMC firmware version is 12.x where x < 7, or 13.x where x < 6, and the BMC is network-accessible to adjacent attackers.
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.
dbcve · scoped12.713.6
Apply the vendor-supplied firmware patch for SPx BMC when available; until then, restrict network access to the BMC management interfaces and monitor for signs of exploitation.
MegaRAC SPx firmware version 12.7 (for 12.x branch) or 13.6 (for 13.x branch) or later
- 1. Identify the current MegaRAC SPx firmware version running on the BMC by accessing the BMC web interface or using IPMI commands.
- 2. Obtain the fixed firmware version from the hardware vendor (the server OEM such as Dell, HP, Lenovo, etc. or AMI directly). The fixed versions are 12.7 or later for the 12.x branch, and 13.6 or later for the 13.x branch.
- 3. Follow the vendor's standard BMC firmware update procedure, which typically involves uploading the firmware binary through the BMC web interface or using tools like flashrom, ipmiutil, or the vendor's management utility.
- 4. After flashing, verify the new firmware version is installed and the BMC has rebooted successfully.
- 5. Validate that the BMC is operational and all management functions are working normally.
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation8.0 h
- Implementation16.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $10,240.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-37294 — 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-37294 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