CVE-2022-28639 Vulnerability Analysis & Exploit Details

CVE-2022-28639
Vulnerability Scoring

8.8
/10
Severe Risk

Cybersecurity professionals consider CVE-2022-28639 an immediate threat requiring urgent mitigation.

Attack Complexity Details

  • Attack Complexity: Low
    Exploits can be performed without significant complexity or special conditions.
  • Attack Vector: Adjacent_network
    Attack Vector Under Analysis
  • Privileges Required: None
    No privileges are required for exploitation.
  • Scope: Unchanged
    Exploit remains within the originally vulnerable component.
  • User Interaction: None
    No user interaction is necessary for exploitation.

CVE-2022-28639 Details

Status: Modified

Last updated: 🕡 21 Nov 2024, 06:57 UTC
Originally published on: 🕘 20 Sep 2022, 21:15 UTC

Time between publication and last update: 792 days

CVSS Release: version 3

CVSS3 Source

nvd@nist.gov

CVSS3 Type

Primary

CVSS3 Vector

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

CVE-2022-28639 Vulnerability Summary

CVE-2022-28639: 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.

Assessing the Risk of CVE-2022-28639

Access Complexity Graph

The exploitability of CVE-2022-28639 depends on two key factors: attack complexity (the level of effort required to execute an exploit) and privileges required (the access level an attacker needs).

Exploitability Analysis for CVE-2022-28639

With low attack complexity and no required privileges, CVE-2022-28639 is an easy target for cybercriminals. Organizations should prioritize immediate mitigation measures to prevent unauthorized access and data breaches.

Understanding AC and PR

A lower complexity and fewer privilege requirements make exploitation easier. Security teams should evaluate these aspects to determine the urgency of mitigation strategies, such as patch management and access control policies.

Attack Complexity (AC) measures the difficulty in executing an exploit. A high AC means that specific conditions must be met, making an attack more challenging, while a low AC means the vulnerability can be exploited with minimal effort.

Privileges Required (PR) determine the level of system access necessary for an attack. Vulnerabilities requiring no privileges are more accessible to attackers, whereas high privilege requirements limit exploitation to authorized users with elevated access.

CVSS Score Breakdown Chart

Above is the CVSS Sub-score Breakdown for CVE-2022-28639, illustrating how Base, Impact, and Exploitability factors combine to form the overall severity rating. A higher sub-score typically indicates a more severe or easier-to-exploit vulnerability.

CIA Impact Analysis

Below is the Impact Analysis for CVE-2022-28639, showing how Confidentiality, Integrity, and Availability might be affected if the vulnerability is exploited. Higher values usually signal greater potential damage.

  • Confidentiality: High
    Exploiting CVE-2022-28639 can result in unauthorized access to sensitive data, severely compromising data privacy.
  • Integrity: High
    CVE-2022-28639 could allow unauthorized modifications to data, potentially affecting system reliability and trust.
  • Availability: High
    CVE-2022-28639 can disrupt system operations, potentially causing complete denial of service (DoS).

Exploit Prediction Scoring System (EPSS)

The EPSS score estimates the probability that this vulnerability will be exploited in the near future.

EPSS Score: 0.065% (probability of exploit)

EPSS Percentile: 31.42% (lower percentile = lower relative risk)
This vulnerability is less risky than approximately 68.58% of others.

CVE-2022-28639 References

External References

CWE Common Weakness Enumeration

NVD-CWE-noinfo

