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-30084: CWE-367: Time-of-check Time-of-use (TOCTOU) Race Condition in Microsoft Windows 10 Version 1809

0
High
VulnerabilityCVE-2024-30084cvecve-2024-30084cwe-367
Published: Tue Jun 11 2024 (06/11/2024, 16:59:53 UTC)
Source: CVE
Vendor/Project: Microsoft
Product: Windows 10 Version 1809

Description

Windows Kernel-Mode Driver Elevation of Privilege Vulnerability

AI-Powered Analysis

AILast updated: 12/17/2025, 23:37:33 UTC

Technical Analysis

CVE-2024-30084 is a kernel-mode elevation of privilege vulnerability identified in Microsoft Windows 10 Version 1809 (build 10.0.17763.0). It stems from a Time-of-check Time-of-use (TOCTOU) race condition (CWE-367) within a Windows kernel driver. This race condition occurs when the system checks a condition and then uses the result without ensuring the state remains unchanged, allowing an attacker to manipulate the timing to cause inconsistent or unauthorized behavior. Specifically, an attacker with limited privileges and local access can exploit this flaw to escalate their privileges to higher levels, potentially SYSTEM or kernel-level privileges. The vulnerability has a CVSS 3.1 base score of 7.0, indicating high severity, with attack vector local (AV:L), attack complexity high (AC:H), privileges required low (PR:L), and no user interaction (UI:N). The impact on confidentiality, integrity, and availability is high, meaning a successful exploit could lead to full system compromise. No public exploit code or active exploitation has been reported yet. The vulnerability was reserved in March 2024 and published in June 2024. No patch links are currently provided, suggesting patches may be forthcoming or in progress. The vulnerability affects legacy Windows 10 systems, which remain in use in various enterprise and government environments. Because it requires local access and has high attack complexity, exploitation is more challenging but remains a significant risk for environments where untrusted users have local access or where attackers have already gained limited footholds.

Potential Impact

For European organizations, this vulnerability poses a significant risk primarily to those still operating Windows 10 Version 1809, which, despite being an older release, remains present in some enterprise and government systems due to legacy application dependencies or delayed upgrade cycles. Successful exploitation could allow attackers to elevate privileges from low-level user accounts to SYSTEM or kernel-level, enabling full control over affected machines. This could lead to data breaches, disruption of critical services, deployment of ransomware or other malware, and compromise of sensitive information. Sectors such as finance, healthcare, government, and critical infrastructure are particularly at risk due to the potential for severe operational and reputational damage. The requirement for local access limits remote exploitation but does not eliminate risk, especially in environments with shared workstations, remote desktop access, or insider threats. The lack of known exploits in the wild provides a window for proactive mitigation, but the high impact demands urgent attention.

Mitigation Recommendations

1. Monitor Microsoft security advisories closely and apply official patches immediately once released to address CVE-2024-30084. 2. Restrict local access to systems running Windows 10 Version 1809 by enforcing strict access controls and limiting administrative privileges. 3. Implement application whitelisting and endpoint detection and response (EDR) solutions to detect suspicious local activity indicative of privilege escalation attempts. 4. Conduct regular audits of user accounts and permissions to minimize the number of users with local access and low privilege accounts that could be leveraged. 5. Where possible, accelerate migration from Windows 10 Version 1809 to supported, fully patched versions of Windows 10 or Windows 11 to reduce exposure to legacy vulnerabilities. 6. Employ network segmentation to isolate legacy systems and reduce the risk of lateral movement following local compromise. 7. Educate IT staff and users about the risks of local privilege escalation vulnerabilities and the importance of maintaining updated systems. 8. Use multi-factor authentication and strong endpoint security policies to reduce the likelihood of initial foothold by attackers.

Need more detailed analysis?Upgrade to Pro Console

Technical Details

Data Version
5.1
Assigner Short Name
microsoft
Date Reserved
2024-03-22T23:12:15.570Z
Cisa Enriched
true
Cvss Version
3.1
State
PUBLISHED

Threat ID: 682cd0fa1484d88663aec102

Added to database: 5/20/2025, 6:59:06 PM

Last enriched: 12/17/2025, 11:37:33 PM

Last updated: 1/18/2026, 5:45:18 AM

Views: 62

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 in Console -> Billing for AI refresh and higher limits.

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

Latest Threats