CVE-2019-11983
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 buffer overflow 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 buffer overflow vulnerability exists in HPE Integrated Lights-Out 4 (iLO 4) prior to v2.61b for Gen9 servers and iLO 5 prior to v1.39 for Gen10 servers. The vulnerability allows remote attackers to potentially execute arbitrary code or cause a denial of service due to insufficient bounds checking in the iLO firmware's remote 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
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- Low
- Availability
- High
CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/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.
-
Confirm HPE iLO management interface is presentAccess the iLO web interface by browsing to the server's iLO IP address, or use the HPONCFG command-line utility (hponcfg -g) to query the iLO subsystemAffected if The system does not have an iLO management interface, this CVE does not apply
-
Identify iLO generation (iLO 4 vs iLO 5)In the iLO web interface, go to Information > Overview. iLO 4 appears on Gen9 servers, iLO 5 on Gen10 servers. Alternatively, check the firmware version number format: iLO 4 versions typically start with 2.x, iLO 5 versions with 1.xAffected if Unable to determine iLO generation, version comparison may be invalid
-
Check installed iLO firmware versionIn the iLO web interface, navigate to Administration > Firmware. Note the firmware version displayed. Alternatively, run 'hponcfg -g' from the server OS to retrieve the iLO firmware versionAffected if The installed version cannot be determined or is not displayed
-
Compare version against affected rangesFor iLO 4: if version is less than 2.61b, the system is affected. For iLO 5: if version is less than 1.39, the system is affected. Note that versions 2.61b and 1.39 and later are patchedAffected if iLO 4 version <= 2.61b OR iLO 5 version <= 1.39
A system is affected if it runs HPE iLO 4 firmware version 2.61b or lower, or iLO 5 firmware version 1.39 or lower, on Gen9 or Gen10 servers respectively.
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 firmware to version v2.61b or later for iLO 4 (Gen9) and v1.39 or later for iLO 5 (Gen10). Apply during a scheduled maintenance window following HPE's firmware update procedures.
- Consultation2.0 h
- Implementation2.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,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-11983 — 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-11983 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