Vulnerable Configurations

  • cpe:2.3:o:hpe:integrated_lights-out_5_firmware:-:*:*:*:*:*:*:*
    cpe:2.3:o:hpe:integrated_lights-out_5_firmware:-:*:*:*:*:*:*:*
  • cpe:2.3:o:hpe:integrated_lights-out_5_firmware:2.63:*:*:*:*:*:*:*
    cpe:2.3:o:hpe:integrated_lights-out_5_firmware:2.63:*:*:*:*:*:*:*
  • cpe:2.3:o:hpe:integrated_lights-out_5_firmware:2.71:*:*:*:*:*:*:*
    cpe:2.3:o:hpe:integrated_lights-out_5_firmware:2.71:*:*:*:*:*:*:*
  • cpe:2.3:h:hp:apollo_4200_gen10_server:-:*:*:*:*:*:*:*
    cpe:2.3:h:hp:apollo_4200_gen10_server:-:*:*:*:*:*:*:*
  • cpe:2.3:h:hp:apollo_4500:-:*:*:*:*:*:*:*
    cpe:2.3:h:hp:apollo_4500:-:*:*:*:*:*:*:*
  • cpe:2.3:h:hp:apollo_r2000_chassis:-:*:*:*:*:*:*:*
    cpe:2.3:h:hp:apollo_r2000_chassis:-:*:*:*:*:*:*:*
  • cpe:2.3:h:hpe:apollo_2000_gen10_plus_system:-:*:*:*:*:*:*:*
    cpe:2.3:h:hpe:apollo_2000_gen10_plus_system:-:*:*:*:*:*:*:*
  • cpe:2.3:h:hpe:apollo_4200_gen10_plus_system:-:*:*:*:*:*:*:*
    cpe:2.3:h:hpe:apollo_4200_gen10_plus_system:-:*:*:*:*:*:*:*
  • cpe:2.3:h:hpe:apollo_4510_gen10_system:-:*:*:*:*:*:*:*
    cpe:2.3:h:hpe:apollo_4510_gen10_system:-:*:*:*:*:*:*:*
  • cpe:2.3:h:hpe:apollo_6500_gen10_plus:-:*:*:*:*:*:*:*
    cpe:2.3:h:hpe:apollo_6500_gen10_plus:-:*:*:*:*:*:*:*
  • cpe:2.3:h:hpe:apollo_n2600_gen10_plus:-:*:*:*:*:*:*:*
    cpe:2.3:h:hpe:apollo_n2600_gen10_plus:-:*:*:*:*:*:*:*
  • cpe:2.3:h:hpe:apollo_n2800_gen10_plus:-:*:*:*:*:*:*:*
    cpe:2.3:h:hpe:apollo_n2800_gen10_plus:-:*:*:*:*:*:*:*
  • cpe:2.3:h:hpe:apollo_r2600_gen10:-:*:*:*:*:*:*:*
    cpe:2.3:h:hpe:apollo_r2600_gen10:-:*:*:*:*:*:*:*
  • cpe:2.3:h:hpe:apollo_r2800_gen10:-:*:*:*:*:*:*:*
    cpe:2.3:h:hpe:apollo_r2800_gen10:-:*:*:*:*:*:*:*
  • cpe:2.3:h:hpe:edgeline_e920_server_blade:-:*:*:*:*:*:*:*
    cpe:2.3:h:hpe:edgeline_e920_server_blade:-:*:*:*:*:*:*:*
  • cpe:2.3:h:hpe:edgeline_e920d_server_blade:-:*:*:*:*:*:*:*
    cpe:2.3:h:hpe:edgeline_e920d_server_blade:-:*:*:*:*:*:*:*
  • cpe:2.3:h:hpe:edgeline_e920t_server_blade:-:*:*:*:*:*:*:*
    cpe:2.3:h:hpe:edgeline_e920t_server_blade:-:*:*:*:*:*:*:*
  • cpe:2.3:h:hpe:integrated_lights-out_5:-:*:*:*:*:*:*:*
    cpe:2.3:h:hpe:integrated_lights-out_5:-:*:*:*:*:*:*:*
  • cpe:2.3:h:hpe:proliant_bl460c_gen10_server_blade:-:*:*:*:*:*:*:*
    cpe:2.3:h:hpe:proliant_bl460c_gen10_server_blade:-:*:*:*:*:*:*:*
  • cpe:2.3:h:hpe:proliant_dl110_gen10_plus_telco_server:-:*:*:*:*:*:*:*
    cpe:2.3:h:hpe:proliant_dl110_gen10_plus_telco_server:-:*:*:*:*:*:*:*
  • cpe:2.3:h:hpe:proliant_dl160_gen10_server:-:*:*:*:*:*:*:*
    cpe:2.3:h:hpe:proliant_dl160_gen10_server:-:*:*:*:*:*:*:*
  • cpe:2.3:h:hpe:proliant_dl180_gen10_server:-:*:*:*:*:*:*:*
    cpe:2.3:h:hpe:proliant_dl180_gen10_server:-:*:*:*:*:*:*:*
  • cpe:2.3:h:hpe:proliant_dl20_gen10_plus_server:-:*:*:*:*:*:*:*
    cpe:2.3:h:hpe:proliant_dl20_gen10_plus_server:-:*:*:*:*:*:*:*
  • cpe:2.3:h:hpe:proliant_dl20_gen10_server:-:*:*:*:*:*:*:*
    cpe:2.3:h:hpe:proliant_dl20_gen10_server:-:*:*:*:*:*:*:*
  • cpe:2.3:h:hpe:proliant_dl325_gen10_plus_server:-:*:*:*:*:*:*:*
    cpe:2.3:h:hpe:proliant_dl325_gen10_plus_server:-:*:*:*:*:*:*:*
  • cpe:2.3:h:hpe:proliant_dl325_gen10_plus_v2_server:-:*:*:*:*:*:*:*
    cpe:2.3:h:hpe:proliant_dl325_gen10_plus_v2_server:-:*:*:*:*:*:*:*
  • cpe:2.3:h:hpe:proliant_dl325_gen10_server:-:*:*:*:*:*:*:*
    cpe:2.3:h:hpe:proliant_dl325_gen10_server:-:*:*:*:*:*:*:*
  • cpe:2.3:h:hpe:proliant_dl345_gen10_plus_server:-:*:*:*:*:*:*:*
    cpe:2.3:h:hpe:proliant_dl345_gen10_plus_server:-:*:*:*:*:*:*:*
  • cpe:2.3:h:hpe:proliant_dl360_gen10_plus_server:-:*:*:*:*:*:*:*
    cpe:2.3:h:hpe:proliant_dl360_gen10_plus_server:-:*:*:*:*:*:*:*
  • cpe:2.3:h:hpe:proliant_dl360_gen10_server:-:*:*:*:*:*:*:*
    cpe:2.3:h:hpe:proliant_dl360_gen10_server:-:*:*:*:*:*:*:*
  • cpe:2.3:h:hpe:proliant_dl365_gen10_plus_server:-:*:*:*:*:*:*:*
    cpe:2.3:h:hpe:proliant_dl365_gen10_plus_server:-:*:*:*:*:*:*:*
  • cpe:2.3:h:hpe:proliant_dl380_gen10_plus_server:-:*:*:*:*:*:*:*
    cpe:2.3:h:hpe:proliant_dl380_gen10_plus_server:-:*:*:*:*:*:*:*
  • cpe:2.3:h:hpe:proliant_dl380_gen10_server:-:*:*:*:*:*:*:*
    cpe:2.3:h:hpe:proliant_dl380_gen10_server:-:*:*:*:*:*:*:*
  • cpe:2.3:h:hpe:proliant_dl385_gen10_plus_server:-:*:*:*:*:*:*:*
    cpe:2.3:h:hpe:proliant_dl385_gen10_plus_server:-:*:*:*:*:*:*:*
  • cpe:2.3:h:hpe:proliant_dl385_gen10_plus_v2_server:-:*:*:*:*:*:*:*
    cpe:2.3:h:hpe:proliant_dl385_gen10_plus_v2_server:-:*:*:*:*:*:*:*
  • cpe:2.3:h:hpe:proliant_dl385_gen10_server:-:*:*:*:*:*:*:*
    cpe:2.3:h:hpe:proliant_dl385_gen10_server:-:*:*:*:*:*:*:*
  • cpe:2.3:h:hpe:proliant_dl560_gen10_server:-:*:*:*:*:*:*:*
    cpe:2.3:h:hpe:proliant_dl560_gen10_server:-:*:*:*:*:*:*:*
  • cpe:2.3:h:hpe:proliant_dl580_gen10_server:-:*:*:*:*:*:*:*
    cpe:2.3:h:hpe:proliant_dl580_gen10_server:-:*:*:*:*:*:*:*
  • cpe:2.3:h:hpe:proliant_dx170r_gen10_server:-:*:*:*:*:*:*:*
    cpe:2.3:h:hpe:proliant_dx170r_gen10_server:-:*:*:*:*:*:*:*
  • cpe:2.3:h:hpe:proliant_dx190r_gen10_server:-:*:*:*:*:*:*:*
    cpe:2.3:h:hpe:proliant_dx190r_gen10_server:-:*:*:*:*:*:*:*
  • cpe:2.3:h:hpe:proliant_dx220n_gen10_plus_server:-:*:*:*:*:*:*:*
    cpe:2.3:h:hpe:proliant_dx220n_gen10_plus_server:-:*:*:*:*:*:*:*
  • cpe:2.3:h:hpe:proliant_dx325_gen10_plus_v2_server:-:*:*:*:*:*:*:*
    cpe:2.3:h:hpe:proliant_dx325_gen10_plus_v2_server:-:*:*:*:*:*:*:*
  • cpe:2.3:h:hpe:proliant_dx360_gen10_plus_server:-:*:*:*:*:*:*:*
    cpe:2.3:h:hpe:proliant_dx360_gen10_plus_server:-:*:*:*:*:*:*:*
  • cpe:2.3:h:hpe:proliant_dx360_gen10_server:-:*:*:*:*:*:*:*
    cpe:2.3:h:hpe:proliant_dx360_gen10_server:-:*:*:*:*:*:*:*
  • cpe:2.3:h:hpe:proliant_dx380_gen10_plus_server:-:*:*:*:*:*:*:*
    cpe:2.3:h:hpe:proliant_dx380_gen10_plus_server:-:*:*:*:*:*:*:*
  • cpe:2.3:h:hpe:proliant_dx380_gen10_server:-:*:*:*:*:*:*:*
    cpe:2.3:h:hpe:proliant_dx380_gen10_server:-:*:*:*:*:*:*:*
  • cpe:2.3:h:hpe:proliant_dx385_gen10_plus_server:-:*:*:*:*:*:*:*
    cpe:2.3:h:hpe:proliant_dx385_gen10_plus_server:-:*:*:*:*:*:*:*
  • cpe:2.3:h:hpe:proliant_dx385_gen10_plus_v2_server:-:*:*:*:*:*:*:*
    cpe:2.3:h:hpe:proliant_dx385_gen10_plus_v2_server:-:*:*:*:*:*:*:*
  • cpe:2.3:h:hpe:proliant_dx4200_gen10_server:-:*:*:*:*:*:*:*
    cpe:2.3:h:hpe:proliant_dx4200_gen10_server:-:*:*:*:*:*:*:*
  • cpe:2.3:h:hpe:proliant_dx560_gen10_server:-:*:*:*:*:*:*:*
    cpe:2.3:h:hpe:proliant_dx560_gen10_server:-:*:*:*:*:*:*:*
  • cpe:2.3:h:hpe:proliant_e910_server_blade:-:*:*:*:*:*:*:*
    cpe:2.3:h:hpe:proliant_e910_server_blade:-:*:*:*:*:*:*:*
  • cpe:2.3:h:hpe:proliant_e910t_server_blade:-:*:*:*:*:*:*:*
    cpe:2.3:h:hpe:proliant_e910t_server_blade:-:*:*:*:*:*:*:*
  • cpe:2.3:h:hpe:proliant_m750_server_blade:-:*:*:*:*:*:*:*
    cpe:2.3:h:hpe:proliant_m750_server_blade:-:*:*:*:*:*:*:*
  • cpe:2.3:h:hpe:proliant_microserver_gen10_plus:-:*:*:*:*:*:*:*
    cpe:2.3:h:hpe:proliant_microserver_gen10_plus:-:*:*:*:*:*:*:*
  • cpe:2.3:h:hpe:proliant_ml110_gen10_server:-:*:*:*:*:*:*:*
    cpe:2.3:h:hpe:proliant_ml110_gen10_server:-:*:*:*:*:*:*:*
  • cpe:2.3:h:hpe:proliant_ml30_gen10_plus_server:-:*:*:*:*:*:*:*
    cpe:2.3:h:hpe:proliant_ml30_gen10_plus_server:-:*:*:*:*:*:*:*
  • cpe:2.3:h:hpe:proliant_ml30_gen10_server:-:*:*:*:*:*:*:*
    cpe:2.3:h:hpe:proliant_ml30_gen10_server:-:*:*:*:*:*:*:*
  • cpe:2.3:h:hpe:proliant_ml350_gen10_server:-:*:*:*:*:*:*:*
    cpe:2.3:h:hpe:proliant_ml350_gen10_server:-:*:*:*:*:*:*:*
  • cpe:2.3:h:hpe:proliant_xl170r_gen10_server:-:*:*:*:*:*:*:*
    cpe:2.3:h:hpe:proliant_xl170r_gen10_server:-:*:*:*:*:*:*:*
  • cpe:2.3:h:hpe:proliant_xl190r_gen10_server:-:*:*:*:*:*:*:*
    cpe:2.3:h:hpe:proliant_xl190r_gen10_server:-:*:*:*:*:*:*:*
  • cpe:2.3:h:hpe:proliant_xl220n_gen10_plus_server:-:*:*:*:*:*:*:*
    cpe:2.3:h:hpe:proliant_xl220n_gen10_plus_server:-:*:*:*:*:*:*:*
  • cpe:2.3:h:hpe:proliant_xl225n_gen10_plus_1u_node:-:*:*:*:*:*:*:*
    cpe:2.3:h:hpe:proliant_xl225n_gen10_plus_1u_node:-:*:*:*:*:*:*:*
  • cpe:2.3:h:hpe:proliant_xl230k_gen10_server:-:*:*:*:*:*:*:*
    cpe:2.3:h:hpe:proliant_xl230k_gen10_server:-:*:*:*:*:*:*:*
  • cpe:2.3:h:hpe:proliant_xl270d_gen10_server:-:*:*:*:*:*:*:*
    cpe:2.3:h:hpe:proliant_xl270d_gen10_server:-:*:*:*:*:*:*:*
  • cpe:2.3:h:hpe:proliant_xl290n_gen10_plus_server:-:*:*:*:*:*:*:*
    cpe:2.3:h:hpe:proliant_xl290n_gen10_plus_server:-:*:*:*:*:*:*:*
  • cpe:2.3:h:hpe:proliant_xl420_gen10_server:-:*:*:*:*:*:*:*
    cpe:2.3:h:hpe:proliant_xl420_gen10_server:-:*:*:*:*:*:*:*
  • cpe:2.3:h:hpe:proliant_xl450_gen10_server:-:*:*:*:*:*:*:*
    cpe:2.3:h:hpe:proliant_xl450_gen10_server:-:*:*:*:*:*:*:*
  • cpe:2.3:h:hpe:proliant_xl645d_gen10_plus_server:-:*:*:*:*:*:*:*
    cpe:2.3:h:hpe:proliant_xl645d_gen10_plus_server:-:*:*:*:*:*:*:*
  • cpe:2.3:h:hpe:proliant_xl675d_gen10_plus_server:-:*:*:*:*:*:*:*
    cpe:2.3:h:hpe:proliant_xl675d_gen10_plus_server:-:*:*:*:*:*:*:*
  • cpe:2.3:h:hpe:proliant_xl925g_gen10_plus_1u_4-node_configure-to-order_server:-:*:*:*:*:*:*:*
    cpe:2.3:h:hpe:proliant_xl925g_gen10_plus_1u_4-node_configure-to-order_server:-:*:*:*:*:*:*:*
  • cpe:2.3:h:hpe:storage_file_controller:-:*:*:*:*:*:*:*
    cpe:2.3:h:hpe:storage_file_controller:-:*:*:*:*:*:*:*
  • cpe:2.3:h:hpe:storage_performance_file_controller:-:*:*:*:*:*:*:*
    cpe:2.3:h:hpe:storage_performance_file_controller:-:*:*:*:*:*:*:*
  • cpe:2.3:h:hpe:storeeasy_1460_storage:-:*:*:*:*:*:*:*
    cpe:2.3:h:hpe:storeeasy_1460_storage:-:*:*:*:*:*:*:*
  • cpe:2.3:h:hpe:storeeasy_1560_storage:-:*:*:*:*:*:*:*
    cpe:2.3:h:hpe:storeeasy_1560_storage:-:*:*:*:*:*:*:*
  • cpe:2.3:h:hpe:storeeasy_1660_expanded_storage:-:*:*:*:*:*:*:*
    cpe:2.3:h:hpe:storeeasy_1660_expanded_storage:-:*:*:*:*:*:*:*
  • cpe:2.3:h:hpe:storeeasy_1660_performance_storage:-:*:*:*:*:*:*:*
    cpe:2.3:h:hpe:storeeasy_1660_performance_storage:-:*:*:*:*:*:*:*
  • cpe:2.3:h:hpe:storeeasy_1660_storage:-:*:*:*:*:*:*:*
    cpe:2.3:h:hpe:storeeasy_1660_storage:-:*:*:*:*:*:*:*
  • cpe:2.3:h:hpe:storeeasy_1860_performance_storage:-:*:*:*:*:*:*:*
    cpe:2.3:h:hpe:storeeasy_1860_performance_storage:-:*:*:*:*:*:*:*
  • cpe:2.3:h:hpe:storeeasy_1860_storage:-:*:*:*:*:*:*:*
    cpe:2.3:h:hpe:storeeasy_1860_storage:-:*:*:*:*:*:*:*

