How severe is CVE-2023-20599?

CVE-2023-20599 has a CVSS 3.x base score of 7.9, rated high severity. It is exploitable over local access with low attack complexity, requires high privileges and no user interaction. Impact on confidentiality is high, integrity high, and availability none.

Is CVE-2023-20599 being actively exploited?

It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (5th percentile), an estimate of the probability of exploitation in the next 30 days.

How do I fix CVE-2023-20599?

Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its high severity, prioritise patching exposed systems.

Does CVE-2023-20599 have an EU (EUVD) identifier?

Yes. CVE-2023-20599 is tracked in the ENISA EU Vulnerability Database (EUVD) as EUVD-2023-24778.

When was CVE-2023-20599 published?

CVE-2023-20599 was published on 2025-06-10 and last updated on 2026-06-17.

CVE-2023-20599

CVE-2023-20599 is a high-severity vulnerability with a CVSS 3.x base score of 7.9. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-1262.

Key facts

Severity: High (CVSS 3.x base score 7.9)
EPSS exploit prediction: 0% (5th percentile)
Actively exploited: Not listed in CISA KEV
EU (EUVD) id: EUVD-2023-24778
Weakness: CWE-1262
Published: 2025-06-10
Last modified: 2026-06-17

Description

Improper register access control in ASP may allow a privileged attacker to perform unauthorized access to ASP’s Crypto Co-Processor (CCP) registers from x86 resulting in potential loss of control of cryptographic key pointer/index leading to loss of integrity or confidentiality.

Frequently asked questions

What is CVE-2023-20599?: Improper register access control in ASP may allow a privileged attacker to perform unauthorized access to ASP’s Crypto Co-Processor (CCP) registers from x86 resulting in potential loss of control of cryptographic key pointer/index leading to loss of integrity or confidentiality.
How severe is CVE-2023-20599?: CVE-2023-20599 has a CVSS 3.x base score of 7.9, rated high severity. It is exploitable over local access with low attack complexity, requires high privileges and no user interaction. Impact on confidentiality is high, integrity high, and availability none.
Is CVE-2023-20599 being actively exploited?: It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (5th percentile), an estimate of the probability of exploitation in the next 30 days.
How do I fix CVE-2023-20599?: Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its high severity, prioritise patching exposed systems.
Does CVE-2023-20599 have an EU (EUVD) identifier?: Yes. CVE-2023-20599 is tracked in the ENISA EU Vulnerability Database (EUVD) as EUVD-2023-24778.
When was CVE-2023-20599 published?: CVE-2023-20599 was published on 2025-06-10 and last updated on 2026-06-17.

References

https://www.amd.com/en/resources/product-security/bulletin/AMD-SB-7039.html

Other CWE-1262 vulnerabilities

CVE-2025-47385 — High (CVSS 7.8): Memory Corruption when accessing trusted execution environment without proper privilege check.
CVE-2024-6354 — High (CVSS 7.2): Improper access control in PAM dashboard in Devolutions Remote Desktop Manager 2024.2.11 and earlier on Windows allows…
CVE-2024-45556 — Medium (CVSS 6.5): Cryptographic issue may arise because the access control configuration permits Linux to read key registers in TCSR.
CVE-2025-20788 — Medium (CVSS 4.4): In GPU pdma, there is a possible memory corruption due to a missing permission check. This could lead to local denial…
CVE-2025-54509 — Medium (CVSS 4.0): Improper access control for register interface in the input-output memory management unit (IOMMU) could allow a…
CVE-2025-36194 — Low (CVSS 2.8): IBM PowerVM Hypervisor FW1110.00 through FW1110.03, FW1060.00 through FW1060.51, and FW950.00 through FW950.F0 may…

Browse all CWE-1262 vulnerabilities →