dbcve.org
Cloudline Cl3100 Gen10 Server FirmwareOperating system · Hpe

CVE-2021-25136

HIGH · 7.8 CVSS v3.1 Published 2021-01-29
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
80/100
Remediation priority · High
Zero-click

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 · unedited
The 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 setsolvideoremotestorage_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 confidence

A local buffer overflow vulnerability exists in the HPE Cloudline BMC firmware's spx_restservice component, specifically in the setsolvideoremotestorage_func function. This allows a local authenticated attacker to potentially execute arbitrary code or cause a denial of service via buffer overflow exploitation.

MitigationApply the vendor-supplied BMC firmware update from HPE for the affected Cloudline CL series servers. As this is a local vulnerability, ensure proper access controls and least-privilege principles for BMC access.

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
Cloudline Cl3100 Gen10 Server FirmwareOperating system
Affected:= 1.08.0.0= 1.10.0.0
Cloudline Cl4100 Gen10 Server FirmwareOperating system
Affected:= 1.08.0.0= 1.10.0.0
Cloudline Cl5200 Gen9 Server FirmwareOperating system
Affected:= 1.07.0.0
Cloudline Cl5800 Gen10 Server FirmwareOperating system
Affected:= 1.08.0.0
Cloudline Cl5800 Gen9 Server FirmwareOperating system
Affected:= 1.09.0.0

CVSS 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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify the HPE Cloudline server model
    Access the BMC web interface or use IPMI commands to query the system model. Look for CL3100, CL4100, CL5200, or CL5800 in the hardware inventory.
    Affected if The server model is NOT an HPE Cloudline CL3100, CL4100, CL5200, or CL5800 Gen9/Gen10 server.
  2. Check the BMC firmware version
    Use IPMI command 'ipmitool -I lanplus -H <BMC_IP> -U <user> -P <pass> raw' or access the BMC web interface under 'Maintenance' or 'Firmware Information' to retrieve the installed firmware version.
    Affected if The firmware version matches exactly 1.08.0.0, 1.10.0.0 (CL3100/CL4100 Gen10), 1.07.0.0 (CL5200 Gen9), 1.09.0.0 (CL5800 Gen9), or 1.08.0.0 (CL5800 Gen10).
  3. Verify the spx_restservice component is running
    Access the BMC via SSH or web API and check for the spx_restservice process. This may be visible in the BMC service status or via API endpoint such as /api/spx/restservice/status.
    Affected if The spx_restservice component is exposed and running on the BMC.
  4. Confirm the setsolvideoremotestorage function is accessible
    The vulnerability exists in the setsolvideoremotestorage_func function. Check if the BMC API endpoint related to SOL video remote storage configuration is exposed, typically via REST API calls to configure remote storage features.
    Affected if The SOL video remote storage configuration feature is available and accessible on the BMC.
  5. Verify local authenticated access to BMC
    Confirm that local user accounts exist with access to the BMC. This is required for the exploit as the vulnerability is local and requires authentication.
    Affected if Local BMC user accounts with administrative or operator-level access are configured.

You are affected if you are running an HPE Cloudline CL3100, CL4100, CL5200, or CL5800 server with firmware version 1.07.0.0, 1.08.0.0, 1.09.0.0, or 1.10.0.0, and the spx_restservice with SOL video remote storage functionality is accessible to authenticated local users.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply the vendor-supplied BMC firmware update from HPE for the affected Cloudline CL series servers. As this is a local vulnerability, ensure proper access controls and least-privilege principles for BMC access.

Fix this in Cloudline Cl3100 Gen10 Server Firmware Scoped from the published advisory
  • Consultation3.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,440
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,304.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2021-25136 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2021-25136 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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