Skip to main content
VulnerabilityPublished Updated

CVE-2023-43753: Intel(R) Processors with Intel(R) SGX · Information Disclosure

Affects Intel(R) Processors with Intel(R) SGXSource CVE Database V5

0

Not known to be exploited · CVSS 6.8 Medium.

Data as of 26 Oct 2026, 17:16 UTC

CVSS 4.0 base score
6.8Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.1% chance of exploitation in 30 days – higher than 4% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:4.0/AV:L/AC:H/AT:N/PR:H/UI:N/VC:H/VI:N/VA:N/SC:H/SI:N/SA:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 16 Sep 2024

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

AI-suggested

To mitigate CVE-2023-43753, European organizations should prioritize the following actions: 1) Apply Intel's official microcode and firmware updates as soon as they are released to address the improper conditions check in SGX. 2) Restrict and monitor privileged user access rigorously, employing the principle of least privilege and strong authentication mechanisms to reduce the risk of insider threats. 3) Implement robust auditing and logging of privileged operations on systems with SGX-enabled processors to detect suspicious activities promptly. 4) Where possible, isolate SGX-enabled systems in secure network segments with limited access to reduce exposure. 5) Review and update incident response plans to include scenarios involving SGX enclave data leakage. 6) Engage with hardware and software vendors to ensure all components interacting with SGX are up to date and configured securely. 7) Consider additional encryption or data protection layers at the application level to mitigate potential enclave data exposure. These measures go beyond generic advice by focusing on access control, monitoring, and layered defense tailored to the SGX environment.

Description

Improper conditions check in some Intel(R) Processors with Intel(R) SGX may allow a privileged user to potentially enable information disclosure via local access.

References

Community reviews

Loading reviews…