Skip to main content
CVE Vulnerability Database
Vulnerability Database/CVE-2024-37969

CVE-2024-37969: Windows 10 1507 Secure Boot Bypass Flaw

CVE-2024-37969 is a Secure Boot security feature bypass vulnerability in Microsoft Windows 10 1507 that allows attackers to circumvent boot-level protections. This article covers technical details, impact, and mitigations.

Updated:

CVE-2024-37969 Overview

CVE-2024-37969 is a Secure Boot security feature bypass vulnerability affecting a broad range of Microsoft Windows client and server operating systems. The flaw is tracked under [CWE-822: Untrusted Pointer Dereference] and carries a CVSS 3.1 base score of 8.0. Successful exploitation allows an attacker on an adjacent network to bypass Secure Boot integrity checks, undermining the trust chain that validates firmware and bootloader components at system startup. The vulnerability requires user interaction and impacts confidentiality, integrity, and availability of affected hosts. Microsoft addressed the issue through its Patch Tuesday servicing channel for supported Windows 10, Windows 11, and Windows Server releases.

Critical Impact

An attacker who bypasses Secure Boot can load unsigned or malicious pre-OS code, enabling bootkit persistence that survives operating system reinstallation and evades traditional endpoint controls.

Affected Products

  • Microsoft Windows 10 (versions 1507, 1607, 1809, 21H2, 22H2)
  • Microsoft Windows 11 (versions 21H2, 22H2, 23H2)
  • Microsoft Windows Server 2012, 2016, 2019, 2022, and Server 2022 23H2

Discovery Timeline

  • 2024-07-09 - CVE-2024-37969 published to NVD and Microsoft releases security update
  • 2026-06-17 - Last updated in NVD database

Technical Details for CVE-2024-37969

Vulnerability Analysis

CVE-2024-37969 is a Secure Boot bypass rooted in an untrusted pointer dereference condition ([CWE-822]) within the Windows boot trust validation path. Secure Boot is a Unified Extensible Firmware Interface (UEFI) feature that verifies the cryptographic signature of every component loaded before the operating system kernel executes. When the boot process dereferences a pointer whose value is influenced by attacker-controlled data, the integrity checks that gate execution of pre-OS binaries can be circumvented. An attacker who exploits this condition can execute code before Windows-based security controls initialize, placing the compromise below the operating system boundary.

Root Cause

The underlying weakness maps to [CWE-822] Untrusted Pointer Dereference. A component involved in Secure Boot validation dereferences a pointer that is not validated against expected memory regions or trust boundaries, allowing manipulated data to influence execution flow during early boot.

Attack Vector

The CVSS vector AV:A/AC:L/PR:N/UI:R indicates an adjacent-network attack path with user interaction required and no privileges needed. An attacker on the same logical network segment can deliver a crafted payload, such as a manipulated boot component or configuration artifact, that the user must load or accept. Once processed, the malformed pointer dereference bypasses signature enforcement and permits execution of unauthorized boot code. Because the compromise occurs before the operating system loads, downstream endpoint protections cannot observe or block the initial execution.

No public proof-of-concept or exploit code is listed for this CVE in the enriched data. See the Microsoft CVE-2024-37969 Advisory for vendor-specific technical detail.

Detection Methods for CVE-2024-37969

Indicators of Compromise

  • Unexpected changes to UEFI variables, the boot configuration data (BCD) store, or the EFI System Partition contents.
  • Presence of unsigned or unknown .efi binaries in \EFI\Microsoft\Boot\ or vendor EFI directories.
  • Secure Boot state transitions from enabled to disabled without an authorized administrative change.
  • Anomalous DBX (forbidden signature database) updates or missing revocation entries that should be present after patching.

Detection Strategies

  • Collect and baseline Get-SecureBootUEFI, Confirm-SecureBootUEFI, and TPM measured boot log output across the fleet to identify drift.
  • Monitor Windows Event Log channels Microsoft-Windows-Kernel-Boot and Microsoft-Windows-TPM-WMI for boot integrity anomalies.
  • Correlate patch deployment telemetry against systems still reporting pre-July 2024 build numbers on the affected Windows and Windows Server SKUs.

Monitoring Recommendations

  • Ingest UEFI and measured boot telemetry into a centralized SIEM or data lake for longitudinal comparison against known-good baselines.
  • Alert on any endpoint reporting Secure Boot as disabled, particularly on managed servers where the state should be static.
  • Track Microsoft servicing stack and cumulative update compliance across all listed Windows client and server versions.

How to Mitigate CVE-2024-37969

Immediate Actions Required

  • Apply the July 2024 Microsoft security updates that address CVE-2024-37969 to every affected Windows 10, Windows 11, and Windows Server host.
  • Confirm Secure Boot is enabled in UEFI firmware settings on all managed systems and enforce that state through hardware or configuration policy.
  • Restrict physical and adjacent-network access to endpoints where Secure Boot integrity is critical, including domain controllers and privileged workstations.
  • Audit boot configuration and EFI System Partition contents after patching to validate that no unauthorized components persisted.

Patch Information

Microsoft published fixes through the standard Windows Update and Microsoft Update Catalog channels on 2024-07-09. Refer to the Microsoft CVE-2024-37969 Advisory for the KB article numbers corresponding to each affected build. Servers running Windows Server 2012 and 2012 R2 require Extended Security Update (ESU) coverage to receive the fix.

Workarounds

  • No official workaround replaces the security update; patch application is the supported remediation path.
  • Where patching is delayed, disable installation of untrusted removable media and restrict network segments that could deliver boot-time payloads.
  • Enforce BitLocker with TPM+PIN to raise the cost of pre-boot tampering on high-value hosts.
bash
# Verify Secure Boot status and current OS build on Windows hosts
Confirm-SecureBootUEFI
Get-ComputerInfo -Property OsName,OsVersion,OsBuildNumber,WindowsVersion

# Inventory installed servicing updates to confirm July 2024 rollup is present
Get-HotFix | Sort-Object -Property InstalledOn -Descending | Select-Object -First 20

Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.

Default Legacy - Prefooter | Experience the World’s Most Advanced Cybersecurity Platform

Experience the Most Advanced Cybersecurity Platform

See how the world’s most intelligent, autonomous cybersecurity platform can protect your organization today and into the future.