CVE-2021-29202
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 · uneditedA local buffer overflow vulnerability was discovered in HPE Integrated Lights-Out 4 (iLO 4); HPE SimpliVity 380 Gen9; HPE Integrated Lights-Out 5 (iLO 5) for HPE Gen10 Servers; HPE SimpliVity 380 Gen10; HPE SimpliVity 2600; HPE SimpliVity 380 Gen10 G; HPE SimpliVity 325; HPE SimpliVity 380 Gen10 H version(s): Prior to version 2.78.
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 HPE Integrated Lights-Out (iLO) firmware versions prior to 2.78. The vulnerability affects iLO 4, iLO 5 for Gen10 servers, and multiple SimpliVity systems. Successful exploitation requires local access to the system.
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< 2.78< 2.44CVSS 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
- High
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:H/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 iLO in your environmentInventory your HPE servers and check if they have Integrated Lights-Out (iLO) management interfaces installed. This includes HPE ProLiant servers with iLO 4 or iLO 5.Affected if Any HPE server with iLO 4 or iLO 5 firmware is present in the environment.
-
Determine iLO firmware versionAccess the iLO web interface via HTTPS, or connect via SSH to the iLO IP address. Use the command 'show /map1/firmware1' or check the firmware information page in the web UI to retrieve the installed iLO firmware version.Affected if The installed firmware version cannot be determined or is visible in the management interface.
-
Compare version against affected rangesCheck if the installed iLO version is below 2.78 for iLO 4, or below 2.44 for iLO 5. Note the specific iLO generation (4 or 5) as indicated in the management interface.Affected if iLO 4 firmware version is less than 2.78, OR iLO 5 firmware version is less than 2.44.
-
Verify local access exposureAssess whether local physical or console access to the iLO management interface is possible. This includes direct console access, KVM over IP, or local network segment access to the iLO dedicated network port.Affected if Local or console-level access to the iLO interface is possible or cannot be restricted.
You are affected if your environment contains HPE iLO 4 firmware prior to 2.78 or iLO 5 firmware prior to 2.44, and local access to the iLO interface is feasible.
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 data2.442.78
Upgrade HPE iLO firmware to version 2.78 or later to remediate this vulnerability. This is a local-only attack vector, reducing risk in properly segmented environments.
- Consultation2.0 h
- Implementation4.0 h
- Testing2.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 $2,848.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-29202 — 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-29202 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