1-minute read of a 4 min report

Signed UEFI shells bypass Secure Boot before the OS starts

By

1-minute read

What a defender needs to know

CERT/CC lists vendor-signed UEFI Shell applications that Secure Boot can authorize even though their diagnostic commands can modify protected pre-boot memory. The issue affects systems that trust the relevant vendor certificate or listed application Authenticode hash in UEFI DB and where an attacker with physical access or administrative privileges can launch the shell. Code running at that stage precedes operating-system and EDR monitoring.

Match UEFI-shell SHA-256 file hashes in firmware packages or distributed utilities to CERT/CC’s affected-binary table, then compare the corresponding signing trust with each affected machine’s DB. Scope exposure by the matching binary and each machine’s boot trust and revocation state. Coordinate model-specific firmware updates with the hardware vendor, and update DBX to revoke the older vulnerable binary or, where required, its certificate. Plan for boot and recovery compatibility before changing signing trust.

After rollout, verify that the updated firmware replaces the affected shell, that the previous binary is rejected under the updated DBX, and that normal signed boot succeeds. Firmware and boot-chain investigation is warranted for a previously exposed machine when an attacker had physical or administrative access: ordinary OS logs offer limited visibility into pre-OS execution. Eclypsium’s earlier Framework research separates shell fixes from revocation updates, so inspect both control states.

Primary sources