CVE-2022-31477 Vulnerability Analysis & Exploit Details

CVE-2022-31477
Vulnerability Scoring

4.0
/10
Moderate Risk

Exploiting CVE-2022-31477 requires specific conditions, leading to a moderate security impact.

Attack Complexity Details

  • Attack Complexity: High
    Exploits require significant effort and special conditions.
  • Attack Vector: Local
    Vulnerability requires local system access.
  • Privileges Required: High
    High-level privileges are required for exploitation.
  • Scope: Unchanged
    Exploit remains within the originally vulnerable component.
  • User Interaction: Required
    User interaction is necessary for successful exploitation.

CVE-2022-31477 Details

Status: Modified

Last updated: 🕖 21 Nov 2024, 07:04 UTC
Originally published on: 🕑 10 May 2023, 14:15 UTC

Time between publication and last update: 560 days

CVSS Release: version 3

CVSS3 Source

secure@intel.com

CVSS3 Type

Secondary

CVSS3 Vector

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

CVE-2022-31477 Vulnerability Summary

CVE-2022-31477: Improper initialization for some Intel(R) NUC BIOS firmware may allow a privileged user to potentially enable information disclosure via local access.

Assessing the Risk of CVE-2022-31477

Access Complexity Graph

The exploitability of CVE-2022-31477 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-31477

The exploitability of CVE-2022-31477 is influenced by multiple factors. Security teams should analyze system configurations and apply appropriate countermeasures to mitigate threats.

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-31477, 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-31477, 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-31477 can result in unauthorized access to sensitive data, severely compromising data privacy.
  • Integrity: None
    CVE-2022-31477 poses no threat to data integrity.
  • Availability: None
    CVE-2022-31477 does not impact system availability.

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.45% (lower percentile = lower relative risk)
This vulnerability is less risky than approximately 84.55% of others.

CVE-2022-31477 References

External References

CWE Common Weakness Enumeration

CWE-665

