Skip to content
WIRED·

🔓TianoCore UEFI Flaw Lets Attackers Own Boot Before OS Loads, Rated 9.5

Your fleet's boot firmware might be wide open

TL;DR

A 16-year-old buffer overflow in TianoCore EDK II's PXE driver scores 9.5 out of 10. Attackers can send one unicast packet to run ring 0 code before the OS loads. Servers and PXE-booting fleets need a BIOS/UEFI update.

A buffer overflow that's been sitting in TianoCore EDK II's PXE-Base Code driver for 16 years just got rated 9.5 out of 10. Attackers can hit it with a single unicast packet sent to a target's IP address, from basically any network distance. That packet plants a counterfeit event that runs malicious code in ring 0 before the OS or firmware defenses wake up. If your machines PXE boot, this is your problem. Servers, storage gear, and bare-metal provisioning setups that pull images over the local network are the exposed ones. Home and small office users who boot only from disk are safe. So are Intel's commercial products under active security support, which aren't known to be affected. The fix is a basic code change, but it means shipping a BIOS/UEFI update. The catch? Attestation won't save you, because the bug bypasses the cryptographic proof meant to show remote servers the hardware is clean. Fixing it doesn't require revoking keys or touching pk/kek/db/dbx, which makes rollout simpler. Expect this to be a forever bug on end-of-support hardware.

TianoCore UEFI Flaw Lets Attackers Own Boot Before OS Loads, Rated 9.5 — WIRED

Key Points

1

The flaw sits in NetworkPkg/UefiPxeBcDxe, the PXE-Base Code driver that lets devices boot code pulled from a local network.

Keep reading — it's free

Enter your email to keep reading — plus the best of AI & tech, daily. Free, forever.

Also get
or

Already a member? Sign in

UEFITianoCoreEDK2PXEfirmware-vulnerability

Comments

Subscribe to join the conversation...

Be the first to comment