CVE-2021-26342 Vulnerability Analysis & Exploit Details

CVE-2021-26342
Vulnerability Scoring

3.3
/10
Moderate Risk

Exploiting CVE-2021-26342 requires specific conditions, leading to a moderate security impact.

Attack Complexity Details

  • Attack Complexity: Low
    Exploits can be performed without significant complexity or 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-2021-26342 Details

Status: Modified

Last updated: 🕠 21 Nov 2024, 05:56 UTC
Originally published on: 🕔 11 May 2022, 17:15 UTC

Time between publication and last update: 924 days

CVSS Release: version 3

CVSS3 Source

nvd@nist.gov

CVSS3 Type

Primary

CVSS3 Vector

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

CVE-2021-26342 Vulnerability Summary

CVE-2021-26342: In SEV guest VMs, the CPU may fail to flush the Translation Lookaside Buffer (TLB) following a particular sequence of operations that includes creation of a new virtual machine control block (VMCB). The failure to flush the TLB may cause the microcode to use stale TLB translations which may allow for disclosure of SEV guest memory contents. Users of SEV-ES/SEV-SNP guest VMs are not impacted by this vulnerability.

Assessing the Risk of CVE-2021-26342

Access Complexity Graph

The exploitability of CVE-2021-26342 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-2021-26342

CVE-2021-26342 presents an accessible attack vector with minimal effort required. Restricting access controls and implementing security updates are critical to reducing exploitation 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-2021-26342, 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-2021-26342, showing how Confidentiality, Integrity, and Availability might be affected if the vulnerability is exploited. Higher values usually signal greater potential damage.

  • Confidentiality: Low
    CVE-2021-26342 could lead to minor leaks of non-critical information without major privacy breaches.
  • Integrity: None
    CVE-2021-26342 poses no threat to data integrity.
  • Availability: None
    CVE-2021-26342 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-2021-26342 References

External References

CWE Common Weakness Enumeration

NVD-CWE-noinfo