Protect Your Infrastructure against CVE-2022-28639: Combat Critical CVE Threats

Stay updated with real-time CVE vulnerabilities and take action to secure your systems. Enhance your cybersecurity posture with the latest threat intelligence and mitigation techniques. Develop the skills necessary to defend against CVEs and secure critical infrastructures. Join the top cybersecurity professionals safeguarding today's infrastructures.

Other 5 Recently Published CVEs Vulnerabilities

  • CVE-2025-2129 – A vulnerability was found in Mage AI 0.9.75. It has been classified as problematic. This affects an unknown part. The manipulation leads to insecur...
  • CVE-2025-2127 – A vulnerability was found in JoomlaUX JUX Real Estate 3.4.0 on Joomla. It has been classified as problematic. Affected is an unknown function of th...
  • CVE-2025-2126 – A vulnerability was found in JoomlaUX JUX Real Estate 3.4.0 on Joomla and classified as critical. This issue affects some unknown processing of the...
  • CVE-2025-2125 – A vulnerability has been found in Control iD RH iD 25.2.25.0 and classified as problematic. This vulnerability affects unknown code of the file /v2...
  • CVE-2025-2124 – A vulnerability, which was classified as problematic, was found in Control iD RH iD 25.2.25.0. This affects an unknown part of the file /v2/custome...