chipsec.library.uefi.dbx module

Helpers for comparing a live UEFI dbx variable with Microsoft’s Secure Boot DBX reference JSON. Used by chipsec_util uefi dbx-check.

The check compares the live UEFI dbx (forbidden signatures) variable against Microsoft’s published Secure Boot DBX reference and reports any reference entries that are missing from the platform. This helps determine whether the platform has received the DBX updates that revoke known-vulnerable bootloaders (e.g. BootHole, CVE-2020-10713).

Before running, download the reference JSON from the Microsoft secureboot_objects repository and save it locally:

https://github.com/microsoft/secureboot_objects/blob/main/PreSignedObjects/DBX/dbx_info_msft_latest.json

CHIPSEC reads only this local file and never connects to the network.

>>> chipsec_util uefi dbx-check <architecture> <microsoft_dbx_json>

Arguments:

<architecture> Firmware architecture to check: x64, ia32, aarch64, or arm <microsoft_dbx_json> Path to the downloaded dbx_info_msft_latest.json

The check compares:

  • Authenticode SHA-256 image hashes (EFI_CERT_SHA256_GUID entries)

  • X.509 certificate SHA-1 thumbprints (EFI_CERT_X509_GUID entries)

Output:

  • Logs whether Secure Boot is currently enabled

  • Lists the number and type of reference entries absent from dbx (up to 5 sample values per type), or reports that all entries are present

Limitations:

  • Only the supplied JSON snapshot is checked; results are only as current as the downloaded file

  • SVN (Security Version Number) revocation records are not evaluated

  • The active bootloader is not inspected; the check does not confirm whether a vulnerable binary is actually in use

  • Requires the CHIPSEC driver (reads live UEFI variables)

Examples:

>>> chipsec_util uefi dbx-check x64 dbx_info_msft_latest.json
>>> chipsec_util uefi dbx-check aarch64 C:\dbx\dbx_info_msft_latest.json