LiveActive security incident?Get immediate response
CVE Record

CVE-2022-28639: A remote potential adjacent denial of service (DoS) and potential adjacent arbitrary code execution vulnera...

A remote potential adjacent denial of service (DoS) and potential adjacent arbitrary code execution vulnerability that could potentially lead to a loss of confidentiality, integrity, and availability were discovered in HPE Integrated Lights-Out 5 (iLO 5) in Version: 2.71. Hewlett Packard Enterprise has provided updated firmware for HPE Integrated Lights-Out 5 (iLO 5) that addresses these security vulnerabilities.

HighCVSS 8.8Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

CVE-2022-28639 affects HPE Integrated Lights-Out 5 firmware before 2.72. An unauthenticated attacker with adjacent network access could potentially crash the management controller or execute code, threatening server management confidentiality, integrity, and availability.

Executive priority

High priority for infrastructure teams. iLO controls server management functions, so compromise or disruption can affect recovery, operations, and platform trust even when host operating systems are patched.

Technical view

The CVSS 3.1 vector is AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H, scored 8.8. Sources describe potential adjacent denial of service and arbitrary code execution in HPE iLO 5 version 2.71 and earlier, associated with CWE-400.

Likely exposure

Organizations using HPE servers with iLO 5 firmware prior to 2.72 are the exposed population. Risk is highest where iLO management interfaces are reachable from shared, poorly segmented, or broadly accessible adjacent networks.

Exploitation context

The provided sources do not report active exploitation, and the CVE is not marked as CISA KEV. Treat exploitation status as unconfirmed, while prioritizing remediation because the vulnerability is unauthenticated and has high confidentiality, integrity, and availability impact.

Researcher notes

Evidence is limited to the CVE record and HPE advisory reference. The CVSS adjacent-network vector is important for scoping, but the potential code execution impact warrants treating reachable management networks as sensitive.

Mitigation direction

  • Upgrade HPE iLO 5 firmware to version 2.72 or later.
  • Use HPE’s advisory to obtain current firmware and installation guidance.
  • Prioritize iLO 5 version 2.71 and earlier in remediation queues.
  • Track remediation completion across all HPE server management controllers.

Validation and detection

  • Inventory HPE iLO 5 devices and record firmware versions.
  • Flag iLO 5 firmware prior to 2.72 as affected.
  • Confirm whether iLO interfaces are reachable from adjacent or shared networks.
  • Recheck HPE advisory for any newer vendor guidance.
Prepared
Confidence
high
Sources
3

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · low confidence lookup

CWE-400: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
description · low confidence lookup

Execution behavior lookup

The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2022-28639 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
High
CVSS
8.8 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
2Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
8.8CVSS 3.1HighCVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H2.85.9Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

8.8High
CVSS 3.1 vector shape for CVE-2022-28639Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/aHPE Integrated Lights-Out 5 (iLO 5)Prior to 2.72, unspecifiedListed
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-400 · source CWE mapping

Uncontrolled Resource Consumption

Uncontrolled Resource Consumption represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.