CVE-2023-26299 Vulnerability Analysis & Exploit Details

CVE-2023-26299
Vulnerability Scoring

7.0
/10
High Risk

If left unpatched, CVE-2023-26299 could lead to major system disruptions or data loss.

Attack Complexity Details

  • Attack Complexity: High
    Exploits require significant effort and special conditions.
  • Attack Vector: Local
    Vulnerability requires local system access.
  • Privileges Required: Low
    Some privileges are necessary to exploit the vulnerability.
  • Scope: Unchanged
    Exploit remains within the originally vulnerable component.
  • User Interaction: None
    No user interaction is necessary for exploitation.

CVE-2023-26299 Details

Status: Modified

Last updated: 🕢 21 Nov 2024, 07:51 UTC
Originally published on: 🕓 30 Jun 2023, 16:15 UTC

Time between publication and last update: 509 days

CVSS Release: version 3

CVSS3 Source

nvd@nist.gov

CVSS3 Type

Primary

CVSS3 Vector

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

CVE-2023-26299 Vulnerability Summary

CVE-2023-26299: A potential Time-of-Check to Time-of-Use (TOCTOU) vulnerability has been identified in certain HP PC products using AMI UEFI Firmware (system BIOS), which might allow arbitrary code execution. AMI has released updates to mitigate the potential vulnerability.

Assessing the Risk of CVE-2023-26299

Access Complexity Graph

The exploitability of CVE-2023-26299 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-2023-26299

This vulnerability, CVE-2023-26299, requires a high level of attack complexity and low privileges, making it difficult but not impossible to exploit. Organizations should ensure robust security configurations to mitigate risks.

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-2023-26299, 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-2023-26299, 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-2023-26299 can result in unauthorized access to sensitive data, severely compromising data privacy.
  • Integrity: High
    CVE-2023-26299 could allow unauthorized modifications to data, potentially affecting system reliability and trust.
  • Availability: High
    CVE-2023-26299 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.044% (probability of exploit)

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

CVE-2023-26299 References

External References

CWE Common Weakness Enumeration

CWE-367

CAPEC Common Attack Pattern Enumeration and Classification

  • Leveraging Race Conditions via Symbolic Links CAPEC-27 This attack leverages the use of symbolic links (Symlinks) in order to write to sensitive files. An attacker can create a Symlink link to a target file not otherwise accessible to them. When the privileged program tries to create a temporary file with the same name as the Symlink link, it will actually write to the target file pointed to by the attackers' Symlink link. If the attacker can insert malicious content in the temporary file they will be writing to the sensitive file by using the Symlink. The race occurs because the system checks if the temporary file exists, then creates the file. The attacker would typically create the Symlink during the interval between the check and the creation of the temporary file.
  • Leveraging Time-of-Check and Time-of-Use (TOCTOU) Race Conditions CAPEC-29 This attack targets a race condition occurring between the time of check (state) for a resource and the time of use of a resource. A typical example is file access. The adversary can leverage a file access race condition by "running the race", meaning that they would modify the resource between the first time the target program accesses the file and the time the target program uses the file. During that period of time, the adversary could replace or modify the file, causing the application to behave unexpectedly.

