CVE-2023-34345
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 BMC contains a vulnerability in the SPX REST API, where an attacker with the required privileges can access arbitrary files, which may lead to information disclosure.
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 · high confidenceAMI BMC contains a path traversal vulnerability in the SPX REST API where an authenticated attacker with the required privileges can access arbitrary files on the filesystem, leading to sensitive information disclosure.
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.0, < 12.7>= 13.0, < 13.5CVSS 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
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/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 checksWork through these to decide whether this CVE applies to you.
-
Identify the BMC firmware versionAccess the BMC web interface, use IPMI command 'ipmitool -I lanplus -H <BMC_IP> -U <user> -P <pass> raw command', or query the Redfish API endpoint /redfish/v1/Managers/1 to retrieve the firmware versionAffected if The firmware version is AMI Megarac SP X and falls within 12.0 <= version < 12.7 or 13.0 <= version < 13.5
-
Confirm the SPX REST API is enabledCheck the BMC web UI under 'Services' or 'API Settings', or query the Redfish API for endpoint availability at /api/spx or similar SPX-related pathsAffected if The SPX REST API service is enabled and accessible on the BMC
-
Verify API authentication is requiredAttempt an unauthenticated request to the SPX REST API endpoints, or review the BMC user authentication settings and privilege levels configured for API accessAffected if The SPX REST API accepts requests from authenticated users with any privilege level, including low-privilege accounts
Your environment is affected if the BMC runs a vulnerable AMI Megarac SP X firmware version (12.0-12.6.x or 13.0-13.4.x) and the SPX REST API is enabled with accessible authentication.
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.5
Apply vendor-provided firmware patches from AMI for the BMC, and review/restrict SPX REST API privileges to minimize exposure.
Megarac Sp X version 12.7 or later for 12.x branch; version 13.5 or later for 13.x branch
- 1. Identify the current Megarac Sp X version by accessing the BMC web interface or using IPMI commands
- 2. If running version >=12.0 and <12.7, plan upgrade to version 12.7 or later in the 12.x branch
- 3. If running version >=13.0 and <13.5, plan upgrade to version 13.5 or later in the 13.x branch
- 4. Review release notes for any specific upgrade requirements or注意事项
- 5. Back up current BMC configuration if possible
- 6. Upload the firmware image through the BMC web interface or Redfish API
- 7. Verify the upgrade was successful by checking the new firmware version
- 8. Validate that the path traversal vulnerability is no longer present
Generated from the published advisory — verify against the referenced sources before acting.
- 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-34345 — 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-34345 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