CVE-2023-20593 Vulnerability Analysis & Exploit Details

CVE-2023-20593
Vulnerability Scoring

5.5

/10

Significant Risk

Security assessments indicate that CVE-2023-20593 presents a notable risk, potentially requiring prompt mitigation.

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-2023-20593 Details

Status: Modified

Last updated: 🕔 13 Feb 2025, 17:16 UTC
Originally published on: 🕗 24 Jul 2023, 20:15 UTC

Time between publication and last update: 569 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:H/I:N/A:N

CVE-2023-20593 Vulnerability Summary

CVE-2023-20593: An issue in “Zen 2” CPUs, under specific microarchitectural circumstances, may allow an attacker to potentially access sensitive information.

Assessing the Risk of CVE-2023-20593

Access Complexity Graph

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

CVE-2023-20593 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-2023-20593, 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-20593, 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-20593 can result in unauthorized access to sensitive data, severely compromising data privacy.
Integrity: None
CVE-2023-20593 poses no threat to data integrity.
Availability: None
CVE-2023-20593 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.092% (probability of exploit)

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

CVE-2023-20593 References

External References

CWE Common Weakness Enumeration

CWE-209

CAPEC Common Attack Pattern Enumeration and Classification

Fuzzing for application mapping CAPEC-215 An attacker sends random, malformed, or otherwise unexpected messages to a target application and observes the application's log or error messages returned. The attacker does not initially know how a target will respond to individual messages but by attempting a large number of message variants they may find a variant that trigger's desired behavior. In this attack, the purpose of the fuzzing is to observe the application's log and error messages, although fuzzing a target can also sometimes cause the target to enter an unstable state, causing a crash.
Padding Oracle Crypto Attack CAPEC-463 An adversary is able to efficiently decrypt data without knowing the decryption key if a target system leaks data on whether or not a padding error happened while decrypting the ciphertext. A target system that leaks this type of information becomes the padding oracle and an adversary is able to make use of that oracle to efficiently decrypt data without knowing the decryption key by issuing on average 128*b calls to the padding oracle (where b is the number of bytes in the ciphertext block). In addition to performing decryption, an adversary is also able to produce valid ciphertexts (i.e., perform encryption) by using the padding oracle, all without knowing the encryption key.
Query System for Information CAPEC-54 An adversary, aware of an application's location (and possibly authorized to use the application), probes an application's structure and evaluates its robustness by submitting requests and examining responses. Often, this is accomplished by sending variants of expected queries in the hope that these modified queries might return information beyond what the expected set of queries would provide.
Blind SQL Injection CAPEC-7 Blind SQL Injection results from an insufficient mitigation for SQL Injection. Although suppressing database error messages are considered best practice, the suppression alone is not sufficient to prevent SQL Injection. Blind SQL Injection is a form of SQL Injection that overcomes the lack of error messages. Without the error messages that facilitate SQL Injection, the adversary constructs input strings that probe the target through simple Boolean SQL expressions. The adversary can determine if the syntax and structure of the injection was successful based on whether the query was executed or not. Applied iteratively, the adversary determines how and where the target is vulnerable to SQL Injection.

Vulnerable Configurations

