CVE-2024-28047: Intel(R) Processors · Information Disclosure
Affects Intel(R) ProcessorsSource CVE Database V5
Not known to be exploited · CVSS 6.8 Medium.
Data as of 26 Oct 2026, 08:30 UTC
- EPSS
- 0.2% chance of exploitation in 30 days – higher than 16% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:4.0/AV:L/AC:H/AT:P/PR:H/UI:N/VC:H/VI:N/VA:N/SC:H/SI:N/SA:NExploitation evidence
Disclosed: evidence found.
CVE published 12 Feb 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by 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-2024-28047, European organizations should: 1) Monitor Intel and OEM advisories closely for firmware updates addressing this vulnerability and apply patches promptly once available. 2) Restrict privileged local access strictly, enforcing the principle of least privilege to reduce the risk of insider exploitation. 3) Implement robust endpoint security solutions that detect and prevent unauthorized privilege escalation or suspicious local activity. 4) Use hardware-based security features such as Intel Trusted Execution Technology (TXT) and secure boot to enhance firmware integrity. 5) Conduct regular audits of privileged accounts and access logs to detect anomalous behavior. 6) Educate system administrators and users with elevated privileges about the risks and signs of exploitation. 7) Consider network segmentation to limit the spread of an attacker who gains local access. 8) Employ firmware integrity verification tools where available to detect unauthorized modifications. These steps go beyond generic advice by focusing on controlling privileged access and monitoring firmware integrity in addition to patching.
Description
Improper input validation in UEFI firmware for some Intel(R) Processors may allow a privileged user to potentially enable information disclosure via local access.