CVE-2023-24932

Published May 9, 2023

Last updated 2 years ago

Overview

AI description

Automated description summarized from trusted sources.

CVE-2023-24932 is a Secure Boot bypass vulnerability found in the Windows Boot Manager. This flaw allows an attacker with administrative privileges or physical access to a device to circumvent Secure Boot protections. The vulnerability is often exploited by replacing a modern, secure bootloader with an older, vulnerable version that is still recognized as trusted by the system. By exploiting this vulnerability, attackers can execute untrusted software during the boot process, potentially establishing persistence at the firmware level. This can allow them to bypass security mechanisms such as BitLocker and traditional antivirus solutions. The vulnerability has been notably associated with the BlackLotus UEFI bootkit.

Description
Secure Boot Security Feature Bypass Vulnerability
Source
secure@microsoft.com
NVD status
Modified

Risk scores

CVSS 3.1

Type
Primary
Base score
6.7
Impact score
5.9
Exploitability score
0.8
Vector string
CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H
Severity
MEDIUM

Weaknesses

nvd@nist.gov
NVD-CWE-noinfo
134c704f-9b21-4f2e-91b3-4a467353bcc0
CWE-863

Social media

Hype score
Not currently trending
  1. Put together a full BPMN process diagram for the Secure Boot 2026 certificate deployment. Four lanes: Assessment, BIOS Updates, Phase 1 (certificate deployment), Phase 2 (revocation + SVN enforcement). This is what the complete CVE-2023-24932 remediation looks like end to end. h

    @kaidja

    22 Mar 2026

    1945 Impressions

    8 Retweets

    24 Likes

    20 Bookmarks

    0 Replies

    0 Quotes

  2. Just completed the full CVE-2023-24932 remediation on an enterprise Lenovo device. All four mitigations done. FirmwareSVN: 7.0. Compliant. Here is what most people do not know: the Intune Settings Catalog policy and Microsoft's 2026 Secure Boot playbook only cover mitigations ht

    @kaidja

    22 Mar 2026

    4611 Impressions

    18 Retweets

    57 Likes

    67 Bookmarks

    0 Replies

    0 Quotes

  3. 前に検証が中途半端になってたやつの検証終わったので、自動処理スクリプトもついでに公開 再起動を跨いで自律完走するセキュアブート(CVE-2023-24932)自動更新スクリプトの実装|はちくわ https://t.co/yBwh97vQu6

    @8chikuwa3

    4 Mar 2026

    507 Impressions

    2 Retweets

    6 Likes

    2 Bookmarks

    2 Replies

    0 Quotes

  4. Cybersecurity alert! Protect your system from the Black Lotus vulnerability (CVE-2023-24932) targeting Secure Boot. Here's what admins need to know to safeguard their devices. Don’t wait until it’s too late. Act now #CyberSecurity #InfoSec #CVE2023 https://t.co/29RYguGLBm

    @cheinyeanlim

    23 Mar 2025

    35 Impressions

    0 Retweets

    0 Likes

    0 Bookmarks

    0 Replies

    0 Quotes

  5. Actively exploited CVE : CVE-2023-24932

    @transilienceai

    25 Feb 2025

    13 Impressions

    0 Retweets

    0 Likes

    0 Bookmarks

    1 Reply

    0 Quotes

  6. Actively exploited CVE : CVE-2023-24932

    @transilienceai

    24 Feb 2025

    6 Impressions

    0 Retweets

    0 Likes

    0 Bookmarks

    1 Reply

    0 Quotes

  7. Patch Tuesday and no update on the enforcement date for KB5025885: How to manage the Windows Boot Manager revocations for Secure Boot changes associated with CVE-2023-24932 Still waiting.. #Windows11 #Windows10 https://t.co/mrwQ3xlBYp

    @ccmexec

    14 Jan 2025

    2828 Impressions

    9 Retweets

    21 Likes

    6 Bookmarks

    2 Replies

    0 Quotes

Configurations

  1. In the Linux kernel, the following vulnerability has been resolved: scsi: qla2xxx: Fix bsg_done() causing double free Kernel panic observed on system, [5353358.825191] BUG: unable to handle page fault for address: ff5f5e897b024000 [5353358.825194] #PF: supervisor write access in kernel mode [5353358.825195] #PF: error_code(0x0002) - not-present page [5353358.825196] PGD 100006067 P4D 0 [5353358.825198] Oops: 0002 [#1] PREEMPT SMP NOPTI [5353358.825200] CPU: 5 PID: 2132085 Comm: qlafwupdate.sub Kdump: loaded Tainted: G W L ------- --- 5.14.0-503.34.1.el9_5.x86_64 #1 [5353358.825203] Hardware name: HPE ProLiant DL360 Gen11/ProLiant DL360 Gen11, BIOS 2.44 01/17/2025 [5353358.825204] RIP: 0010:memcpy_erms+0x6/0x10 [5353358.825211] RSP: 0018:ff591da8f4f6b710 EFLAGS: 00010246 [5353358.825212] RAX: ff5f5e897b024000 RBX: 0000000000007090 RCX: 0000000000001000 [5353358.825213] RDX: 0000000000001000 RSI: ff591da8f4fed090 RDI: ff5f5e897b024000 [5353358.825214] RBP: 0000000000010000 R08: ff5f5e897b024000 R09: 0000000000000000 [5353358.825215] R10: ff46cf8c40517000 R11: 0000000000000001 R12: 0000000000008090 [5353358.825216] R13: ff591da8f4f6b720 R14: 0000000000001000 R15: 0000000000000000 [5353358.825218] FS: 00007f1e88d47740(0000) GS:ff46cf935f940000(0000) knlGS:0000000000000000 [5353358.825219] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 [5353358.825220] CR2: ff5f5e897b024000 CR3: 0000000231532004 CR4: 0000000000771ef0 [5353358.825221] PKRU: 55555554 [5353358.825222] Call Trace: [5353358.825223] <TASK> [5353358.825224] ? show_trace_log_lvl+0x1c4/0x2df [5353358.825229] ? show_trace_log_lvl+0x1c4/0x2df [5353358.825232] ? sg_copy_buffer+0xc8/0x110 [5353358.825236] ? __die_body.cold+0x8/0xd [5353358.825238] ? page_fault_oops+0x134/0x170 [5353358.825242] ? kernelmode_fixup_or_oops+0x84/0x110 [5353358.825244] ? exc_page_fault+0xa8/0x150 [5353358.825247] ? asm_exc_page_fault+0x22/0x30 [5353358.825252] ? memcpy_erms+0x6/0x10 [5353358.825253] sg_copy_buffer+0xc8/0x110 [5353358.825259] qla2x00_process_vendor_specific+0x652/0x1320 [qla2xxx] [5353358.825317] qla24xx_bsg_request+0x1b2/0x2d0 [qla2xxx] Most routines in qla_bsg.c call bsg_done() only for success cases. However a few invoke it for failure case as well leading to a double free. Validate before calling bsg_done().CVE-2025-71238

References

Sources include official advisories and independent security research.