cpe:2.3:o:xen:xen:4.14.0:*:*:*:*:*:x86:*
cpe:2.3:o:xen:xen:4.14.0:*:*:*:*:*:x86:*
cpe:2.3:o:xen:xen:4.15.0:*:*:*:*:*:x86:*
cpe:2.3:o:xen:xen:4.15.0:*:*:*:*:*:x86:*
cpe:2.3:o:xen:xen:4.16.0:*:*:*:*:*:x86:*
cpe:2.3:o:xen:xen:4.16.0:*:*:*:*:*:x86:*
cpe:2.3:o:xen:xen:4.17.0:*:*:*:*:*:x86:*
cpe:2.3:o:xen:xen:4.17.0:*:*:*:*:*:x86:*
cpe:2.3:o:debian:debian_linux:10.0:*:*:*:*:*:*:*
cpe:2.3:o:debian:debian_linux:10.0:*:*:*:*:*:*:*
cpe:2.3:o:debian:debian_linux:11.0:*:*:*:*:*:*:*
cpe:2.3:o:debian:debian_linux:11.0:*:*:*:*:*:*:*
cpe:2.3:o:debian:debian_linux:12.0:*:*:*:*:*:*:*
cpe:2.3:o:debian:debian_linux:12.0:*:*:*:*:*:*:*
cpe:2.3:o:amd:ryzen_3_3100_firmware:-:*:*:*:*:*:*:*
cpe:2.3:o:amd:ryzen_3_3100_firmware:-:*:*:*:*:*:*:*
cpe:2.3:h:amd:ryzen_3_3100:-:*:*:*:*:*:*:*
cpe:2.3:h:amd:ryzen_3_3100:-:*:*:*:*:*:*:*
cpe:2.3:o:amd:ryzen_3_3300x_firmware:-:*:*:*:*:*:*:*
cpe:2.3:o:amd:ryzen_3_3300x_firmware:-:*:*:*:*:*:*:*
cpe:2.3:h:amd:ryzen_3_3300x:-:*:*:*:*:*:*:*
cpe:2.3:h:amd:ryzen_3_3300x:-:*:*:*:*:*:*:*
cpe:2.3:o:amd:ryzen_5_3500_firmware:-:*:*:*:*:*:*:*
cpe:2.3:o:amd:ryzen_5_3500_firmware:-:*:*:*:*:*:*:*
cpe:2.3:h:amd:ryzen_5_3500:-:*:*:*:*:*:*:*
cpe:2.3:h:amd:ryzen_5_3500:-:*:*:*:*:*:*:*
cpe:2.3:o:amd:ryzen_5_3500x_firmware:-:*:*:*:*:*:*:*
cpe:2.3:o:amd:ryzen_5_3500x_firmware:-:*:*:*:*:*:*:*
cpe:2.3:h:amd:ryzen_5_3500x:-:*:*:*:*:*:*:*
cpe:2.3:h:amd:ryzen_5_3500x:-:*:*:*:*:*:*:*
cpe:2.3:o:amd:ryzen_5_3600_firmware:-:*:*:*:*:*:*:*
cpe:2.3:o:amd:ryzen_5_3600_firmware:-:*:*:*:*:*:*:*
cpe:2.3:h:amd:ryzen_5_3600:-:*:*:*:*:*:*:*
cpe:2.3:h:amd:ryzen_5_3600:-:*:*:*:*:*:*:*
cpe:2.3:o:amd:ryzen_5_3600x_firmware:-:*:*:*:*:*:*:*
cpe:2.3:o:amd:ryzen_5_3600x_firmware:-:*:*:*:*:*:*:*
cpe:2.3:h:amd:ryzen_5_3600x:-:*:*:*:*:*:*:*
cpe:2.3:h:amd:ryzen_5_3600x:-:*:*:*:*:*:*:*
cpe:2.3:o:amd:ryzen_5_3600xt_firmware:-:*:*:*:*:*:*:*
cpe:2.3:o:amd:ryzen_5_3600xt_firmware:-:*:*:*:*:*:*:*
cpe:2.3:h:amd:ryzen_5_3600xt:-:*:*:*:*:*:*:*
cpe:2.3:h:amd:ryzen_5_3600xt:-:*:*:*:*:*:*:*
cpe:2.3:o:amd:ryzen_7_3700x_firmware:-:*:*:*:*:*:*:*
cpe:2.3:o:amd:ryzen_7_3700x_firmware:-:*:*:*:*:*:*:*
cpe:2.3:h:amd:ryzen_7_3700x:-:*:*:*:*:*:*:*
cpe:2.3:h:amd:ryzen_7_3700x:-:*:*:*:*:*:*:*
cpe:2.3:o:amd:ryzen_7_3800x_firmware:-:*:*:*:*:*:*:*
cpe:2.3:o:amd:ryzen_7_3800x_firmware:-:*:*:*:*:*:*:*
cpe:2.3:h:amd:ryzen_7_3800x:-:*:*:*:*:*:*:*
cpe:2.3:h:amd:ryzen_7_3800x:-:*:*:*:*:*:*:*
cpe:2.3:o:amd:ryzen_7_3800xt_firmware:-:*:*:*:*:*:*:*
cpe:2.3:o:amd:ryzen_7_3800xt_firmware:-:*:*:*:*:*:*:*
cpe:2.3:h:amd:ryzen_7_3800xt:-:*:*:*:*:*:*:*
cpe:2.3:h:amd:ryzen_7_3800xt:-:*:*:*:*:*:*:*
cpe:2.3:o:amd:ryzen_9_3900_firmware:-:*:*:*:*:*:*:*
cpe:2.3:o:amd:ryzen_9_3900_firmware:-:*:*:*:*:*:*:*
cpe:2.3:h:amd:ryzen_9_3900:-:*:*:*:*:*:*:*
cpe:2.3:h:amd:ryzen_9_3900:-:*:*:*:*:*:*:*
cpe:2.3:o:amd:ryzen_9_3900x_firmware:-:*:*:*:*:*:*:*
cpe:2.3:o:amd:ryzen_9_3900x_firmware:-:*:*:*:*:*:*:*
cpe:2.3:h:amd:ryzen_9_3900x:-:*:*:*:*:*:*:*
cpe:2.3:h:amd:ryzen_9_3900x:-:*:*:*:*:*:*:*
cpe:2.3:o:amd:ryzen_9_3900xt_firmware:-:*:*:*:*:*:*:*
cpe:2.3:o:amd:ryzen_9_3900xt_firmware:-:*:*:*:*:*:*:*
cpe:2.3:h:amd:ryzen_9_3900xt:-:*:*:*:*:*:*:*
cpe:2.3:h:amd:ryzen_9_3900xt:-:*:*:*:*:*:*:*
cpe:2.3:o:amd:ryzen_9_3950x_firmware:-:*:*:*:*:*:*:*
cpe:2.3:o:amd:ryzen_9_3950x_firmware:-:*:*:*:*:*:*:*
cpe:2.3:h:amd:ryzen_9_3950x:-:*:*:*:*:*:*:*
cpe:2.3:h:amd:ryzen_9_3950x:-:*:*:*:*:*:*:*
cpe:2.3:o:amd:ryzen_9_pro_3900_firmware:-:*:*:*:*:*:*:*
cpe:2.3:o:amd:ryzen_9_pro_3900_firmware:-:*:*:*:*:*:*:*
cpe:2.3:h:amd:ryzen_9_pro_3900:-:*:*:*:*:*:*:*
cpe:2.3:h:amd:ryzen_9_pro_3900:-:*:*:*:*:*:*:*
cpe:2.3:o:amd:ryzen_threadripper_pro_3995wx_firmware:-:*:*:*:*:*:*:*
cpe:2.3:o:amd:ryzen_threadripper_pro_3995wx_firmware:-:*:*:*:*:*:*:*
cpe:2.3:h:amd:ryzen_threadripper_pro_3995wx:-:*:*:*:*:*:*:*
cpe:2.3:h:amd:ryzen_threadripper_pro_3995wx:-:*:*:*:*:*:*:*
cpe:2.3:o:amd:ryzen_threadripper_pro_3975wx_firmware:-:*:*:*:*:*:*:*
cpe:2.3:o:amd:ryzen_threadripper_pro_3975wx_firmware:-:*:*:*:*:*:*:*
cpe:2.3:h:amd:ryzen_threadripper_pro_3975wx:-:*:*:*:*:*:*:*
cpe:2.3:h:amd:ryzen_threadripper_pro_3975wx:-:*:*:*:*:*:*:*
cpe:2.3:o:amd:ryzen_threadripper_pro_3955wx_firmware:-:*:*:*:*:*:*:*
cpe:2.3:o:amd:ryzen_threadripper_pro_3955wx_firmware:-:*:*:*:*:*:*:*
cpe:2.3:h:amd:ryzen_threadripper_pro_3955wx:-:*:*:*:*:*:*:*
cpe:2.3:h:amd:ryzen_threadripper_pro_3955wx:-:*:*:*:*:*:*:*
cpe:2.3:o:amd:ryzen_threadripper_pro_3945wx_firmware:-:*:*:*:*:*:*:*
cpe:2.3:o:amd:ryzen_threadripper_pro_3945wx_firmware:-:*:*:*:*:*:*:*
cpe:2.3:h:amd:ryzen_threadripper_pro_3945wx:-:*:*:*:*:*:*:*
cpe:2.3:h:amd:ryzen_threadripper_pro_3945wx:-:*:*:*:*:*:*:*
cpe:2.3:o:amd:ryzen_threadripper_3990x_firmware:-:*:*:*:*:*:*:*
cpe:2.3:o:amd:ryzen_threadripper_3990x_firmware:-:*:*:*:*:*:*:*
cpe:2.3:h:amd:ryzen_threadripper_3990x:-:*:*:*:*:*:*:*
cpe:2.3:h:amd:ryzen_threadripper_3990x:-:*:*:*:*:*:*:*
cpe:2.3:o:amd:ryzen_threadripper_3970x_firmware:-:*:*:*:*:*:*:*
cpe:2.3:o:amd:ryzen_threadripper_3970x_firmware:-:*:*:*:*:*:*:*
cpe:2.3:h:amd:ryzen_threadripper_3970x:-:*:*:*:*:*:*:*
cpe:2.3:h:amd:ryzen_threadripper_3970x:-:*:*:*:*:*:*:*
cpe:2.3:o:amd:ryzen_threadripper_3960x_firmware:-:*:*:*:*:*:*:*
cpe:2.3:o:amd:ryzen_threadripper_3960x_firmware:-:*:*:*:*:*:*:*
cpe:2.3:h:amd:ryzen_threadripper_3960x:-:*:*:*:*:*:*:*
cpe:2.3:h:amd:ryzen_threadripper_3960x:-:*:*:*:*:*:*:*
cpe:2.3:o:amd:ryzen_7_4700g_firmware:-:*:*:*:*:*:*:*
cpe:2.3:o:amd:ryzen_7_4700g_firmware:-:*:*:*:*:*:*:*
cpe:2.3:h:amd:ryzen_7_4700g:-:*:*:*:*:*:*:*
cpe:2.3:h:amd:ryzen_7_4700g:-:*:*:*:*:*:*:*
cpe:2.3:o:amd:ryzen_7_4700ge_firmware:-:*:*:*:*:*:*:*
cpe:2.3:o:amd:ryzen_7_4700ge_firmware:-:*:*:*:*:*:*:*
cpe:2.3:h:amd:ryzen_7_4700ge:-:*:*:*:*:*:*:*
cpe:2.3:h:amd:ryzen_7_4700ge:-:*:*:*:*:*:*:*
cpe:2.3:o:amd:ryzen_5_4600g_firmware:-:*:*:*:*:*:*:*
cpe:2.3:o:amd:ryzen_5_4600g_firmware:-:*:*:*:*:*:*:*
cpe:2.3:h:amd:ryzen_5_4600g:-:*:*:*:*:*:*:*
cpe:2.3:h:amd:ryzen_5_4600g:-:*:*:*:*:*:*:*
cpe:2.3:o:amd:ryzen_5_4600ge_firmware:-:*:*:*:*:*:*:*
cpe:2.3:o:amd:ryzen_5_4600ge_firmware:-:*:*:*:*:*:*:*
cpe:2.3:h:amd:ryzen_5_4600ge:-:*:*:*:*:*:*:*
cpe:2.3:h:amd:ryzen_5_4600ge:-:*:*:*:*:*:*:*
cpe:2.3:o:amd:ryzen_3_4300g_firmware:-:*:*:*:*:*:*:*
cpe:2.3:o:amd:ryzen_3_4300g_firmware:-:*:*:*:*:*:*:*
cpe:2.3:h:amd:ryzen_3_4300g:-:*:*:*:*:*:*:*
cpe:2.3:h:amd:ryzen_3_4300g:-:*:*:*:*:*:*:*
cpe:2.3:o:amd:ryzen_3_4300ge_firmware:-:*:*:*:*:*:*:*
cpe:2.3:o:amd:ryzen_3_4300ge_firmware:-:*:*:*:*:*:*:*
cpe:2.3:h:amd:ryzen_3_4300ge:-:*:*:*:*:*:*:*
cpe:2.3:h:amd:ryzen_3_4300ge:-:*:*:*:*:*:*:*
cpe:2.3:o:amd:ryzen_3_pro_4450u_firmware:-:*:*:*:*:*:*:*
cpe:2.3:o:amd:ryzen_3_pro_4450u_firmware:-:*:*:*:*:*:*:*
cpe:2.3:h:amd:ryzen_3_pro_4450u:-:*:*:*:*:*:*:*
cpe:2.3:h:amd:ryzen_3_pro_4450u:-:*:*:*:*:*:*:*
cpe:2.3:o:amd:ryzen_3_pro_4350ge_firmware:-:*:*:*:*:*:*:*
cpe:2.3:o:amd:ryzen_3_pro_4350ge_firmware:-:*:*:*:*:*:*:*
cpe:2.3:h:amd:ryzen_3_pro_4350ge:-:*:*:*:*:*:*:*
cpe:2.3:h:amd:ryzen_3_pro_4350ge:-:*:*:*:*:*:*:*
cpe:2.3:o:amd:ryzen_3_pro_4350g_firmware:-:*:*:*:*:*:*:*
cpe:2.3:o:amd:ryzen_3_pro_4350g_firmware:-:*:*:*:*:*:*:*
cpe:2.3:h:amd:ryzen_3_pro_4350g:-:*:*:*:*:*:*:*
cpe:2.3:h:amd:ryzen_3_pro_4350g:-:*:*:*:*:*:*:*
cpe:2.3:o:amd:ryzen_3_pro_4200g_firmware:-:*:*:*:*:*:*:*
cpe:2.3:o:amd:ryzen_3_pro_4200g_firmware:-:*:*:*:*:*:*:*
cpe:2.3:h:amd:ryzen_3_pro_4200g:-:*:*:*:*:*:*:*
cpe:2.3:h:amd:ryzen_3_pro_4200g:-:*:*:*:*:*:*:*
cpe:2.3:o:amd:ryzen_5_pro_4650ge_firmware:-:*:*:*:*:*:*:*
cpe:2.3:o:amd:ryzen_5_pro_4650ge_firmware:-:*:*:*:*:*:*:*
cpe:2.3:h:amd:ryzen_5_pro_4650ge:-:*:*:*:*:*:*:*
cpe:2.3:h:amd:ryzen_5_pro_4650ge:-:*:*:*:*:*:*:*
cpe:2.3:o:amd:ryzen_5_pro_4650g_firmware:-:*:*:*:*:*:*:*
cpe:2.3:o:amd:ryzen_5_pro_4650g_firmware:-:*:*:*:*:*:*:*
cpe:2.3:h:amd:ryzen_5_pro_4650g:-:*:*:*:*:*:*:*
cpe:2.3:h:amd:ryzen_5_pro_4650g:-:*:*:*:*:*:*:*
cpe:2.3:o:amd:ryzen_5_pro_4400g_firmware:-:*:*:*:*:*:*:*
cpe:2.3:o:amd:ryzen_5_pro_4400g_firmware:-:*:*:*:*:*:*:*
cpe:2.3:h:amd:ryzen_5_pro_4400g:-:*:*:*:*:*:*:*
cpe:2.3:h:amd:ryzen_5_pro_4400g:-:*:*:*:*:*:*:*
cpe:2.3:o:amd:ryzen_7_pro_4750u_firmware:-:*:*:*:*:*:*:*
cpe:2.3:o:amd:ryzen_7_pro_4750u_firmware:-:*:*:*:*:*:*:*
cpe:2.3:h:amd:ryzen_7_pro_4750u:-:*:*:*:*:*:*:*
cpe:2.3:h:amd:ryzen_7_pro_4750u:-:*:*:*:*:*:*:*
cpe:2.3:o:amd:ryzen_7_pro_4750ge_firmware:-:*:*:*:*:*:*:*
cpe:2.3:o:amd:ryzen_7_pro_4750ge_firmware:-:*:*:*:*:*:*:*
cpe:2.3:h:amd:ryzen_7_pro_4750ge:-:*:*:*:*:*:*:*
cpe:2.3:h:amd:ryzen_7_pro_4750ge:-:*:*:*:*:*:*:*
cpe:2.3:o:amd:ryzen_7_pro_4750g_firmware:-:*:*:*:*:*:*:*
cpe:2.3:o:amd:ryzen_7_pro_4750g_firmware:-:*:*:*:*:*:*:*
cpe:2.3:h:amd:ryzen_7_pro_4750g:-:*:*:*:*:*:*:*
cpe:2.3:h:amd:ryzen_7_pro_4750g:-:*:*:*:*:*:*:*
cpe:2.3:o:amd:ryzen_7_5700u_firmware:-:*:*:*:*:*:*:*
cpe:2.3:o:amd:ryzen_7_5700u_firmware:-:*:*:*:*:*:*:*
cpe:2.3:h:amd:ryzen_7_5700u:-:*:*:*:*:*:*:*
cpe:2.3:h:amd:ryzen_7_5700u:-:*:*:*:*:*:*:*
cpe:2.3:o:amd:ryzen_5_5500u_firmware:-:*:*:*:*:*:*:*
cpe:2.3:o:amd:ryzen_5_5500u_firmware:-:*:*:*:*:*:*:*
cpe:2.3:h:amd:ryzen_5_5500u:-:*:*:*:*:*:*:*
cpe:2.3:h:amd:ryzen_5_5500u:-:*:*:*:*:*:*:*
cpe:2.3:o:amd:ryzen_3_5300u_firmware:-:*:*:*:*:*:*:*
cpe:2.3:o:amd:ryzen_3_5300u_firmware:-:*:*:*:*:*:*:*
cpe:2.3:h:amd:ryzen_3_5300u:-:*:*:*:*:*:*:*
cpe:2.3:h:amd:ryzen_3_5300u:-:*:*:*:*:*:*:*
cpe:2.3:o:amd:ryzen_5_7520u_firmware:-:*:*:*:*:*:*:*
cpe:2.3:o:amd:ryzen_5_7520u_firmware:-:*:*:*:*:*:*:*
cpe:2.3:h:amd:ryzen_5_7520u:-:*:*:*:*:*:*:*
cpe:2.3:h:amd:ryzen_5_7520u:-:*:*:*:*:*:*:*
cpe:2.3:o:amd:ryzen_3_7320u_firmware:-:*:*:*:*:*:*:*
cpe:2.3:o:amd:ryzen_3_7320u_firmware:-:*:*:*:*:*:*:*
cpe:2.3:h:amd:ryzen_3_7320u:-:*:*:*:*:*:*:*
cpe:2.3:h:amd:ryzen_3_7320u:-:*:*:*:*:*:*:*
cpe:2.3:o:amd:athlon_gold_7220u_firmware:-:*:*:*:*:*:*:*
cpe:2.3:o:amd:athlon_gold_7220u_firmware:-:*:*:*:*:*:*:*
cpe:2.3:h:amd:athlon_gold_7220u:-:*:*:*:*:*:*:*
cpe:2.3:h:amd:athlon_gold_7220u:-:*:*:*:*:*:*:*
cpe:2.3:o:amd:epyc_7232p_firmware:-:*:*:*:*:*:*:*
cpe:2.3:o:amd:epyc_7232p_firmware:-:*:*:*:*:*:*:*
cpe:2.3:h:amd:epyc_7232p:-:*:*:*:*:*:*:*
cpe:2.3:h:amd:epyc_7232p:-:*:*:*:*:*:*:*
cpe:2.3:o:amd:epyc_7302p_firmware:-:*:*:*:*:*:*:*
cpe:2.3:o:amd:epyc_7302p_firmware:-:*:*:*:*:*:*:*
cpe:2.3:h:amd:epyc_7302p:-:*:*:*:*:*:*:*
cpe:2.3:h:amd:epyc_7302p:-:*:*:*:*:*:*:*
cpe:2.3:o:amd:epyc_7402p_firmware:-:*:*:*:*:*:*:*
cpe:2.3:o:amd:epyc_7402p_firmware:-:*:*:*:*:*:*:*
cpe:2.3:h:amd:epyc_7402p:-:*:*:*:*:*:*:*
cpe:2.3:h:amd:epyc_7402p:-:*:*:*:*:*:*:*
cpe:2.3:o:amd:epyc_7502p_firmware:-:*:*:*:*:*:*:*
cpe:2.3:o:amd:epyc_7502p_firmware:-:*:*:*:*:*:*:*
cpe:2.3:h:amd:epyc_7502p:-:*:*:*:*:*:*:*
cpe:2.3:h:amd:epyc_7502p:-:*:*:*:*:*:*:*
cpe:2.3:o:amd:epyc_7702p_firmware:-:*:*:*:*:*:*:*
cpe:2.3:o:amd:epyc_7702p_firmware:-:*:*:*:*:*:*:*
cpe:2.3:h:amd:epyc_7702p:-:*:*:*:*:*:*:*
cpe:2.3:h:amd:epyc_7702p:-:*:*:*:*:*:*:*
cpe:2.3:o:amd:epyc_7252_firmware:-:*:*:*:*:*:*:*
cpe:2.3:o:amd:epyc_7252_firmware:-:*:*:*:*:*:*:*
cpe:2.3:h:amd:epyc_7252:-:*:*:*:*:*:*:*
cpe:2.3:h:amd:epyc_7252:-:*:*:*:*:*:*:*
cpe:2.3:o:amd:epyc_7262_firmware:-:*:*:*:*:*:*:*
cpe:2.3:o:amd:epyc_7262_firmware:-:*:*:*:*:*:*:*
cpe:2.3:h:amd:epyc_7262:-:*:*:*:*:*:*:*
cpe:2.3:h:amd:epyc_7262:-:*:*:*:*:*:*:*
cpe:2.3:o:amd:epyc_7272_firmware:-:*:*:*:*:*:*:*
cpe:2.3:o:amd:epyc_7272_firmware:-:*:*:*:*:*:*:*
cpe:2.3:h:amd:epyc_7272:-:*:*:*:*:*:*:*
cpe:2.3:h:amd:epyc_7272:-:*:*:*:*:*:*:*
cpe:2.3:o:amd:epyc_7282_firmware:-:*:*:*:*:*:*:*
cpe:2.3:o:amd:epyc_7282_firmware:-:*:*:*:*:*:*:*
cpe:2.3:h:amd:epyc_7282:-:*:*:*:*:*:*:*
cpe:2.3:h:amd:epyc_7282:-:*:*:*:*:*:*:*
cpe:2.3:o:amd:epyc_7302_firmware:-:*:*:*:*:*:*:*
cpe:2.3:o:amd:epyc_7302_firmware:-:*:*:*:*:*:*:*
cpe:2.3:h:amd:epyc_7302:-:*:*:*:*:*:*:*
cpe:2.3:h:amd:epyc_7302:-:*:*:*:*:*:*:*
cpe:2.3:o:amd:epyc_7352_firmware:-:*:*:*:*:*:*:*
cpe:2.3:o:amd:epyc_7352_firmware:-:*:*:*:*:*:*:*
cpe:2.3:h:amd:epyc_7352:-:*:*:*:*:*:*:*
cpe:2.3:h:amd:epyc_7352:-:*:*:*:*:*:*:*
cpe:2.3:o:amd:epyc_7402_firmware:-:*:*:*:*:*:*:*
cpe:2.3:o:amd:epyc_7402_firmware:-:*:*:*:*:*:*:*
cpe:2.3:h:amd:epyc_7402:-:*:*:*:*:*:*:*
cpe:2.3:h:amd:epyc_7402:-:*:*:*:*:*:*:*
cpe:2.3:o:amd:epyc_7452_firmware:-:*:*:*:*:*:*:*
cpe:2.3:o:amd:epyc_7452_firmware:-:*:*:*:*:*:*:*
cpe:2.3:h:amd:epyc_7452:-:*:*:*:*:*:*:*
cpe:2.3:h:amd:epyc_7452:-:*:*:*:*:*:*:*
cpe:2.3:o:amd:epyc_7502_firmware:-:*:*:*:*:*:*:*
cpe:2.3:o:amd:epyc_7502_firmware:-:*:*:*:*:*:*:*
cpe:2.3:h:amd:epyc_7502:-:*:*:*:*:*:*:*
cpe:2.3:h:amd:epyc_7502:-:*:*:*:*:*:*:*
cpe:2.3:o:amd:epyc_7532_firmware:-:*:*:*:*:*:*:*
cpe:2.3:o:amd:epyc_7532_firmware:-:*:*:*:*:*:*:*
cpe:2.3:h:amd:epyc_7532:-:*:*:*:*:*:*:*
cpe:2.3:h:amd:epyc_7532:-:*:*:*:*:*:*:*
cpe:2.3:o:amd:epyc_7542_firmware:-:*:*:*:*:*:*:*
cpe:2.3:o:amd:epyc_7542_firmware:-:*:*:*:*:*:*:*
cpe:2.3:h:amd:epyc_7542:-:*:*:*:*:*:*:*
cpe:2.3:h:amd:epyc_7542:-:*:*:*:*:*:*:*
cpe:2.3:o:amd:epyc_7552_firmware:-:*:*:*:*:*:*:*
cpe:2.3:o:amd:epyc_7552_firmware:-:*:*:*:*:*:*:*
cpe:2.3:h:amd:epyc_7552:-:*:*:*:*:*:*:*
cpe:2.3:h:amd:epyc_7552:-:*:*:*:*:*:*:*
cpe:2.3:o:amd:epyc_7642_firmware:-:*:*:*:*:*:*:*
cpe:2.3:o:amd:epyc_7642_firmware:-:*:*:*:*:*:*:*
cpe:2.3:h:amd:epyc_7642:-:*:*:*:*:*:*:*
cpe:2.3:h:amd:epyc_7642:-:*:*:*:*:*:*:*
cpe:2.3:o:amd:epyc_7662_firmware:-:*:*:*:*:*:*:*
cpe:2.3:o:amd:epyc_7662_firmware:-:*:*:*:*:*:*:*
cpe:2.3:h:amd:epyc_7662:-:*:*:*:*:*:*:*
cpe:2.3:h:amd:epyc_7662:-:*:*:*:*:*:*:*
cpe:2.3:o:amd:epyc_7702_firmware:-:*:*:*:*:*:*:*
cpe:2.3:o:amd:epyc_7702_firmware:-:*:*:*:*:*:*:*
cpe:2.3:h:amd:epyc_7702:-:*:*:*:*:*:*:*
cpe:2.3:h:amd:epyc_7702:-:*:*:*:*:*:*:*
cpe:2.3:o:amd:epyc_7742_firmware:-:*:*:*:*:*:*:*
cpe:2.3:o:amd:epyc_7742_firmware:-:*:*:*:*:*:*:*
cpe:2.3:h:amd:epyc_7742:-:*:*:*:*:*:*:*
cpe:2.3:h:amd:epyc_7742:-:*:*:*:*:*:*:*
cpe:2.3:o:amd:epyc_7h12_firmware:-:*:*:*:*:*:*:*
cpe:2.3:o:amd:epyc_7h12_firmware:-:*:*:*:*:*:*:*
cpe:2.3:h:amd:epyc_7h12:-:*:*:*:*:*:*:*
cpe:2.3:h:amd:epyc_7h12:-:*:*:*:*:*:*:*
cpe:2.3:o:amd:epyc_7f32_firmware:-:*:*:*:*:*:*:*
cpe:2.3:o:amd:epyc_7f32_firmware:-:*:*:*:*:*:*:*
cpe:2.3:h:amd:epyc_7f32:-:*:*:*:*:*:*:*
cpe:2.3:h:amd:epyc_7f32:-:*:*:*:*:*:*:*
cpe:2.3:o:amd:epyc_7f52_firmware:-:*:*:*:*:*:*:*
cpe:2.3:o:amd:epyc_7f52_firmware:-:*:*:*:*:*:*:*
cpe:2.3:h:amd:epyc_7f52:-:*:*:*:*:*:*:*
cpe:2.3:h:amd:epyc_7f52:-:*:*:*:*:*:*:*
cpe:2.3:o:amd:epyc_7f72_firmware:-:*:*:*:*:*:*:*
cpe:2.3:o:amd:epyc_7f72_firmware:-:*:*:*:*:*:*:*
cpe:2.3:h:amd:epyc_7f72:-:*:*:*:*:*:*:*
cpe:2.3:h:amd:epyc_7f72:-:*:*:*:*:*:*:*

Protect Your Infrastructure against CVE-2023-20593: 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-3103 – The CLEVER - HTML5 Radio Player With History - Shoutcast and Icecast - Elementor Widget Addon plugin for WordPress is vulnerable to arbitrary file ...
CVE-2025-3275 – The Themesflat Addons For Elementor plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the TF E Slider widget in all versions up...
CVE-2025-1457 – The Element Pack Addons for Elementor – Free Templates and Widgets for Your WordPress Websites plugin for WordPress is vulnerable to Stored Cross-S...
CVE-2025-1093 – The AIHub theme for WordPress is vulnerable to arbitrary file uploads due to missing file type validation in the generate_image function in all ver...
CVE-2025-3284 – The User Registration & Membership – Custom Registration Form, Login Form, and User Profile plugin for WordPress is vulnerable to Cross-Site Reques...