CVE-2021-25129
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 spx_restservice getvideodata_func function path traversal vulnerability.
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 confidenceLocal path traversal vulnerability in HPE Cloudline BMC firmware's spx_restservice getvideodata_func function allows local attackers to read arbitrary files from the filesystem via specially crafted requests.
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 BMC firmware versionAccess the HPE BMC web interface (iLO) and navigate to Administration > Firmware or use CLI: 'show /system1/firmware1'. For HPE Cloudline, check under iLO web UI > Server Information > Firmware Version.Affected if The displayed firmware version matches exactly 1.08.0.0, 1.10.0.0, 1.07.0.0, or 1.09.0.0 for the Cloudline models listed.
-
Confirm server model is affectedVerify the server is one of the following models: HPE Cloudline CL3100 Gen10, CL4100 Gen10, CL5200 Gen9, CL5800 Gen9, or CL5800 Gen10. Check via BMC web interface under Server Name or System Information.Affected if The server model is any of these five Cloudline models.
-
Check if spx_restservice is accessibleAttempt to access the vulnerable endpoint via curl or browser: GET https://<BMC-IP>/spx_restservice/getvideodata_func?path=/etc/passwd or check if the BMC exposes port 8443/443 with the spx_restservice API.Affected if The spx_restservice endpoint returns file contents or is reachable without authentication restrictions.
-
Review BMC network access settingsIn BMC web UI, navigate to Network > Management Network or Access Settings. Verify who can reach the BMC management interface.Affected if The BMC management interface (iLO) is accessible from untrusted networks or does not have strict IP access controls.
A user is affected if their Cloudline server firmware version exactly matches one of the four vulnerable versions and the BMC management interface with spx_restservice is accessible to them or an attacker.
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 HPE firmware updates when released; until then, restrict physical access to servers and limit administrative access to the BMC management interface to trusted personnel only.
- 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-25129 — 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-25129 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