CAPEC Common Attack Pattern Enumeration and Classification

  • Leveraging Race Conditions CAPEC-26 The adversary targets a race condition occurring when multiple processes access and manipulate the same resource concurrently, and the outcome of the execution depends on the particular order in which the access takes place. The adversary can leverage a race condition by "running the race", modifying the resource and modifying the normal execution flow. For instance, a race condition can occur while accessing a file: the adversary can trick the system by replacing the original file with their version and cause the system to read the malicious 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:intel:nuc11pahi3_firmware:-:*:*:*:*:*:*:*
    cpe:2.3:o:intel:nuc11pahi3_firmware:-:*:*:*:*:*:*:*
  • cpe:2.3:h:intel:nuc11pahi3:-:*:*:*:*:*:*:*
    cpe:2.3:h:intel:nuc11pahi3:-:*:*:*:*:*:*:*
  • cpe:2.3:o:intel:nuc11pahi30z_firmware:-:*:*:*:*:*:*:*
    cpe:2.3:o:intel:nuc11pahi30z_firmware:-:*:*:*:*:*:*:*
  • cpe:2.3:h:intel:nuc11pahi30z:-:*:*:*:*:*:*:*
    cpe:2.3:h:intel:nuc11pahi30z:-:*:*:*:*:*:*:*
  • cpe:2.3:o:intel:nuc11paki3_firmware:-:*:*:*:*:*:*:*
    cpe:2.3:o:intel:nuc11paki3_firmware:-:*:*:*:*:*:*:*
  • cpe:2.3:h:intel:nuc11paki3:-:*:*:*:*:*:*:*
    cpe:2.3:h:intel:nuc11paki3:-:*:*:*:*:*:*:*
  • cpe:2.3:o:intel:nuc11pahi5_firmware:-:*:*:*:*:*:*:*
    cpe:2.3:o:intel:nuc11pahi5_firmware:-:*:*:*:*:*:*:*
  • cpe:2.3:h:intel:nuc11pahi5:-:*:*:*:*:*:*:*
    cpe:2.3:h:intel:nuc11pahi5:-:*:*:*:*:*:*:*
  • cpe:2.3:o:intel:nuc11pahi50z_firmware:-:*:*:*:*:*:*:*
    cpe:2.3:o:intel:nuc11pahi50z_firmware:-:*:*:*:*:*:*:*
  • cpe:2.3:h:intel:nuc11pahi50z:-:*:*:*:*:*:*:*
    cpe:2.3:h:intel:nuc11pahi50z:-:*:*:*:*:*:*:*
  • cpe:2.3:o:intel:nuc11paki5_firmware:-:*:*:*:*:*:*:*
    cpe:2.3:o:intel:nuc11paki5_firmware:-:*:*:*:*:*:*:*
  • cpe:2.3:h:intel:nuc11paki5:-:*:*:*:*:*:*:*
    cpe:2.3:h:intel:nuc11paki5:-:*:*:*:*:*:*:*
  • cpe:2.3:o:intel:nuc11paqi50wa_firmware:-:*:*:*:*:*:*:*
    cpe:2.3:o:intel:nuc11paqi50wa_firmware:-:*:*:*:*:*:*:*
  • cpe:2.3:h:intel:nuc11paqi50wa:-:*:*:*:*:*:*:*
    cpe:2.3:h:intel:nuc11paqi50wa:-:*:*:*:*:*:*:*
  • cpe:2.3:o:intel:nuc11pahi7_firmware:-:*:*:*:*:*:*:*
    cpe:2.3:o:intel:nuc11pahi7_firmware:-:*:*:*:*:*:*:*
  • cpe:2.3:h:intel:nuc11pahi7:-:*:*:*:*:*:*:*
    cpe:2.3:h:intel:nuc11pahi7:-:*:*:*:*:*:*:*
  • cpe:2.3:o:intel:nuc11pahi70z_firmware:-:*:*:*:*:*:*:*
    cpe:2.3:o:intel:nuc11pahi70z_firmware:-:*:*:*:*:*:*:*
  • cpe:2.3:h:intel:nuc11pahi70z:-:*:*:*:*:*:*:*
    cpe:2.3:h:intel:nuc11pahi70z:-:*:*:*:*:*:*:*
  • cpe:2.3:o:intel:nuc11paki7_firmware:-:*:*:*:*:*:*:*
    cpe:2.3:o:intel:nuc11paki7_firmware:-:*:*:*:*:*:*:*
  • cpe:2.3:h:intel:nuc11paki7:-:*:*:*:*:*:*:*
    cpe:2.3:h:intel:nuc11paki7:-:*:*:*:*:*:*:*
  • cpe:2.3:o:intel:nuc11paqi70qa_firmware:-:*:*:*:*:*:*:*
    cpe:2.3:o:intel:nuc11paqi70qa_firmware:-:*:*:*:*:*:*:*
  • cpe:2.3:h:intel:nuc11paqi70qa:-:*:*:*:*:*:*:*
    cpe:2.3:h:intel:nuc11paqi70qa:-:*:*:*:*:*:*:*
  • cpe:2.3:o:intel:cm11ebi38w_firmware:-:*:*:*:*:*:*:*
    cpe:2.3:o:intel:cm11ebi38w_firmware:-:*:*:*:*:*:*:*
  • cpe:2.3:h:intel:cm11ebi38w:-:*:*:*:*:*:*:*
    cpe:2.3:h:intel:cm11ebi38w:-:*:*:*:*:*:*:*
  • cpe:2.3:o:intel:cm11ebi58w_firmware:-:*:*:*:*:*:*:*
    cpe:2.3:o:intel:cm11ebi58w_firmware:-:*:*:*:*:*:*:*
  • cpe:2.3:h:intel:cm11ebi58w:-:*:*:*:*:*:*:*
    cpe:2.3:h:intel:cm11ebi58w:-:*:*:*:*:*:*:*
  • cpe:2.3:o:intel:cm11ebi716w_firmware:-:*:*:*:*:*:*:*
    cpe:2.3:o:intel:cm11ebi716w_firmware:-:*:*:*:*:*:*:*
  • cpe:2.3:h:intel:cm11ebi716w:-:*:*:*:*:*:*:*
    cpe:2.3:h:intel:cm11ebi716w:-:*:*:*:*:*:*:*
  • cpe:2.3:o:intel:cm11ebc4w_firmware:-:*:*:*:*:*:*:*
    cpe:2.3:o:intel:cm11ebc4w_firmware:-:*:*:*:*:*:*:*
  • cpe:2.3:h:intel:cm11ebc4w:-:*:*:*:*:*:*:*
    cpe:2.3:h:intel:cm11ebc4w:-:*:*:*:*:*:*:*
  • cpe:2.3:o:intel:lapbc510_firmware:-:*:*:*:*:*:*:*
    cpe:2.3:o:intel:lapbc510_firmware:-:*:*:*:*:*:*:*
  • cpe:2.3:h:intel:lapbc510:-:*:*:*:*:*:*:*
    cpe:2.3:h:intel:lapbc510:-:*:*:*:*:*:*:*
  • cpe:2.3:o:intel:lapbc710_firmware:-:*:*:*:*:*:*:*
    cpe:2.3:o:intel:lapbc710_firmware:-:*:*:*:*:*:*:*
  • cpe:2.3:h:intel:lapbc710:-:*:*:*:*:*:*:*
    cpe:2.3:h:intel:lapbc710:-:*:*:*:*:*:*:*
  • cpe:2.3:o:intel:lapkc51e_firmware:-:*:*:*:*:*:*:*
    cpe:2.3:o:intel:lapkc51e_firmware:-:*:*:*:*:*:*:*
  • cpe:2.3:h:intel:lapkc51e:-:*:*:*:*:*:*:*
    cpe:2.3:h:intel:lapkc51e:-:*:*:*:*:*:*:*
  • cpe:2.3:o:intel:lapkc71e_firmware:-:*:*:*:*:*:*:*
    cpe:2.3:o:intel:lapkc71e_firmware:-:*:*:*:*:*:*:*
  • cpe:2.3:h:intel:lapkc71e:-:*:*:*:*:*:*:*
    cpe:2.3:h:intel:lapkc71e:-:*:*:*:*:*:*:*
  • cpe:2.3:o:intel:lapkc71f_firmware:-:*:*:*:*:*:*:*
    cpe:2.3:o:intel:lapkc71f_firmware:-:*:*:*:*:*:*:*
  • cpe:2.3:h:intel:lapkc71f:-:*:*:*:*:*:*:*
    cpe:2.3:h:intel:lapkc71f:-:*:*:*:*:*:*:*
  • cpe:2.3:o:intel:nuc11btmi7_firmware:-:*:*:*:*:*:*:*
    cpe:2.3:o:intel:nuc11btmi7_firmware:-:*:*:*:*:*:*:*
  • cpe:2.3:h:intel:nuc11btmi7:-:*:*:*:*:*:*:*
    cpe:2.3:h:intel:nuc11btmi7:-:*:*:*:*:*:*:*
  • cpe:2.3:o:intel:nuc11dbbi7_firmware:-:*:*:*:*:*:*:*
    cpe:2.3:o:intel:nuc11dbbi7_firmware:-:*:*:*:*:*:*:*
  • cpe:2.3:h:intel:nuc11dbbi7:-:*:*:*:*:*:*:*
    cpe:2.3:h:intel:nuc11dbbi7:-:*:*:*:*:*:*:*
  • cpe:2.3:o:intel:nuc11btmi9_firmware:-:*:*:*:*:*:*:*
    cpe:2.3:o:intel:nuc11btmi9_firmware:-:*:*:*:*:*:*:*
  • cpe:2.3:h:intel:nuc11btmi9:-:*:*:*:*:*:*:*
    cpe:2.3:h:intel:nuc11btmi9:-:*:*:*:*:*:*:*
  • cpe:2.3:o:intel:nuc11dbbi9_firmware:-:*:*:*:*:*:*:*
    cpe:2.3:o:intel:nuc11dbbi9_firmware:-:*:*:*:*:*:*:*
  • cpe:2.3:h:intel:nuc11dbbi9:-:*:*:*:*:*:*:*
    cpe:2.3:h:intel:nuc11dbbi9:-:*:*:*:*:*:*:*
  • cpe:2.3:o:intel:nuc11phki7c_firmware:-:*:*:*:*:*:*:*
    cpe:2.3:o:intel:nuc11phki7c_firmware:-:*:*:*:*:*:*:*
  • cpe:2.3:h:intel:nuc11phki7c:-:*:*:*:*:*:*:*
    cpe:2.3:h:intel:nuc11phki7c:-:*:*:*:*:*:*:*
  • cpe:2.3:o:intel:nuc11phki7caa_firmware:-:*:*:*:*:*:*:*
    cpe:2.3:o:intel:nuc11phki7caa_firmware:-:*:*:*:*:*:*:*
  • cpe:2.3:h:intel:nuc11phki7caa:-:*:*:*:*:*:*:*
    cpe:2.3:h:intel:nuc11phki7caa:-:*:*:*:*:*:*:*
  • cpe:2.3:o:intel:nuc11tnkv50z_firmware:-:*:*:*:*:*:*:*
    cpe:2.3:o:intel:nuc11tnkv50z_firmware:-:*:*:*:*:*:*:*
  • cpe:2.3:h:intel:nuc11tnkv50z:-:*:*:*:*:*:*:*
    cpe:2.3:h:intel:nuc11tnkv50z:-:*:*:*:*:*:*:*
  • cpe:2.3:o:intel:nuc11tnhv70l_firmware:-:*:*:*:*:*:*:*
    cpe:2.3:o:intel:nuc11tnhv70l_firmware:-:*:*:*:*:*:*:*
  • cpe:2.3:h:intel:nuc11tnhv70l:-:*:*:*:*:*:*:*
    cpe:2.3:h:intel:nuc11tnhv70l:-:*:*:*:*:*:*:*
  • cpe:2.3:o:intel:nuc11tnhv50l_firmware:-:*:*:*:*:*:*:*
    cpe:2.3:o:intel:nuc11tnhv50l_firmware:-:*:*:*:*:*:*:*
  • cpe:2.3:h:intel:nuc11tnhv50l:-:*:*:*:*:*:*:*
    cpe:2.3:h:intel:nuc11tnhv50l:-:*:*:*:*:*:*:*
  • cpe:2.3:o:intel:nuc11tnkv5_firmware:-:*:*:*:*:*:*:*
    cpe:2.3:o:intel:nuc11tnkv5_firmware:-:*:*:*:*:*:*:*
  • cpe:2.3:h:intel:nuc11tnkv5:-:*:*:*:*:*:*:*
    cpe:2.3:h:intel:nuc11tnkv5:-:*:*:*:*:*:*:*
  • cpe:2.3:o:intel:nuc11tnkv7_firmware:-:*:*:*:*:*:*:*
    cpe:2.3:o:intel:nuc11tnkv7_firmware:-:*:*:*:*:*:*:*
  • cpe:2.3:h:intel:nuc11tnkv7:-:*:*:*:*:*:*:*
    cpe:2.3:h:intel:nuc11tnkv7:-:*:*:*:*:*:*:*
  • cpe:2.3:o:intel:nuc11tnhv5_firmware:-:*:*:*:*:*:*:*
    cpe:2.3:o:intel:nuc11tnhv5_firmware:-:*:*:*:*:*:*:*
  • cpe:2.3:h:intel:nuc11tnhv5:-:*:*:*:*:*:*:*
    cpe:2.3:h:intel:nuc11tnhv5:-:*:*:*:*:*:*:*
  • cpe:2.3:o:intel:nuc11tnhv7_firmware:-:*:*:*:*:*:*:*
    cpe:2.3:o:intel:nuc11tnhv7_firmware:-:*:*:*:*:*:*:*
  • cpe:2.3:h:intel:nuc11tnhv7:-:*:*:*:*:*:*:*
    cpe:2.3:h:intel:nuc11tnhv7:-:*:*:*:*:*:*:*
  • cpe:2.3:o:intel:nuc11tnbv7_firmware:-:*:*:*:*:*:*:*
    cpe:2.3:o:intel:nuc11tnbv7_firmware:-:*:*:*:*:*:*:*
  • cpe:2.3:h:intel:nuc11tnbv7:-:*:*:*:*:*:*:*
    cpe:2.3:h:intel:nuc11tnbv7:-:*:*:*:*:*:*:*
  • cpe:2.3:o:intel:nuc11tnbv5_firmware:-:*:*:*:*:*:*:*
    cpe:2.3:o:intel:nuc11tnbv5_firmware:-:*:*:*:*:*:*:*
  • cpe:2.3:h:intel:nuc11tnbv5:-:*:*:*:*:*:*:*
    cpe:2.3:h:intel:nuc11tnbv5:-:*:*:*:*:*:*:*

Protect Your Infrastructure against CVE-2022-31477: 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-43903 – NSSCryptoSignBackend.cc in Poppler before 25.04.0 does not verify the adbe.pkcs7.sha1 signatures on documents, resulting in potential signature forgeries.
  • CVE-2025-3796 – A vulnerability classified as critical has been found in PHPGurukul Men Salon Management System 1.0. This affects an unknown part of the file /admi...
  • CVE-2025-32953 – z80pack is a mature emulator of multiple platforms with 8080 and Z80 CPU. In version 1.38 and prior, the `makefile-ubuntu.yml` workflow file uses `...
  • CVE-2025-29058 – An issue in Qimou CMS v.3.34.0 allows a remote attacker to execute arbitrary code via the upgrade.php component.
  • CVE-2024-53591 – An issue in the login page of Seclore v3.27.5.0 allows attackers to bypass authentication via a brute force attack.