CVE-2020-7202
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 potential security vulnerability has been identified in HPE Integrated Lights-Out 5 (iLO 5) and Integrated Lights-Out 4 (iLO 4) firmware. The vulnerability could be remotely exploited to disclose the serial number and other information.
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 remote information disclosure vulnerability in HPE Integrated Lights-Out 4 (iLO 4) and iLO 5 firmware allows unauthenticated attackers to retrieve the server's serial number and potentially other sensitive system information via the iLO web interface or API.
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.76< 2.31CVSS 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
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
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.
-
Check iLO 4 firmware versionLog into the iLO web interface, navigate to the 'Overview' or 'Information' page under 'iLO Activity', and locate the firmware version displayed under 'iLO Firmware Version'. Alternatively, access the iLO web interface at https://<server-ip>/ and look for the version in the login page footer or the Dashboard overview.Affected if The displayed firmware version is lower than 2.76 (for example, 2.70, 2.50, or any version < 2.76).
-
Check iLO 5 firmware versionLog into the iLO web interface, navigate to the 'Overview' or 'Information' page under 'iLO Activity', and locate the firmware version displayed under 'iLO Firmware Version'. Alternatively, access the iLO web interface at https://<server-ip>/ and check the Dashboard or the iLO Overview section.Affected if The displayed firmware version is lower than 2.31 (for example, 2.22, 2.10, or any version < 2.31).
-
Check iLO version via RESTful APISend an HTTP GET request to the iLO RESTful API endpoint: GET https://<ilo-ip>/redfish/v1/Managers/Self. Inspect the 'FirmwareVersion' field in the JSON response.Affected if The 'FirmwareVersion' field shows a version below 2.76 for iLO 4 or below 2.31 for iLO 5.
-
Check iLO version using HPONCFGRun the HPONCFG utility (HPE Lights-Out Configuration Utility) on the host server: 'hponcfg -g' or 'hponcfg -a -i' to retrieve the current iLO configuration and firmware version. Look for the 'Firmware Revision' or 'Firmware Version' field in the output.Affected if The reported firmware version is < 2.76 (iLO 4) or < 2.31 (iLO 5).
You are affected if your HPE iLO 4 firmware version is below 2.76 or your iLO 5 firmware version is below 2.31, as this unauthenticated vulnerability allows attackers to retrieve sensitive system information via the iLO web interface or API.
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.312.76
Update HPE iLO firmware to the latest patched version available from HPE support, ensuring the update is applied during a scheduled maintenance window following HPE's firmware update procedures.
- Consultation2.0 h
- Implementation1.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,696.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-7202 — 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-2020-7202 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