CVE-2021-25135
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 setsmtp_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 local buffer overflow vulnerability exists in the Baseboard Management Controller (BMC) firmware of HPE Cloudline Gen9 and Gen10 servers. The overflow occurs in the spx_restservice component's setsmtp_func function, which handles SMTP configuration. An attacker with local access to the BMC could potentially exploit this to execute arbitrary code or cause a denial of service.
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 the HPE Cloudline server modelCheck the server model label or BMC web interface for the exact model number (CL3100, CL4100, CL5200, CL5800) and generation (Gen9 or Gen10)Affected if The model is CL3100 Gen10, CL4100 Gen10, CL5200 Gen9, CL5800 Gen10, or CL5800 Gen9
-
Retrieve the BMC firmware versionAccess the BMC web interface or use IPMI command 'ipmiutil fru' or 'ipmitool mc info' to obtain the installed firmware versionAffected if The firmware version matches exactly 1.08.0.0, 1.10.0.0 (Gen10), 1.07.0.0 (CL5200 Gen9), or 1.09.0.0 (CL5800 Gen9)
-
Verify SMTP configuration accessCheck if the BMC SMTP configuration interface is accessible via the web UI or API endpoint for setsmtp_func in the spx_restservice componentAffected if The SMTP configuration feature is exposed and the spx_restservice component is running on the BMC
-
Confirm local BMC access capabilityDetermine if an attacker could obtain local access to the BMC through physical access or network management interfaceAffected if Physical access to the server or network access to the BMC management interface is possible
A user is affected if they are running one of the listed HPE Cloudline models with the exact firmware versions specified and the BMC SMTP configuration feature 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 vendor-provided BMC firmware patch from HPE to address this vulnerability. If a patch is unavailable, restrict physical and network access to the BMC management interface to minimize attack surface.
- Consultation3.0 h
- Implementation6.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 $4,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-25135 — 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-25135 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