EUVD-2025-210693
GHSA-xqm6-x399-jg2r
Severity by source
CVSS:4.0/AV:L/AC:H/AT:P/PR:H/UI:N/VC:N/VI:L/VA:L/SC:N/SI:H/SA:L/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
Local access and kernel privilege required per description; scope changes because SI:H downstream integrity impact propagates to attestation-relying systems.
Primary rating from Vendor (intel).
CVSS VectorVendor: intel
Lifecycle Timeline
1DescriptionCVE.org
Omission of security-relevant information for some Intel(R) Software Guard Extensions Data Center Attestation Primitives within Ring 0: Kernel may allow a denial of service. Authorized adversary with a privileged user combined with a high complexity attack may enable data alteration. This result may potentially occur via local access when attack requirements are present with special internal knowledge and requires no user interaction. The potential vulnerability may impact the confidentiality (none), integrity (low) and availability (low) of the vulnerable system, resulting in subsequent system confidentiality (none), integrity (high) and availability (low) impacts.
AnalysisAI
Intel Software Guard Extensions Data Center Attestation Primitives (SGX DCAP), operating at Ring 0 kernel privilege level, omits security-relevant information during attestation operations, enabling a privileged local attacker under high-complexity conditions to cause denial of service and high-integrity data alteration on downstream systems relying on attestation output. The SI:H subsequent-system integrity impact is the critical concern: systems that consume SGX attestation results - cloud orchestrators, confidential VM managers, or trust brokers - may accept manipulated evidence, undermining the core trust guarantees of confidential computing infrastructure. No public exploit code or CISA KEV listing exists at time of analysis, and the PR:H and AC:H prerequisites substantially constrain the realistic attacker pool.
Technical ContextAI
Intel SGX (Software Guard Extensions) provides hardware-based Trusted Execution Environments called enclaves. The Data Center Attestation Primitives (DCAP) component operates at Ring 0 (kernel privilege level) and enables remote attestation - the mechanism by which relying parties cryptographically verify that software executes within a genuine SGX enclave on authenticated Intel hardware. CWE-223 (Omission of Security-relevant Information) identifies the root cause: the implementation fails to include or propagate critical security context during attestation processing, allowing security-relevant states to be silently omitted from attestation evidence or Quote structures. The affected CPE (cpe:2.3:a:n/a:intel(r)_software_guard_extensions_data_center_attestation_primitives:*:*:*:*:*:*:*:*) uses a wildcard version, meaning all versions are nominally in scope pending the authoritative range defined by Intel advisory INTEL-SA-01421. The AT:P (attack requirements present) metric in the CVSS 4.0 vector explicitly calls out that 'special internal knowledge' of DCAP internals is required - a non-trivial prerequisite.
RemediationAI
Consult Intel Security Advisory INTEL-SA-01421 at https://intel.com/content/www/us/en/security-center/advisory/intel-sa-01421.html to obtain the specific patched version of Intel SGX DCAP - no fixed version number is identified in the available intelligence data, and version information must be sourced directly from Intel. Until patched, restrict kernel-level access to SGX DCAP interfaces to only the minimum set of authorized privileged accounts; given that PR:H is required for exploitation, enforcing strict administrative access controls substantially reduces exposure. Organizations using SGX attestation as a root-of-trust for critical workload admission decisions should consider implementing secondary attestation verification or out-of-band integrity checks until the patch is applied. Note that the high privilege and high complexity prerequisites mean urgency is significantly lower than for remotely exploitable vulnerabilities; however, confidential computing environments where attestation integrity is foundational should prioritize patching.
Same weakness CWE-223 – Omission of Security-relevant Information
View allSame technique Denial Of Service
View allShare
External POC / Exploit Code
Leaving vuln.today