Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

CVE-2025-0033: CWE-284 Improper Access Control in AMD AMD EPYC™ 7003 Series Processors (formerly codenamed "Milan")

0
Medium
VulnerabilityCVE-2025-0033cvecve-2025-0033cwe-284
Published: Tue Oct 14 2025 (10/14/2025, 14:49:03 UTC)
Source: CVE Database V5
Vendor/Project: AMD
Product: AMD EPYC™ 7003 Series Processors (formerly codenamed "Milan")

Description

Improper access control within AMD SEV-SNP could allow an admin privileged attacker to write to the RMP during SNP initialization, potentially resulting in a loss of SEV-SNP guest memory integrity.

AI-Powered Analysis

AILast updated: 10/14/2025, 15:22:36 UTC

Technical Analysis

CVE-2025-0033 is a vulnerability categorized under CWE-284 (Improper Access Control) affecting AMD EPYC 7003 Series processors, also known as Milan. The flaw resides in the AMD SEV-SNP (Secure Encrypted Virtualization - Secure Nested Paging) feature, which is designed to protect virtual machine memory confidentiality and integrity by encrypting guest memory and preventing unauthorized access. Specifically, the vulnerability allows an attacker with administrative privileges on the host system to write to the Reverse Map Table (RMP) during the initialization phase of SEV-SNP. The RMP is critical for maintaining the mapping between guest physical addresses and host physical addresses, ensuring memory integrity and isolation. By improperly controlling access to the RMP, the attacker can potentially corrupt or manipulate the guest memory mappings, leading to a loss of memory integrity for SEV-SNP guests. This could undermine the security guarantees of SEV-SNP, allowing for potential data corruption or unauthorized data access within protected virtual machines. The CVSS v3.1 score is 6.0 (medium severity), reflecting that exploitation requires local access with high privileges but no user interaction, and the impact is limited to integrity without affecting confidentiality or availability directly. No known exploits have been reported in the wild as of the publication date. The vulnerability highlights the importance of robust access control mechanisms in hardware-based virtualization security features.

Potential Impact

For European organizations, especially those operating cloud services, data centers, or virtualized environments using AMD EPYC 7003 processors, this vulnerability poses a significant risk to the integrity of virtual machine workloads protected by SEV-SNP. Compromise of guest memory integrity could lead to data corruption, unauthorized modification of sensitive information, or undermining of trust in secure virtualization environments. This is particularly critical for sectors handling sensitive data such as finance, healthcare, and government services. While confidentiality is not directly impacted, the integrity loss could facilitate further attacks or data manipulation. The requirement for administrative privileges limits the attack vector to insiders or attackers who have already gained elevated access, but the potential damage within a multi-tenant cloud environment or critical infrastructure is substantial. Organizations relying on AMD SEV-SNP for confidential computing must consider this vulnerability in their risk assessments and incident response planning.

Mitigation Recommendations

To mitigate CVE-2025-0033, European organizations should implement the following specific measures: 1) Enforce strict access controls and monitoring on administrative accounts to prevent unauthorized privilege escalation or misuse. 2) Limit the number of users with high-level privileges on hosts running AMD EPYC 7003 processors and SEV-SNP enabled virtual machines. 3) Monitor system logs and audit trails for unusual activities related to SEV-SNP initialization and RMP modifications. 4) Apply firmware, microcode, or software patches provided by AMD as soon as they become available to address this vulnerability. 5) Employ hardware attestation and integrity verification tools to detect anomalies in SEV-SNP guest memory mappings. 6) Consider additional isolation measures such as network segmentation and strict tenant separation in multi-tenant environments. 7) Engage with cloud service providers to confirm their patching status and mitigation strategies if using hosted infrastructure. These steps go beyond generic advice by focusing on administrative privilege management and monitoring specific to the vulnerable component.

Need more detailed analysis?Get Pro

Technical Details

Data Version
5.1
Assigner Short Name
AMD
Date Reserved
2024-11-21T16:17:59.196Z
Cvss Version
3.1
State
PUBLISHED

Threat ID: 68ee6aa71b3029e3c7dc1688

Added to database: 10/14/2025, 3:22:15 PM

Last enriched: 10/14/2025, 3:22:36 PM

Last updated: 10/16/2025, 2:43:42 PM

Views: 38

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need enhanced features?

Contact root@offseq.com for Pro access with improved analysis and higher rate limits.

Latest Threats