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-2024-37987: CWE-843: Access of Resource Using Incompatible Type ('Type Confusion') in Microsoft Windows 10 Version 1809

0
High
VulnerabilityCVE-2024-37987cvecve-2024-37987cwe-843cwe-122
Published: Tue Jul 09 2024 (07/09/2024, 17:02:21 UTC)
Source: CVE
Vendor/Project: Microsoft
Product: Windows 10 Version 1809

Description

Secure Boot Security Feature Bypass Vulnerability

AI-Powered Analysis

Machine-generated threat intelligence

AILast updated: 02/11/2026, 10:29:20 UTC

Technical Analysis

CVE-2024-37987 is a vulnerability classified under CWE-843 (Access of Resource Using Incompatible Type, or type confusion) affecting Microsoft Windows 10 Version 1809 (build 10.0.17763.0). The flaw allows an attacker to bypass the Secure Boot security feature, which is designed to ensure that only trusted software is loaded during the system boot process. The vulnerability arises from improper handling of data types within the Secure Boot mechanism, leading to a scenario where an attacker can manipulate the boot process to load unauthorized or malicious code. The CVSS v3.1 base score is 8.0, indicating high severity, with an attack vector of adjacent network (AV:A), low attack complexity (AC:L), no privileges required (PR:N), but requiring user interaction (UI:R). The scope is unchanged (S:U), and the impact on confidentiality, integrity, and availability is high (C:H/I:H/A:H). This means that exploitation can lead to full system compromise, including unauthorized access, data tampering, and denial of service. Although no exploits are currently known in the wild, the vulnerability's nature and impact make it a significant risk. The vulnerability was reserved in June 2024 and published in July 2024, with no patches currently listed, indicating that mitigation options may be limited to workarounds or upgrading to newer Windows versions. The vulnerability is particularly critical because Secure Boot is a foundational security control in modern Windows systems, and bypassing it undermines the trustworthiness of the entire boot chain.

Potential Impact

For European organizations, especially those relying on Windows 10 Version 1809, this vulnerability poses a serious threat. Compromise of Secure Boot can enable attackers to execute persistent, stealthy malware at the earliest stage of system startup, evading many traditional security controls. This can lead to widespread data breaches, disruption of critical services, and potential espionage or sabotage. Sectors such as government, finance, energy, and healthcare, which often use legacy Windows versions due to compatibility requirements, are particularly vulnerable. The high impact on confidentiality, integrity, and availability means that sensitive data and critical infrastructure could be severely affected. Additionally, the requirement for user interaction may limit large-scale automated exploitation but does not eliminate targeted attacks, especially spear-phishing or social engineering campaigns common in Europe. The lack of known exploits in the wild currently provides a window for proactive defense, but the presence of a high-severity vulnerability in a widely used OS version demands urgent attention.

Mitigation Recommendations

1. Upgrade affected systems from Windows 10 Version 1809 to a supported and patched version of Windows 10 or Windows 11, as Microsoft typically addresses such vulnerabilities in newer releases. 2. Monitor Microsoft security advisories closely for the release of patches specifically addressing CVE-2024-37987 and apply them promptly. 3. Implement strict user interaction controls, such as disabling or restricting the execution of untrusted applications and enforcing application whitelisting, to reduce the risk of exploitation requiring user action. 4. Enhance endpoint detection and response (EDR) capabilities to identify anomalous boot processes or unauthorized modifications to boot components. 5. Employ network segmentation and limit exposure of systems running Windows 10 1809 to adjacent network threats, as the attack vector is adjacent network. 6. Conduct user awareness training focused on social engineering and phishing to reduce the likelihood of user interaction leading to exploitation. 7. Regularly audit and inventory systems to identify those running the vulnerable Windows version and prioritize their remediation. 8. Consider implementing hardware-based security features such as TPM and secure firmware updates to strengthen boot integrity.

Pro Console: star threats, build custom feeds, automate alerts via Slack, email & webhooks.Upgrade to Pro

Technical Details

Data Version
5.1
Assigner Short Name
microsoft
Date Reserved
2024-06-10T21:22:19.231Z
Cisa Enriched
true
Cvss Version
3.1
State
PUBLISHED

Threat ID: 682d981dc4522896dcbdb72c

Added to database: 5/21/2025, 9:08:45 AM

Last enriched: 2/11/2026, 10:29:20 AM

Last updated: 3/24/2026, 8:37:19 PM

Views: 58

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 more coverage?

Upgrade to Pro Console for AI refresh and higher limits.

For incident response and remediation, OffSeq services can help resolve threats faster.

Latest Threats

Breach by OffSeqOFFSEQFRIENDS — 25% OFF

Check if your credentials are on the dark web

Instant breach scanning across billions of leaked records. Free tier available.

Scan now
OffSeq TrainingCredly Certified

Lead Pen Test Professional

Technical5-day eLearningPECB Accredited
View courses