CVE-2019-11982
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 remote cross site scripting vulnerability was identified in HPE Integrated Lights-Out 4 (iLO 4) earlier than v2.61b for Gen9 servers and Integrated Lights-Out 5 (iLO 5) for Gen10 Servers earlier than version v1.39.
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 confidenceA remote cross-site scripting (XSS) vulnerability in HPE Integrated Lights-Out 4 (iLO 4) before v2.61b for Gen9 servers and iLO 5 before v1.39 for Gen10 servers allows attackers to inject malicious scripts through the web management interface.
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.39<= 2.61bCVSS 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
- High
- Privileges
- None
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:N/AC:H/PR:N/UI:R/S:C/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 firmware version via web interfaceLog in to the iLO web management interface and navigate to the main dashboard or 'Overview' page. The firmware version is typically displayed in the 'General Information' or 'iLO Firmware Version' section.Affected if The displayed firmware version is 2.61b or lower for iLO 4, or 1.39 or lower for iLO 5.
-
Identify iLO firmware version via SSHConnect to the iLO management interface via SSH using an administrative account. Run the command 'info' or 'version' to retrieve the firmware version information.Affected if The returned firmware version is 2.61b or lower for iLO 4, or 1.39 or lower for iLO 5.
-
Identify iLO firmware version via HPONCFGUse the HPONCFG utility from the host operating system to query iLO. Run 'hponcfg -g' or 'hponcfg -i' to retrieve the current iLO firmware version.Affected if The reported firmware version is 2.61b or lower for iLO 4, or 1.39 or lower for iLO 5.
-
Identify iLO version via iLO RESTful APISend a GET request to the iLO RESTful API endpoint (such as https://<ilo-ip>/redfish/v1/Managers/Self) using curl or a similar tool with appropriate authentication to retrieve the firmware version.Affected if The firmware version in the API response is 2.61b or lower for iLO 4, or 1.39 or lower for iLO 5.
You are affected if your HPE iLO 4 firmware is version 2.61b or lower, or your iLO 5 firmware is version 1.39 or lower, and the web management interface 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 dataUpgrade HPE iLO 4 firmware to version v2.61b or later for Gen9 servers, and iLO 5 firmware to v1.39 or later for Gen10 servers.
- Consultation4.0 h
- Implementation4.0 h
- Testing3.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 $3,728.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-11982 — 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-2019-11982 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