dbcve.org
Integrated Lights Out 5 FirmwareOperating system · Hpe

CVE-2023-50272

CRITICAL · 9.8 CVSS v3.1 Published 2023-12-19
Fix available
A fix is available. Upgrade to after 3.00 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

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 · unedited
A potential security vulnerability has been identified in HPE Integrated Lights-Out 5 (iLO 5) and Integrated Lights-Out 6 (iLO 6). The vulnerability could be remotely exploited to allow authentication bypass.

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 confidence

A critical authentication bypass vulnerability in HPE Integrated Lights-Out 5 (iLO 5) and Integrated Lights-Out 6 (iLO 6) baseboard management controllers. The flaw allows remote attackers to bypass authentication mechanisms and gain unauthorized administrative access to the BMC, potentially leading to complete server compromise.

MitigationApply the relevant HPE firmware update for iLO 5 or iLO 6 from the HPE security advisory. Until patched, restrict network accessibility of iLO management interfaces using firewall rules or ACLs, and monitor for unauthorized access attempts.

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
Integrated Lights Out 5 FirmwareOperating system
Affected:>= 2.63, <= 3.00
Integrated Lights Out 6 FirmwareOperating system
Affected:>= 1.05, <= 1.55

CVSS 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
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify HPE iLO BMC in your environment
    Locate HPE servers and access their baseboard management controller interfaces. You can identify iLO via: (1) Scanning network for HTTPS services on port 443 or 8443 with HPE iLO SSL certificates, (2) Checking server hardware documentation or inventory systems for iLO BMC presence, (3) Accessing the BMC web interface at https://[server-ip]/ or via SSH to the iLO IP.
    Affected if The environment contains HPE ProLiant servers with Integrated Lights-Out (iLO) 5 or iLO 6 baseboard management controllers.
  2. Determine iLO firmware version
    Access the iLO web interface and navigate to the 'Overview' or 'General' page in the 'iLO Settings' section to view the firmware version. Alternatively, connect via SSH to the iLO IP and run the command 'show /map1/firmwareinfo' or 'version'. You can also query the Redfish API at https://[ilo-ip]/redfish/v1/Managers/1 to retrieve firmware version information.
    Affected if You have access to an HPE iLO BMC and can retrieve its firmware version.
  3. Confirm iLO 5 version falls within affected range
    If you identified iLO 5, check if the firmware version is between 2.63 and 3.00 (inclusive). Compare your installed version number against this range. iLO 5 versions typically appear as formats like 2.63, 2.70, 2.80, or 3.00.
    Affected if The iLO 5 firmware version is >= 2.63 and <= 3.00.
  4. Confirm iLO 6 version falls within affected range
    If you identified iLO 6, check if the firmware version is between 1.05 and 1.55 (inclusive). Compare your installed version number against this range. iLO 6 versions typically appear as formats like 1.05, 1.20, 1.40, or 1.55.
    Affected if The iLO 6 firmware version is >= 1.05 and <= 1.55.

Your environment is affected if you have HPE iLO 5 firmware between versions 2.63 and 3.00, or HPE iLO 6 firmware between versions 1.05 and 1.55.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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.

dbcve · scoped
Upgrade available Upgrade to a release after 3.00
Interim mitigation

Apply the relevant HPE firmware update for iLO 5 or iLO 6 from the HPE security advisory. Until patched, restrict network accessibility of iLO management interfaces using firewall rules or ACLs, and monitor for unauthorized access attempts.

Recommended fix Moderate confidence

iLO 5: upgrade to firmware >= 3.10; iLO 6: upgrade to firmware >= 1.60

  1. 1. Identify the current iLO firmware version by accessing the iLO web interface or using the iLO RESTful API
  2. 2. For iLO 5: If firmware version is between 2.63 and 3.00 (inclusive), download and install firmware version 3.10 or later from the HPE support site
  3. 3. For iLO 6: If firmware version is between 1.05 and 1.55 (inclusive), download and install firmware version 1.60 or later from the HPE support site
  4. 4. Upload the firmware via the iLO web interface under 'Firmware' > 'Update' or use the iLO RIBCL or RESTful API for remote updates
  5. 5. After firmware update, verify the new version is installed and confirm the vulnerability is remediated
  6. 6. Review iLO security settings and ensure default credentials have been changed
Caveat Firmware updates require server downtime; verify compatibility with existing management tools and ensure backup of iLO configuration before updating

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Integrated Lights Out 5 Firmware Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-50272 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2023-50272 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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