Vulnerable Configurations

  • cpe:2.3:o:hp:260_g4_desktop_mini_firmware:-:*:*:*:*:*:*:*
    cpe:2.3:o:hp:260_g4_desktop_mini_firmware:-:*:*:*:*:*:*:*
  • cpe:2.3:h:hp:260_g4_desktop_mini:-:*:*:*:*:*:*:*
    cpe:2.3:h:hp:260_g4_desktop_mini:-:*:*:*:*:*:*:*
  • cpe:2.3:h:hp:t430:-:*:*:*:*:*:*:*
    cpe:2.3:h:hp:t430:-:*:*:*:*:*:*:*
  • cpe:2.3:h:hp:t628:-:*:*:*:*:*:*:*
    cpe:2.3:h:hp:t628:-:*:*:*:*:*:*:*
  • cpe:2.3:h:hp:240_g10:-:*:*:*:*:*:*:*
    cpe:2.3:h:hp:240_g10:-:*:*:*:*:*:*:*
  • cpe:2.3:h:hp:245_g6:-:*:*:*:*:*:*:*
    cpe:2.3:h:hp:245_g6:-:*:*:*:*:*:*:*
  • cpe:2.3:h:hp:245_g7:-:*:*:*:*:*:*:*
    cpe:2.3:h:hp:245_g7:-:*:*:*:*:*:*:*
  • cpe:2.3:h:hp:245_g8:-:*:*:*:*:*:*:*
    cpe:2.3:h:hp:245_g8:-:*:*:*:*:*:*:*
  • cpe:2.3:h:hp:247_g8:-:*:*:*:*:*:*:*
    cpe:2.3:h:hp:247_g8:-:*:*:*:*:*:*:*
  • cpe:2.3:h:hp:250_g10:-:*:*:*:*:*:*:*
    cpe:2.3:h:hp:250_g10:-:*:*:*:*:*:*:*
  • cpe:2.3:h:hp:255_g10:-:*:*:*:*:*:*:*
    cpe:2.3:h:hp:255_g10:-:*:*:*:*:*:*:*
  • cpe:2.3:h:hp:349_g7:-:*:*:*:*:*:*:*
    cpe:2.3:h:hp:349_g7:-:*:*:*:*:*:*:*
  • cpe:2.3:h:hp:470_g10:-:*:*:*:*:*:*:*
    cpe:2.3:h:hp:470_g10:-:*:*:*:*:*:*:*
  • cpe:2.3:h:hp:470_g9:-:*:*:*:*:*:*:*
    cpe:2.3:h:hp:470_g9:-:*:*:*:*:*:*:*
  • cpe:2.3:h:hp:zhan_99_g2:-:*:*:*:*:*:*:*
    cpe:2.3:h:hp:zhan_99_g2:-:*:*:*:*:*:*:*
  • cpe:2.3:h:hp:zhan_99_g4:-:*:*:*:*:*:*:*
    cpe:2.3:h:hp:zhan_99_g4:-:*:*:*:*:*:*:*
  • cpe:2.3:h:hp:vr_backpack_g2:-:*:*:*:*:*:*:*
    cpe:2.3:h:hp:vr_backpack_g2:-:*:*:*:*:*:*:*
  • cpe:2.3:o:hp:200_g3_firmware:-:*:*:*:*:*:*:*
    cpe:2.3:o:hp:200_g3_firmware:-:*:*:*:*:*:*:*
  • cpe:2.3:h:hp:200_g3:-:*:*:*:*:*:*:*
    cpe:2.3:h:hp:200_g3:-:*:*:*:*:*:*:*
  • cpe:2.3:o:hp:200_g4_22_all-in-one_firmware:-:*:*:*:*:*:*:*
    cpe:2.3:o:hp:200_g4_22_all-in-one_firmware:-:*:*:*:*:*:*:*
  • cpe:2.3:h:hp:200_g4_22_all-in-one:-:*:*:*:*:*:*:*
    cpe:2.3:h:hp:200_g4_22_all-in-one:-:*:*:*:*:*:*:*
  • cpe:2.3:o:hp:200_pro_g4_22_all-in-one_firmware:-:*:*:*:*:*:*:*
    cpe:2.3:o:hp:200_pro_g4_22_all-in-one_firmware:-:*:*:*:*:*:*:*
  • cpe:2.3:h:hp:200_pro_g4_22_all-in-one:-:*:*:*:*:*:*:*
    cpe:2.3:h:hp:200_pro_g4_22_all-in-one:-:*:*:*:*:*:*:*
  • cpe:2.3:o:hp:205_g4_22_all-in-one_firmware:-:*:*:*:*:*:*:*
    cpe:2.3:o:hp:205_g4_22_all-in-one_firmware:-:*:*:*:*:*:*:*
  • cpe:2.3:h:hp:205_g4_22_all-in-one:-:*:*:*:*:*:*:*
    cpe:2.3:h:hp:205_g4_22_all-in-one:-:*:*:*:*:*:*:*
  • cpe:2.3:o:hp:205_pro_g4_22_all-in-one_firmware:-:*:*:*:*:*:*:*
    cpe:2.3:o:hp:205_pro_g4_22_all-in-one_firmware:-:*:*:*:*:*:*:*
  • cpe:2.3:h:hp:205_pro_g4_22_all-in-one:-:*:*:*:*:*:*:*
    cpe:2.3:h:hp:205_pro_g4_22_all-in-one:-:*:*:*:*:*:*:*
  • cpe:2.3:o:hp:280_g3_firmware:-:*:*:*:*:*:*:*
    cpe:2.3:o:hp:280_g3_firmware:-:*:*:*:*:*:*:*
  • cpe:2.3:h:hp:280_g3:-:*:*:*:*:*:*:*
    cpe:2.3:h:hp:280_g3:-:*:*:*:*:*:*:*
  • cpe:2.3:o:hp:280_g4_firmware:-:*:*:*:*:*:*:*
    cpe:2.3:o:hp:280_g4_firmware:-:*:*:*:*:*:*:*
  • cpe:2.3:h:hp:280_g4:-:*:*:*:*:*:*:*
    cpe:2.3:h:hp:280_g4:-:*:*:*:*:*:*:*
  • cpe:2.3:o:hp:280_g4_microtower_firmware:-:*:*:*:*:*:*:*
    cpe:2.3:o:hp:280_g4_microtower_firmware:-:*:*:*:*:*:*:*
  • cpe:2.3:h:hp:280_g4_microtower:-:*:*:*:*:*:*:*
    cpe:2.3:h:hp:280_g4_microtower:-:*:*:*:*:*:*:*
  • cpe:2.3:o:hp:280_g5_firmware:-:*:*:*:*:*:*:*
    cpe:2.3:o:hp:280_g5_firmware:-:*:*:*:*:*:*:*
  • cpe:2.3:h:hp:280_g5:-:*:*:*:*:*:*:*
    cpe:2.3:h:hp:280_g5:-:*:*:*:*:*:*:*
  • cpe:2.3:o:hp:280_g5_small_form_factor_firmware:-:*:*:*:*:*:*:*
    cpe:2.3:o:hp:280_g5_small_form_factor_firmware:-:*:*:*:*:*:*:*
  • cpe:2.3:h:hp:280_g5_small_form_factor:-:*:*:*:*:*:*:*
    cpe:2.3:h:hp:280_g5_small_form_factor:-:*:*:*:*:*:*:*
  • cpe:2.3:o:hp:280_g6_firmware:-:*:*:*:*:*:*:*
    cpe:2.3:o:hp:280_g6_firmware:-:*:*:*:*:*:*:*
  • cpe:2.3:h:hp:280_g6:-:*:*:*:*:*:*:*
    cpe:2.3:h:hp:280_g6:-:*:*:*:*:*:*:*
  • cpe:2.3:o:hp:280_g8_microtower_firmware:-:*:*:*:*:*:*:*
    cpe:2.3:o:hp:280_g8_microtower_firmware:-:*:*:*:*:*:*:*
  • cpe:2.3:h:hp:280_g8_microtower:-:*:*:*:*:*:*:*
    cpe:2.3:h:hp:280_g8_microtower:-:*:*:*:*:*:*:*
  • cpe:2.3:o:hp:280_pro_g3_firmware:-:*:*:*:*:*:*:*
    cpe:2.3:o:hp:280_pro_g3_firmware:-:*:*:*:*:*:*:*
  • cpe:2.3:h:hp:280_pro_g3:-:*:*:*:*:*:*:*
    cpe:2.3:h:hp:280_pro_g3:-:*:*:*:*:*:*:*
  • cpe:2.3:o:hp:280_pro_g4_microtower_firmware:-:*:*:*:*:*:*:*
    cpe:2.3:o:hp:280_pro_g4_microtower_firmware:-:*:*:*:*:*:*:*
  • cpe:2.3:h:hp:280_pro_g4_microtower:-:*:*:*:*:*:*:*
    cpe:2.3:h:hp:280_pro_g4_microtower:-:*:*:*:*:*:*:*
  • cpe:2.3:o:hp:280_pro_g5_small_form_factor_firmware:-:*:*:*:*:*:*:*
    cpe:2.3:o:hp:280_pro_g5_small_form_factor_firmware:-:*:*:*:*:*:*:*
  • cpe:2.3:h:hp:280_pro_g5_small_form_factor:-:*:*:*:*:*:*:*
    cpe:2.3:h:hp:280_pro_g5_small_form_factor:-:*:*:*:*:*:*:*
  • cpe:2.3:o:hp:282_g5_firmware:-:*:*:*:*:*:*:*
    cpe:2.3:o:hp:282_g5_firmware:-:*:*:*:*:*:*:*
  • cpe:2.3:h:hp:282_g5:-:*:*:*:*:*:*:*
    cpe:2.3:h:hp:282_g5:-:*:*:*:*:*:*:*
  • cpe:2.3:o:hp:282_g6_firmware:-:*:*:*:*:*:*:*
    cpe:2.3:o:hp:282_g6_firmware:-:*:*:*:*:*:*:*
  • cpe:2.3:h:hp:282_g6:-:*:*:*:*:*:*:*
    cpe:2.3:h:hp:282_g6:-:*:*:*:*:*:*:*
  • cpe:2.3:o:hp:282_pro_g4_microtower_firmware:-:*:*:*:*:*:*:*
    cpe:2.3:o:hp:282_pro_g4_microtower_firmware:-:*:*:*:*:*:*:*
  • cpe:2.3:h:hp:282_pro_g4_microtower:-:*:*:*:*:*:*:*
    cpe:2.3:h:hp:282_pro_g4_microtower:-:*:*:*:*:*:*:*
  • cpe:2.3:o:hp:288_g5_firmware:-:*:*:*:*:*:*:*
    cpe:2.3:o:hp:288_g5_firmware:-:*:*:*:*:*:*:*
  • cpe:2.3:h:hp:288_g5:-:*:*:*:*:*:*:*
    cpe:2.3:h:hp:288_g5:-:*:*:*:*:*:*:*
  • cpe:2.3:o:hp:288_g6_firmware:-:*:*:*:*:*:*:*
    cpe:2.3:o:hp:288_g6_firmware:-:*:*:*:*:*:*:*
  • cpe:2.3:h:hp:288_g6:-:*:*:*:*:*:*:*
    cpe:2.3:h:hp:288_g6:-:*:*:*:*:*:*:*
  • cpe:2.3:o:hp:288_pro_g4_microtower_firmware:-:*:*:*:*:*:*:*
    cpe:2.3:o:hp:288_pro_g4_microtower_firmware:-:*:*:*:*:*:*:*
  • cpe:2.3:h:hp:288_pro_g4_microtower:-:*:*:*:*:*:*:*
    cpe:2.3:h:hp:288_pro_g4_microtower:-:*:*:*:*:*:*:*
  • cpe:2.3:o:hp:290_g1_firmware:-:*:*:*:*:*:*:*
    cpe:2.3:o:hp:290_g1_firmware:-:*:*:*:*:*:*:*
  • cpe:2.3:h:hp:290_g1:-:*:*:*:*:*:*:*
    cpe:2.3:h:hp:290_g1:-:*:*:*:*:*:*:*
  • cpe:2.3:o:hp:290_g2_firmware:-:*:*:*:*:*:*:*
    cpe:2.3:o:hp:290_g2_firmware:-:*:*:*:*:*:*:*
  • cpe:2.3:h:hp:290_g2:-:*:*:*:*:*:*:*
    cpe:2.3:h:hp:290_g2:-:*:*:*:*:*:*:*
  • cpe:2.3:o:hp:290_g2_microtower_firmware:-:*:*:*:*:*:*:*
    cpe:2.3:o:hp:290_g2_microtower_firmware:-:*:*:*:*:*:*:*
  • cpe:2.3:h:hp:290_g2_microtower:-:*:*:*:*:*:*:*
    cpe:2.3:h:hp:290_g2_microtower:-:*:*:*:*:*:*:*
  • cpe:2.3:o:hp:290_g3_firmware:-:*:*:*:*:*:*:*
    cpe:2.3:o:hp:290_g3_firmware:-:*:*:*:*:*:*:*
  • cpe:2.3:h:hp:290_g3:-:*:*:*:*:*:*:*
    cpe:2.3:h:hp:290_g3:-:*:*:*:*:*:*:*
  • cpe:2.3:o:hp:290_g3_small_form_factor_firmware:-:*:*:*:*:*:*:*
    cpe:2.3:o:hp:290_g3_small_form_factor_firmware:-:*:*:*:*:*:*:*
  • cpe:2.3:h:hp:290_g3_small_form_factor:-:*:*:*:*:*:*:*
    cpe:2.3:h:hp:290_g3_small_form_factor:-:*:*:*:*:*:*:*
  • cpe:2.3:o:hp:290_g4_firmware:-:*:*:*:*:*:*:*
    cpe:2.3:o:hp:290_g4_firmware:-:*:*:*:*:*:*:*
  • cpe:2.3:h:hp:290_g4:-:*:*:*:*:*:*:*
    cpe:2.3:h:hp:290_g4:-:*:*:*:*:*:*:*
  • cpe:2.3:o:hp:desktop_pro_g1_microtower_firmware:-:*:*:*:*:*:*:*
    cpe:2.3:o:hp:desktop_pro_g1_microtower_firmware:-:*:*:*:*:*:*:*
  • cpe:2.3:h:hp:desktop_pro_g1_microtower:-:*:*:*:*:*:*:*
    cpe:2.3:h:hp:desktop_pro_g1_microtower:-:*:*:*:*:*:*:*
  • cpe:2.3:o:hp:pro_small_form_factor_280_g9_desktop_firmware:-:*:*:*:*:*:*:*
    cpe:2.3:o:hp:pro_small_form_factor_280_g9_desktop_firmware:-:*:*:*:*:*:*:*
  • cpe:2.3:h:hp:pro_small_form_factor_280_g9_desktop:-:*:*:*:*:*:*:*
    cpe:2.3:h:hp:pro_small_form_factor_280_g9_desktop:-:*:*:*:*:*:*:*
  • cpe:2.3:o:hp:pro_small_form_factor_290_g9_desktop_firmware:-:*:*:*:*:*:*:*
    cpe:2.3:o:hp:pro_small_form_factor_290_g9_desktop_firmware:-:*:*:*:*:*:*:*
  • cpe:2.3:h:hp:pro_small_form_factor_290_g9_desktop:-:*:*:*:*:*:*:*
    cpe:2.3:h:hp:pro_small_form_factor_290_g9_desktop:-:*:*:*:*:*:*:*
  • cpe:2.3:o:hp:pro_small_form_factor_zhan_66_g9_desktop_firmware:-:*:*:*:*:*:*:*
    cpe:2.3:o:hp:pro_small_form_factor_zhan_66_g9_desktop_firmware:-:*:*:*:*:*:*:*
  • cpe:2.3:h:hp:pro_small_form_factor_zhan_66_g9_desktop:-:*:*:*:*:*:*:*
    cpe:2.3:h:hp:pro_small_form_factor_zhan_66_g9_desktop:-:*:*:*:*:*:*:*
  • cpe:2.3:o:hp:pro_tower_200_g9_desktop_firmware:-:*:*:*:*:*:*:*
    cpe:2.3:o:hp:pro_tower_200_g9_desktop_firmware:-:*:*:*:*:*:*:*
  • cpe:2.3:h:hp:pro_tower_200_g9_desktop:-:*:*:*:*:*:*:*
    cpe:2.3:h:hp:pro_tower_200_g9_desktop:-:*:*:*:*:*:*:*
  • cpe:2.3:o:hp:pro_tower_280_g9_desktop_firmware:-:*:*:*:*:*:*:*
    cpe:2.3:o:hp:pro_tower_280_g9_desktop_firmware:-:*:*:*:*:*:*:*
  • cpe:2.3:h:hp:pro_tower_280_g9_desktop:-:*:*:*:*:*:*:*
    cpe:2.3:h:hp:pro_tower_280_g9_desktop:-:*:*:*:*:*:*:*
  • cpe:2.3:o:hp:pro_tower_290_g9_desktop_firmware:-:*:*:*:*:*:*:*
    cpe:2.3:o:hp:pro_tower_290_g9_desktop_firmware:-:*:*:*:*:*:*:*
  • cpe:2.3:h:hp:pro_tower_290_g9_desktop:-:*:*:*:*:*:*:*
    cpe:2.3:h:hp:pro_tower_290_g9_desktop:-:*:*:*:*:*:*:*
  • cpe:2.3:o:hp:pro_tower_zhan_99_g9_desktop_firmware:-:*:*:*:*:*:*:*
    cpe:2.3:o:hp:pro_tower_zhan_99_g9_desktop_firmware:-:*:*:*:*:*:*:*
  • cpe:2.3:h:hp:pro_tower_zhan_99_g9_desktop:-:*:*:*:*:*:*:*
    cpe:2.3:h:hp:pro_tower_zhan_99_g9_desktop:-:*:*:*:*:*:*:*
  • cpe:2.3:o:hp:proone_240_g10_firmware:-:*:*:*:*:*:*:*
    cpe:2.3:o:hp:proone_240_g10_firmware:-:*:*:*:*:*:*:*
  • cpe:2.3:h:hp:proone_240_g10:-:*:*:*:*:*:*:*
    cpe:2.3:h:hp:proone_240_g10:-:*:*:*:*:*:*:*
  • cpe:2.3:o:hp:proone_240_g9_firmware:-:*:*:*:*:*:*:*
    cpe:2.3:o:hp:proone_240_g9_firmware:-:*:*:*:*:*:*:*
  • cpe:2.3:h:hp:proone_240_g9:-:*:*:*:*:*:*:*
    cpe:2.3:h:hp:proone_240_g9:-:*:*:*:*:*:*:*
  • cpe:2.3:o:hp:proone_440_g3_firmware:-:*:*:*:*:*:*:*
    cpe:2.3:o:hp:proone_440_g3_firmware:-:*:*:*:*:*:*:*
  • cpe:2.3:h:hp:proone_440_g3:-:*:*:*:*:*:*:*
    cpe:2.3:h:hp:proone_440_g3:-:*:*:*:*:*:*:*
  • cpe:2.3:o:hp:proone_490_g3_firmware:-:*:*:*:*:*:*:*
    cpe:2.3:o:hp:proone_490_g3_firmware:-:*:*:*:*:*:*:*
  • cpe:2.3:h:hp:proone_490_g3:-:*:*:*:*:*:*:*
    cpe:2.3:h:hp:proone_490_g3:-:*:*:*:*:*:*:*
  • cpe:2.3:o:hp:proone_496_g3_firmware:-:*:*:*:*:*:*:*
    cpe:2.3:o:hp:proone_496_g3_firmware:-:*:*:*:*:*:*:*
  • cpe:2.3:h:hp:proone_496_g3:-:*:*:*:*:*:*:*
    cpe:2.3:h:hp:proone_496_g3:-:*:*:*:*:*:*:*
  • cpe:2.3:o:hp:z_vr_backpack_g1_workstation_firmware:-:*:*:*:*:*:*:*
    cpe:2.3:o:hp:z_vr_backpack_g1_workstation_firmware:-:*:*:*:*:*:*:*
  • cpe:2.3:h:hp:z_vr_backpack_g1_workstation:-:*:*:*:*:*:*:*
    cpe:2.3:h:hp:z_vr_backpack_g1_workstation:-:*:*:*:*:*:*:*
  • cpe:2.3:o:hp:zhan_86_pro_g2_microtower_firmware:-:*:*:*:*:*:*:*
    cpe:2.3:o:hp:zhan_86_pro_g2_microtower_firmware:-:*:*:*:*:*:*:*
  • cpe:2.3:h:hp:zhan_86_pro_g2_microtower:-:*:*:*:*:*:*:*
    cpe:2.3:h:hp:zhan_86_pro_g2_microtower:-:*:*:*:*:*:*:*
  • cpe:2.3:o:hp:zhan_99_pro_g1_microtower_firmware:-:*:*:*:*:*:*:*
    cpe:2.3:o:hp:zhan_99_pro_g1_microtower_firmware:-:*:*:*:*:*:*:*
  • cpe:2.3:h:hp:zhan_99_pro_g1_microtower:-:*:*:*:*:*:*:*
    cpe:2.3:h:hp:zhan_99_pro_g1_microtower:-:*:*:*:*:*:*:*

Protect Your Infrastructure against CVE-2023-26299: 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-26205 – Lua 5.4.7, when the debug library is used, has a out-of-bounds read and segmentation violation in mainpositionTV in ltable.c. NOTE: this is dispute...
  • CVE-2025-26204 – Lua 5.4.7, when the debug library is used, has a out-of-bounds read and segmentation violation in equalkey in ltable.c. NOTE: this is disputed beca...
  • 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...