CVE-2021-25130
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 · uneditedThe Baseboard Management Controller(BMC) in HPE Cloudline CL5800 Gen9 Server; HPE Cloudline CL5200 Gen9 Server; HPE Cloudline CL4100 Gen10 Server; HPE Cloudline CL3100 Gen10 Server; HPE Cloudline CL5800 Gen10 Server BMC firmware has a local buffer overlfow in spx_restservice setactdir_func function.
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 confidenceA buffer overflow vulnerability exists in the spx_restservice setactdir_func function in HPE Cloudline BMC firmware. A local attacker with access to the BMC could exploit this to potentially execute arbitrary code or cause a denial of service, as indicated by the HIGH severity and local attack vector.
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= 1.08.0.0= 1.10.0.0= 1.08.0.0= 1.10.0.0= 1.07.0.0= 1.08.0.0= 1.09.0.0CVSS 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
- Local
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/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 HPE Cloudline BMC modelAccess BMC web interface or use IPMI command 'ipmitool mc info' or Redfish GET /redfish/v1/Managers/1 to identify the server model (CL3100, CL4100, CL5200, or CL5800)Affected if Model is Cloudline CL3100 Gen10, CL4100 Gen10, CL5200 Gen9, CL5800 Gen10, or CL5800 Gen9
-
Retrieve BMC firmware versionUse IPMI command 'ipmitool mc get firmware revision' or access BMC web interface System Information page, or query Redfish GET /redfish/v1/Managers/1/SoftwareInventoryAffected if Firmware version matches 1.08.0.0, 1.10.0.0, 1.07.0.0, or 1.09.0.0 for the identified model
-
Verify spx_restservice is runningCheck BMC service status via IPMI 'ipmitool raw' or access BMC shell and run 'ps | grep restservice' or query Redfish /redfish/v1/Managers/1/ServiceAffected if The spx_restservice is active and responding on the BMC (typically port 443 or 80)
-
Confirm local or network BMC access existsVerify BMC IP address is configured and accessible; check physical access controls to server BMC interfaceAffected if BMC is network-accessible or attacker has physical access to BMC management port
System is affected if it is an HPE Cloudline CL3100/CL4100/CL5200/CL5800 server with firmware version 1.07.0.0, 1.08.0.0, 1.09.0.0, or 1.10.0.0 and the BMC interface is accessible.
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 HPE firmware update for the affected Cloudline CL series servers. Until patched, limit physical and local network access to the BMC interface and ensure only authorized personnel have BMC credentials.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.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,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-25130 — 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-2021-25130 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