Vulnerable Configurations

  • cpe:2.3:o:amd:epyc_7763_firmware:-:*:*:*:*:*:*:*
    cpe:2.3:o:amd:epyc_7763_firmware:-:*:*:*:*:*:*:*
  • cpe:2.3:o:amd:epyc_7763_firmware:milanpi-sp3_1.0.0.4:*:*:*:*:*:*:*
    cpe:2.3:o:amd:epyc_7763_firmware:milanpi-sp3_1.0.0.4:*:*:*:*:*:*:*
  • cpe:2.3:o:amd:epyc_7763_firmware:milanpi-sp3_1.0.0.5:*:*:*:*:*:*:*
    cpe:2.3:o:amd:epyc_7763_firmware:milanpi-sp3_1.0.0.5:*:*:*:*:*:*:*
  • cpe:2.3:h:amd:epyc_7763:-:*:*:*:*:*:*:*
    cpe:2.3:h:amd:epyc_7763:-:*:*:*:*:*:*:*
  • cpe:2.3:o:amd:epyc_7713p_firmware:-:*:*:*:*:*:*:*
    cpe:2.3:o:amd:epyc_7713p_firmware:-:*:*:*:*:*:*:*
  • cpe:2.3:o:amd:epyc_7713p_firmware:milanpi-sp3_1.0.0.4:*:*:*:*:*:*:*
    cpe:2.3:o:amd:epyc_7713p_firmware:milanpi-sp3_1.0.0.4:*:*:*:*:*:*:*
  • cpe:2.3:o:amd:epyc_7713p_firmware:milanpi-sp3_1.0.0.5:*:*:*:*:*:*:*
    cpe:2.3:o:amd:epyc_7713p_firmware:milanpi-sp3_1.0.0.5:*:*:*:*:*:*:*
  • cpe:2.3:h:amd:epyc_7713p:-:*:*:*:*:*:*:*
    cpe:2.3:h:amd:epyc_7713p:-:*:*:*:*:*:*:*
  • cpe:2.3:o:amd:epyc_7713_firmware:-:*:*:*:*:*:*:*
    cpe:2.3:o:amd:epyc_7713_firmware:-:*:*:*:*:*:*:*
  • cpe:2.3:o:amd:epyc_7713_firmware:milanpi-sp3_1.0.0.4:*:*:*:*:*:*:*
    cpe:2.3:o:amd:epyc_7713_firmware:milanpi-sp3_1.0.0.4:*:*:*:*:*:*:*
  • cpe:2.3:o:amd:epyc_7713_firmware:milanpi-sp3_1.0.0.5:*:*:*:*:*:*:*
    cpe:2.3:o:amd:epyc_7713_firmware:milanpi-sp3_1.0.0.5:*:*:*:*:*:*:*
  • cpe:2.3:h:amd:epyc_7713:-:*:*:*:*:*:*:*
    cpe:2.3:h:amd:epyc_7713:-:*:*:*:*:*:*:*
  • cpe:2.3:o:amd:epyc_7663_firmware:-:*:*:*:*:*:*:*
    cpe:2.3:o:amd:epyc_7663_firmware:-:*:*:*:*:*:*:*
  • cpe:2.3:o:amd:epyc_7663_firmware:milanpi-sp3_1.0.0.4:*:*:*:*:*:*:*
    cpe:2.3:o:amd:epyc_7663_firmware:milanpi-sp3_1.0.0.4:*:*:*:*:*:*:*
  • cpe:2.3:o:amd:epyc_7663_firmware:milanpi-sp3_1.0.0.5:*:*:*:*:*:*:*
    cpe:2.3:o:amd:epyc_7663_firmware:milanpi-sp3_1.0.0.5:*:*:*:*:*:*:*
  • cpe:2.3:h:amd:epyc_7663:-:*:*:*:*:*:*:*
    cpe:2.3:h:amd:epyc_7663:-:*:*:*:*:*:*:*
  • cpe:2.3:o:amd:epyc_7643_firmware:-:*:*:*:*:*:*:*
    cpe:2.3:o:amd:epyc_7643_firmware:-:*:*:*:*:*:*:*
  • cpe:2.3:o:amd:epyc_7643_firmware:milanpi-sp3_1.0.0.4:*:*:*:*:*:*:*
    cpe:2.3:o:amd:epyc_7643_firmware:milanpi-sp3_1.0.0.4:*:*:*:*:*:*:*
  • cpe:2.3:o:amd:epyc_7643_firmware:milanpi-sp3_1.0.0.5:*:*:*:*:*:*:*
    cpe:2.3:o:amd:epyc_7643_firmware:milanpi-sp3_1.0.0.5:*:*:*:*:*:*:*
  • cpe:2.3:h:amd:epyc_7643:-:*:*:*:*:*:*:*
    cpe:2.3:h:amd:epyc_7643:-:*:*:*:*:*:*:*
  • cpe:2.3:o:amd:epyc_75f3_firmware:-:*:*:*:*:*:*:*
    cpe:2.3:o:amd:epyc_75f3_firmware:-:*:*:*:*:*:*:*
  • cpe:2.3:o:amd:epyc_75f3_firmware:milanpi-sp3_1.0.0.4:*:*:*:*:*:*:*
    cpe:2.3:o:amd:epyc_75f3_firmware:milanpi-sp3_1.0.0.4:*:*:*:*:*:*:*
  • cpe:2.3:o:amd:epyc_75f3_firmware:milanpi-sp3_1.0.0.5:*:*:*:*:*:*:*
    cpe:2.3:o:amd:epyc_75f3_firmware:milanpi-sp3_1.0.0.5:*:*:*:*:*:*:*
  • cpe:2.3:h:amd:epyc_75f3:-:*:*:*:*:*:*:*
    cpe:2.3:h:amd:epyc_75f3:-:*:*:*:*:*:*:*
  • cpe:2.3:o:amd:epyc_7543p_firmware:-:*:*:*:*:*:*:*
    cpe:2.3:o:amd:epyc_7543p_firmware:-:*:*:*:*:*:*:*
  • cpe:2.3:o:amd:epyc_7543p_firmware:milanpi-sp3_1.0.0.4:*:*:*:*:*:*:*
    cpe:2.3:o:amd:epyc_7543p_firmware:milanpi-sp3_1.0.0.4:*:*:*:*:*:*:*
  • cpe:2.3:o:amd:epyc_7543p_firmware:milanpi-sp3_1.0.0.5:*:*:*:*:*:*:*
    cpe:2.3:o:amd:epyc_7543p_firmware:milanpi-sp3_1.0.0.5:*:*:*:*:*:*:*
  • cpe:2.3:h:amd:epyc_7543p:-:*:*:*:*:*:*:*
    cpe:2.3:h:amd:epyc_7543p:-:*:*:*:*:*:*:*
  • cpe:2.3:o:amd:epyc_7543_firmware:-:*:*:*:*:*:*:*
    cpe:2.3:o:amd:epyc_7543_firmware:-:*:*:*:*:*:*:*
  • cpe:2.3:o:amd:epyc_7543_firmware:milanpi-sp3_1.0.0.4:*:*:*:*:*:*:*
    cpe:2.3:o:amd:epyc_7543_firmware:milanpi-sp3_1.0.0.4:*:*:*:*:*:*:*
  • cpe:2.3:o:amd:epyc_7543_firmware:milanpi-sp3_1.0.0.5:*:*:*:*:*:*:*
    cpe:2.3:o:amd:epyc_7543_firmware:milanpi-sp3_1.0.0.5:*:*:*:*:*:*:*
  • cpe:2.3:h:amd:epyc_7543:-:*:*:*:*:*:*:*
    cpe:2.3:h:amd:epyc_7543:-:*:*:*:*:*:*:*
  • cpe:2.3:o:amd:epyc_7513_firmware:-:*:*:*:*:*:*:*
    cpe:2.3:o:amd:epyc_7513_firmware:-:*:*:*:*:*:*:*
  • cpe:2.3:o:amd:epyc_7513_firmware:milanpi-sp3_1.0.0.4:*:*:*:*:*:*:*
    cpe:2.3:o:amd:epyc_7513_firmware:milanpi-sp3_1.0.0.4:*:*:*:*:*:*:*
  • cpe:2.3:o:amd:epyc_7513_firmware:milanpi-sp3_1.0.0.5:*:*:*:*:*:*:*
    cpe:2.3:o:amd:epyc_7513_firmware:milanpi-sp3_1.0.0.5:*:*:*:*:*:*:*
  • cpe:2.3:h:amd:epyc_7513:-:*:*:*:*:*:*:*
    cpe:2.3:h:amd:epyc_7513:-:*:*:*:*:*:*:*
  • cpe:2.3:o:amd:epyc_7453_firmware:-:*:*:*:*:*:*:*
    cpe:2.3:o:amd:epyc_7453_firmware:-:*:*:*:*:*:*:*
  • cpe:2.3:o:amd:epyc_7453_firmware:milanpi-sp3_1.0.0.4:*:*:*:*:*:*:*
    cpe:2.3:o:amd:epyc_7453_firmware:milanpi-sp3_1.0.0.4:*:*:*:*:*:*:*
  • cpe:2.3:o:amd:epyc_7453_firmware:milanpi-sp3_1.0.0.5:*:*:*:*:*:*:*
    cpe:2.3:o:amd:epyc_7453_firmware:milanpi-sp3_1.0.0.5:*:*:*:*:*:*:*
  • cpe:2.3:h:amd:epyc_7453:-:*:*:*:*:*:*:*
    cpe:2.3:h:amd:epyc_7453:-:*:*:*:*:*:*:*
  • cpe:2.3:o:amd:epyc_74f3_firmware:-:*:*:*:*:*:*:*
    cpe:2.3:o:amd:epyc_74f3_firmware:-:*:*:*:*:*:*:*
  • cpe:2.3:o:amd:epyc_74f3_firmware:milanpi-sp3_1.0.0.4:*:*:*:*:*:*:*
    cpe:2.3:o:amd:epyc_74f3_firmware:milanpi-sp3_1.0.0.4:*:*:*:*:*:*:*
  • cpe:2.3:o:amd:epyc_74f3_firmware:milanpi-sp3_1.0.0.5:*:*:*:*:*:*:*
    cpe:2.3:o:amd:epyc_74f3_firmware:milanpi-sp3_1.0.0.5:*:*:*:*:*:*:*
  • cpe:2.3:h:amd:epyc_74f3:-:*:*:*:*:*:*:*
    cpe:2.3:h:amd:epyc_74f3:-:*:*:*:*:*:*:*
  • cpe:2.3:o:amd:epyc_7443p_firmware:-:*:*:*:*:*:*:*
    cpe:2.3:o:amd:epyc_7443p_firmware:-:*:*:*:*:*:*:*
  • cpe:2.3:o:amd:epyc_7443p_firmware:milanpi-sp3_1.0.0.4:*:*:*:*:*:*:*
    cpe:2.3:o:amd:epyc_7443p_firmware:milanpi-sp3_1.0.0.4:*:*:*:*:*:*:*
  • cpe:2.3:o:amd:epyc_7443p_firmware:milanpi-sp3_1.0.0.5:*:*:*:*:*:*:*
    cpe:2.3:o:amd:epyc_7443p_firmware:milanpi-sp3_1.0.0.5:*:*:*:*:*:*:*
  • cpe:2.3:h:amd:epyc_7443p:-:*:*:*:*:*:*:*
    cpe:2.3:h:amd:epyc_7443p:-:*:*:*:*:*:*:*
  • cpe:2.3:o:amd:epyc_7443_firmware:-:*:*:*:*:*:*:*
    cpe:2.3:o:amd:epyc_7443_firmware:-:*:*:*:*:*:*:*
  • cpe:2.3:o:amd:epyc_7443_firmware:milanpi-sp3_1.0.0.4:*:*:*:*:*:*:*
    cpe:2.3:o:amd:epyc_7443_firmware:milanpi-sp3_1.0.0.4:*:*:*:*:*:*:*
  • cpe:2.3:o:amd:epyc_7443_firmware:milanpi-sp3_1.0.0.5:*:*:*:*:*:*:*
    cpe:2.3:o:amd:epyc_7443_firmware:milanpi-sp3_1.0.0.5:*:*:*:*:*:*:*
  • cpe:2.3:h:amd:epyc_7443:-:*:*:*:*:*:*:*
    cpe:2.3:h:amd:epyc_7443:-:*:*:*:*:*:*:*
  • cpe:2.3:o:amd:epyc_7413_firmware:-:*:*:*:*:*:*:*
    cpe:2.3:o:amd:epyc_7413_firmware:-:*:*:*:*:*:*:*
  • cpe:2.3:o:amd:epyc_7413_firmware:milanpi-sp3_1.0.0.4:*:*:*:*:*:*:*
    cpe:2.3:o:amd:epyc_7413_firmware:milanpi-sp3_1.0.0.4:*:*:*:*:*:*:*
  • cpe:2.3:o:amd:epyc_7413_firmware:milanpi-sp3_1.0.0.5:*:*:*:*:*:*:*
    cpe:2.3:o:amd:epyc_7413_firmware:milanpi-sp3_1.0.0.5:*:*:*:*:*:*:*
  • cpe:2.3:h:amd:epyc_7413:-:*:*:*:*:*:*:*
    cpe:2.3:h:amd:epyc_7413:-:*:*:*:*:*:*:*
  • cpe:2.3:o:amd:epyc_73f3_firmware:-:*:*:*:*:*:*:*
    cpe:2.3:o:amd:epyc_73f3_firmware:-:*:*:*:*:*:*:*
  • cpe:2.3:o:amd:epyc_73f3_firmware:milanpi-sp3_1.0.0.4:*:*:*:*:*:*:*
    cpe:2.3:o:amd:epyc_73f3_firmware:milanpi-sp3_1.0.0.4:*:*:*:*:*:*:*
  • cpe:2.3:o:amd:epyc_73f3_firmware:milanpi-sp3_1.0.0.5:*:*:*:*:*:*:*
    cpe:2.3:o:amd:epyc_73f3_firmware:milanpi-sp3_1.0.0.5:*:*:*:*:*:*:*
  • cpe:2.3:h:amd:epyc_73f3:-:*:*:*:*:*:*:*
    cpe:2.3:h:amd:epyc_73f3:-:*:*:*:*:*:*:*
  • cpe:2.3:o:amd:epyc_7343_firmware:-:*:*:*:*:*:*:*
    cpe:2.3:o:amd:epyc_7343_firmware:-:*:*:*:*:*:*:*
  • cpe:2.3:o:amd:epyc_7343_firmware:milanpi-sp3_1.0.0.4:*:*:*:*:*:*:*
    cpe:2.3:o:amd:epyc_7343_firmware:milanpi-sp3_1.0.0.4:*:*:*:*:*:*:*
  • cpe:2.3:o:amd:epyc_7343_firmware:milanpi-sp3_1.0.0.5:*:*:*:*:*:*:*
    cpe:2.3:o:amd:epyc_7343_firmware:milanpi-sp3_1.0.0.5:*:*:*:*:*:*:*
  • cpe:2.3:h:amd:epyc_7343:-:*:*:*:*:*:*:*
    cpe:2.3:h:amd:epyc_7343:-:*:*:*:*:*:*:*
  • cpe:2.3:o:amd:epyc_7313p_firmware:-:*:*:*:*:*:*:*
    cpe:2.3:o:amd:epyc_7313p_firmware:-:*:*:*:*:*:*:*
  • cpe:2.3:o:amd:epyc_7313p_firmware:milanpi-sp3_1.0.0.4:*:*:*:*:*:*:*
    cpe:2.3:o:amd:epyc_7313p_firmware:milanpi-sp3_1.0.0.4:*:*:*:*:*:*:*
  • cpe:2.3:o:amd:epyc_7313p_firmware:milanpi-sp3_1.0.0.5:*:*:*:*:*:*:*
    cpe:2.3:o:amd:epyc_7313p_firmware:milanpi-sp3_1.0.0.5:*:*:*:*:*:*:*
  • cpe:2.3:h:amd:epyc_7313p:-:*:*:*:*:*:*:*
    cpe:2.3:h:amd:epyc_7313p:-:*:*:*:*:*:*:*
  • cpe:2.3:o:amd:epyc_7313_firmware:-:*:*:*:*:*:*:*
    cpe:2.3:o:amd:epyc_7313_firmware:-:*:*:*:*:*:*:*
  • cpe:2.3:o:amd:epyc_7313_firmware:milanpi-sp3_1.0.0.4:*:*:*:*:*:*:*
    cpe:2.3:o:amd:epyc_7313_firmware:milanpi-sp3_1.0.0.4:*:*:*:*:*:*:*
  • cpe:2.3:o:amd:epyc_7313_firmware:milanpi-sp3_1.0.0.5:*:*:*:*:*:*:*
    cpe:2.3:o:amd:epyc_7313_firmware:milanpi-sp3_1.0.0.5:*:*:*:*:*:*:*
  • cpe:2.3:h:amd:epyc_7313:-:*:*:*:*:*:*:*
    cpe:2.3:h:amd:epyc_7313:-:*:*:*:*:*:*:*
  • cpe:2.3:o:amd:epyc_72f3_firmware:-:*:*:*:*:*:*:*
    cpe:2.3:o:amd:epyc_72f3_firmware:-:*:*:*:*:*:*:*
  • cpe:2.3:o:amd:epyc_72f3_firmware:milanpi-sp3_1.0.0.4:*:*:*:*:*:*:*
    cpe:2.3:o:amd:epyc_72f3_firmware:milanpi-sp3_1.0.0.4:*:*:*:*:*:*:*
  • cpe:2.3:o:amd:epyc_72f3_firmware:milanpi-sp3_1.0.0.5:*:*:*:*:*:*:*
    cpe:2.3:o:amd:epyc_72f3_firmware:milanpi-sp3_1.0.0.5:*:*:*:*:*:*:*
  • cpe:2.3:h:amd:epyc_72f3:-:*:*:*:*:*:*:*
    cpe:2.3:h:amd:epyc_72f3:-:*:*:*:*:*:*:*
  • cpe:2.3:o:amd:epyc_7773x_firmware:-:*:*:*:*:*:*:*
    cpe:2.3:o:amd:epyc_7773x_firmware:-:*:*:*:*:*:*:*
  • cpe:2.3:h:amd:epyc_7773x:-:*:*:*:*:*:*:*
    cpe:2.3:h:amd:epyc_7773x:-:*:*:*:*:*:*:*
  • cpe:2.3:o:amd:epyc_7473x_firmware:-:*:*:*:*:*:*:*
    cpe:2.3:o:amd:epyc_7473x_firmware:-:*:*:*:*:*:*:*
  • cpe:2.3:h:amd:epyc_7473x:-:*:*:*:*:*:*:*
    cpe:2.3:h:amd:epyc_7473x:-:*:*:*:*:*:*:*
  • cpe:2.3:o:amd:epyc_7573x_firmware:-:*:*:*:*:*:*:*
    cpe:2.3:o:amd:epyc_7573x_firmware:-:*:*:*:*:*:*:*
  • cpe:2.3:h:amd:epyc_7573x:-:*:*:*:*:*:*:*
    cpe:2.3:h:amd:epyc_7573x:-:*:*:*:*:*:*:*
  • cpe:2.3:o:amd:epyc_7373x_firmware:-:*:*:*:*:*:*:*
    cpe:2.3:o:amd:epyc_7373x_firmware:-:*:*:*:*:*:*:*
  • cpe:2.3:h:amd:epyc_7373x:-:*:*:*:*:*:*:*
    cpe:2.3:h:amd:epyc_7373x:-:*:*:*:*:*:*:*
  • cpe:2.3:o:amd:epyc_7001_firmware:-:*:*:*:*:*:*:*
    cpe:2.3:o:amd:epyc_7001_firmware:-:*:*:*:*:*:*:*
  • cpe:2.3:o:amd:epyc_7001_firmware:naplespi-sp3_1.0.0.g:*:*:*:*:*:*:*
    cpe:2.3:o:amd:epyc_7001_firmware:naplespi-sp3_1.0.0.g:*:*:*:*:*:*:*
  • cpe:2.3:h:amd:epyc_7001:-:*:*:*:*:*:*:*
    cpe:2.3:h:amd:epyc_7001:-:*:*:*:*:*:*:*
  • cpe:2.3:o:amd:epyc_7251_firmware:-:*:*:*:*:*:*:*
    cpe:2.3:o:amd:epyc_7251_firmware:-:*:*:*:*:*:*:*
  • cpe:2.3:o:amd:epyc_7251_firmware:naplespi-sp3_1.0.0.g:*:*:*:*:*:*:*
    cpe:2.3:o:amd:epyc_7251_firmware:naplespi-sp3_1.0.0.g:*:*:*:*:*:*:*
  • cpe:2.3:h:amd:epyc_7251:-:*:*:*:*:*:*:*
    cpe:2.3:h:amd:epyc_7251:-:*:*:*:*:*:*:*
  • cpe:2.3:o:amd:epyc_7261_firmware:-:*:*:*:*:*:*:*
    cpe:2.3:o:amd:epyc_7261_firmware:-:*:*:*:*:*:*:*
  • cpe:2.3:o:amd:epyc_7261_firmware:naplespi-sp3_1.0.0.g:*:*:*:*:*:*:*
    cpe:2.3:o:amd:epyc_7261_firmware:naplespi-sp3_1.0.0.g:*:*:*:*:*:*:*
  • cpe:2.3:h:amd:epyc_7261:-:*:*:*:*:*:*:*
    cpe:2.3:h:amd:epyc_7261:-:*:*:*:*:*:*:*
  • cpe:2.3:o:amd:epyc_7281_firmware:-:*:*:*:*:*:*:*
    cpe:2.3:o:amd:epyc_7281_firmware:-:*:*:*:*:*:*:*
  • cpe:2.3:o:amd:epyc_7281_firmware:naplespi-sp3_1.0.0.g:*:*:*:*:*:*:*
    cpe:2.3:o:amd:epyc_7281_firmware:naplespi-sp3_1.0.0.g:*:*:*:*:*:*:*
  • cpe:2.3:h:amd:epyc_7281:-:*:*:*:*:*:*:*
    cpe:2.3:h:amd:epyc_7281:-:*:*:*:*:*:*:*
  • cpe:2.3:o:amd:epyc_7301_firmware:-:*:*:*:*:*:*:*
    cpe:2.3:o:amd:epyc_7301_firmware:-:*:*:*:*:*:*:*
  • cpe:2.3:o:amd:epyc_7301_firmware:naplespi-sp3_1.0.0.g:*:*:*:*:*:*:*
    cpe:2.3:o:amd:epyc_7301_firmware:naplespi-sp3_1.0.0.g:*:*:*:*:*:*:*
  • cpe:2.3:h:amd:epyc_7301:-:*:*:*:*:*:*:*
    cpe:2.3:h:amd:epyc_7301:-:*:*:*:*:*:*:*
  • cpe:2.3:o:amd:epyc_7351_firmware:-:*:*:*:*:*:*:*
    cpe:2.3:o:amd:epyc_7351_firmware:-:*:*:*:*:*:*:*
  • cpe:2.3:o:amd:epyc_7351_firmware:naplespi-sp3_1.0.0.g:*:*:*:*:*:*:*
    cpe:2.3:o:amd:epyc_7351_firmware:naplespi-sp3_1.0.0.g:*:*:*:*:*:*:*
  • cpe:2.3:h:amd:epyc_7351:-:*:*:*:*:*:*:*
    cpe:2.3:h:amd:epyc_7351:-:*:*:*:*:*:*:*
  • cpe:2.3:o:amd:epyc_7351p_firmware:-:*:*:*:*:*:*:*
    cpe:2.3:o:amd:epyc_7351p_firmware:-:*:*:*:*:*:*:*
  • cpe:2.3:o:amd:epyc_7351p_firmware:naplespi-sp3_1.0.0.g:*:*:*:*:*:*:*
    cpe:2.3:o:amd:epyc_7351p_firmware:naplespi-sp3_1.0.0.g:*:*:*:*:*:*:*
  • cpe:2.3:h:amd:epyc_7351p:-:*:*:*:*:*:*:*
    cpe:2.3:h:amd:epyc_7351p:-:*:*:*:*:*:*:*
  • cpe:2.3:o:amd:epyc_7371_firmware:-:*:*:*:*:*:*:*
    cpe:2.3:o:amd:epyc_7371_firmware:-:*:*:*:*:*:*:*
  • cpe:2.3:o:amd:epyc_7371_firmware:naplespi-sp3_1.0.0.g:*:*:*:*:*:*:*
    cpe:2.3:o:amd:epyc_7371_firmware:naplespi-sp3_1.0.0.g:*:*:*:*:*:*:*
  • cpe:2.3:h:amd:epyc_7371:-:*:*:*:*:*:*:*
    cpe:2.3:h:amd:epyc_7371:-:*:*:*:*:*:*:*
  • cpe:2.3:o:amd:epyc_7401_firmware:-:*:*:*:*:*:*:*
    cpe:2.3:o:amd:epyc_7401_firmware:-:*:*:*:*:*:*:*
  • cpe:2.3:o:amd:epyc_7401_firmware:naplespi-sp3_1.0.0.g:*:*:*:*:*:*:*
    cpe:2.3:o:amd:epyc_7401_firmware:naplespi-sp3_1.0.0.g:*:*:*:*:*:*:*
  • cpe:2.3:h:amd:epyc_7401:-:*:*:*:*:*:*:*
    cpe:2.3:h:amd:epyc_7401:-:*:*:*:*:*:*:*
  • cpe:2.3:o:amd:epyc_7401p_firmware:-:*:*:*:*:*:*:*
    cpe:2.3:o:amd:epyc_7401p_firmware:-:*:*:*:*:*:*:*
  • cpe:2.3:o:amd:epyc_7401p_firmware:naplespi-sp3_1.0.0.g:*:*:*:*:*:*:*
    cpe:2.3:o:amd:epyc_7401p_firmware:naplespi-sp3_1.0.0.g:*:*:*:*:*:*:*
  • cpe:2.3:h:amd:epyc_7401p:-:*:*:*:*:*:*:*
    cpe:2.3:h:amd:epyc_7401p:-:*:*:*:*:*:*:*
  • cpe:2.3:o:amd:epyc_7451_firmware:-:*:*:*:*:*:*:*
    cpe:2.3:o:amd:epyc_7451_firmware:-:*:*:*:*:*:*:*
  • cpe:2.3:o:amd:epyc_7451_firmware:naplespi-sp3_1.0.0.g:*:*:*:*:*:*:*
    cpe:2.3:o:amd:epyc_7451_firmware:naplespi-sp3_1.0.0.g:*:*:*:*:*:*:*
  • cpe:2.3:h:amd:epyc_7451:-:*:*:*:*:*:*:*
    cpe:2.3:h:amd:epyc_7451:-:*:*:*:*:*:*:*
  • cpe:2.3:o:amd:epyc_7501_firmware:-:*:*:*:*:*:*:*
    cpe:2.3:o:amd:epyc_7501_firmware:-:*:*:*:*:*:*:*
  • cpe:2.3:o:amd:epyc_7501_firmware:naplespi-sp3_1.0.0.g:*:*:*:*:*:*:*
    cpe:2.3:o:amd:epyc_7501_firmware:naplespi-sp3_1.0.0.g:*:*:*:*:*:*:*
  • cpe:2.3:h:amd:epyc_7501:-:*:*:*:*:*:*:*
    cpe:2.3:h:amd:epyc_7501:-:*:*:*:*:*:*:*
  • cpe:2.3:o:amd:epyc_7551_firmware:-:*:*:*:*:*:*:*
    cpe:2.3:o:amd:epyc_7551_firmware:-:*:*:*:*:*:*:*
  • cpe:2.3:o:amd:epyc_7551_firmware:naplespi-sp3_1.0.0.g:*:*:*:*:*:*:*
    cpe:2.3:o:amd:epyc_7551_firmware:naplespi-sp3_1.0.0.g:*:*:*:*:*:*:*
  • cpe:2.3:h:amd:epyc_7551:-:*:*:*:*:*:*:*
    cpe:2.3:h:amd:epyc_7551:-:*:*:*:*:*:*:*
  • cpe:2.3:o:amd:epyc_7551p_firmware:-:*:*:*:*:*:*:*
    cpe:2.3:o:amd:epyc_7551p_firmware:-:*:*:*:*:*:*:*
  • cpe:2.3:o:amd:epyc_7551p_firmware:naplespi-sp3_1.0.0.g:*:*:*:*:*:*:*
    cpe:2.3:o:amd:epyc_7551p_firmware:naplespi-sp3_1.0.0.g:*:*:*:*:*:*:*
  • cpe:2.3:h:amd:epyc_7551p:-:*:*:*:*:*:*:*
    cpe:2.3:h:amd:epyc_7551p:-:*:*:*:*:*:*:*
  • cpe:2.3:o:amd:epyc_7601_firmware:-:*:*:*:*:*:*:*
    cpe:2.3:o:amd:epyc_7601_firmware:-:*:*:*:*:*:*:*
  • cpe:2.3:o:amd:epyc_7601_firmware:naplespi-sp3_1.0.0.g:*:*:*:*:*:*:*
    cpe:2.3:o:amd:epyc_7601_firmware:naplespi-sp3_1.0.0.g:*:*:*:*:*:*:*
  • cpe:2.3:h:amd:epyc_7601:-:*:*:*:*:*:*:*
    cpe:2.3:h:amd:epyc_7601:-:*:*:*:*:*:*:*

Protect Your Infrastructure against CVE-2021-26342: 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.