CVE-2023-37295
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 BMC contains a heap memory corruption vulnerability that can be exploited by an attacker on the adjacent network. Successful exploitation allows memory corruption which may compromise confidentiality, integrity, and availability of the affected 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, < 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 if the system uses AMI SPx BMC firmwareCheck the BMC firmware version via IPMI command 'ipmitool -I lanplus -H <bmc-ip> -U <user> -P <pass> mc info' or by accessing the BMC web interface and looking at the firmware/version information under the System Information or About sectionAffected if The BMC is identified as AMI Megarac SP or SPx
-
Determine the installed firmware version numberExtract the firmware version from the BMC information obtained via IPMI ('mc info' output shows firmware revision), Redfish API (GET /redfish/v1/Managers/1), or the BMC web interface firmware version fieldAffected if The version is 12.x where x is less than 7, or 13.x where x is less than 6 (i.e., 12.0 to 12.6 or 13.0 to 13.5)
-
Verify the BMC network management interface is enabledCheck IPMI LAN configuration with 'ipmitool -I lanplus -H <bmc-ip> -U <user> -P <pass> lan print 1' or check via Redfish: GET /redfish/v1/Managers/1/NetworkProtocol; confirm that IP, HTTP, HTTPS, or other network services are enabledAffected if The BMC has an active IP address and network services are enabled, exposing the management interface to the network
The system is affected if it runs AMI Megarac SPx firmware versions 12.0 through 12.6 or 13.0 through 13.5 and has the BMC network interface accessible from an adjacent network.
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 when available; until then, restrict network access to the BMC management interface to trusted networks only and disable unnecessary BMC services.
Megarac SP X version 12.7 or 13.6 (depending on your current major version branch)
- Identify the current Megarac SP X version installed on the affected BMC system
- Download Megarac SP X version 12.7 (for systems currently on 12.x) or version 13.6 (for systems currently on 13.x) from the official Megarac/AMI vendor support portal
- Review the vendor's firmware update documentation and ensure a backup of current BMC configuration is performed
- Apply the firmware upgrade to the BMC via the vendor-recommended method (typically through the BMC web interface, IPMI command, or vendor-specific update utility)
- After upgrade, verify the new version is installed by checking the BMC firmware version
- Validate that affected services and functionality are operational post-upgrade
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation6.0 h
- Implementation12.0 h
- Testing10.0 h
- Review / QA5.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $9,216.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-37295 — 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-37295 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