dbcve.org
Integrated Lights Out 4Operating system · Hp

CVE-2023-28083

MEDIUM · 5.4 CVSS v3.1 Published 2023-03-22
Fix available
A fix is available. Upgrade to 1.20 / 2.78 or later.
See remediation →
58/100
Remediation priority · Elevated
Remotely reachable

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 remote Cross-site Scripting vulnerability was discovered in HPE Integrated Lights-Out 6 (iLO 6), Integrated Lights-Out 5 (iLO 5) and Integrated Lights-Out 4 (iLO 4). HPE has provided software updates to resolve this vulnerability in HPE Integrated Lights-Out.

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 remote Cross-Site Scripting (XSS) vulnerability in HPE Integrated Lights-Out (iLO) firmware versions 4, 5, and 6 allows attackers to inject malicious scripts through the web-based iLO interface.

MitigationApply the HPE software updates provided for the respective iLO version to patch this vulnerability.

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 4Operating system
Affected:< 2.82
Integrated Lights Out 5Operating system
Affected:< 2.78
Integrated Lights Out 6Operating system
Affected:< 1.20

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
Low
User interaction
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/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 checks

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

  1. Identify iLO firmware version via web interface
    Log into the iLO web interface (typically https://[server-ip]/ilo or /hpilo) and navigate to the Overview or Information page to view the iLO firmware version displayed.
    Affected if The displayed firmware version is below 2.82 for iLO 4, below 2.78 for iLO 5, or below 1.20 for iLO 6
  2. Identify iLO firmware version via RESTful API
    Send a GET request to the iLO REST API endpoint (e.g., https://[server-ip]/redfish/v1/Managers/1) and inspect the FirmwareVersion field in the JSON response.
    Affected if The FirmwareVersion value is below 2.82 for iLO 4, below 2.78 for iLO 5, or below 1.20 for iLO 6
  3. Verify web-based iLO interface is enabled
    Confirm that the iLO web interface is accessible and not disabled. Check iLO settings via the web UI under Administration > Access Settings or via the REST API at /redfish/v1/Managers/1/NetworkProtocol.
    Affected if The web interface (HTTP/HTTPS) is enabled and accessible, which is required for the XSS vulnerability to be exploitable
  4. Check iLO generation to determine version family
    Determine whether the server uses iLO 4, iLO 5, or iLO 6 by checking the server model or the iLO login screen banner, which typically displays the iLO generation.
    Affected if The iLO generation is 4, 5, or 6 and the corresponding version falls below the safe thresholds listed above

The environment is affected if the installed iLO firmware version is below 2.82 (iLO 4), below 2.78 (iLO 5), or below 1.20 (iLO 6) and the web-based iLO interface is enabled.

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 1.20 / 2.78 / 2.82 or later
Fixed in 1.202.782.82
Interim mitigation

Apply the HPE software updates provided for the respective iLO version to patch this vulnerability.

Recommended fix Moderate confidence

iLO 4: version 2.82 or later | iLO 5: version 2.78 or later | iLO 6: version 1.20 or later

  1. 1. Identify the current iLO firmware version by accessing the iLO web interface and navigating to the 'Information' or 'Overview' section
  2. 2. Determine which iLO generation (4, 5, or 6) is in use based on the hardware
  3. 3. Navigate to the HPE support website (support.hpe.com) and locate the appropriate iLO firmware update for your specific server model
  4. 4. Download the firmware update - ensure the version meets or exceeds: iLO 4: 2.82, iLO 5: 2.78, iLO 6: 1.20
  5. 5. Access the iLO web interface as an administrator
  6. 6. Navigate to the 'Firmware' or 'Maintenance' section
  7. 7. Upload and apply the new firmware file following the on-screen instructions
  8. 8. Wait for the firmware update to complete and for iLO to reboot
Caveat Firmware updates to BMC/iLO interfaces carry inherent risk; ensure valid backups and consider testing in non-production environment before applying to production systems

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

Fix this in Integrated Lights Out 4 Scoped from the published advisory
  • Consultation4.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,690
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-28083 — 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-28083 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