Skip to main content
Mallory
← Back to News
adversary-emulation-tradecraftembedded-device-vulnerabilityoffensive-tooling-release

Research Highlights How Secure Boot Fails Despite Valid Signatures

Attack Tradecraft · 3 sources · Updated 3mo ago · First seen Aug 19, 2026

Research Highlights How Secure Boot Fails Despite Valid Signatures

A technical write-up published by 0x434b argues that Secure Boot can be bypassed without breaking cryptography when trust is lost elsewhere in the boot chain. The article frames Secure Boot as an end-to-end authorization system rather than a simple signature check and groups failures into four categories: verification that never ran or was not enforced, signatures that covered the wrong bytes, trust placed in the wrong signing authority, and cases where verified code differed from what ultimately executed. It cites public examples including CVE-2019-2278, CVE-2023-48425, CVE-2023-50810, CVE-2021-1931, and Android Verified Boot test keys left in production firmware to show how locked devices can still load unauthorized code.

The research also says measured boot and remote attestation only help if they independently measure the state that actually ran, warning that back-end trust decisions can fail when evidence does not reflect real execution. The post was amplified on r/netsec as an offensive-security-oriented walkthrough of hardware roots of trust, Qualcomm and Android boot stages, UEFI, and attestation, while a separate oss-security thread on a proposed fallback.efi/SBAT/GRUB memdisk bypass showed how disputed Secure Boot bypass claims can hinge on trust-model assumptions. In that discussion, maintainers from Red Hat and Oracle argued the reported chain required privileges that already undermine the platform's security guarantees, underscoring the article's broader point that boot integrity depends on enforcement, authority, coverage, and continuity across the full chain.

Who uses this technique?Get the actors, campaigns, and ATT&CK mapping behind it.
Get the tradecraft
Event timeline

How this story unfolded

Events from the most recent confirmed update back to the earliest known activity.

22 events · 2016 – Aug 19, 2026
  1. Reported Aug 19, 20263mo ago

    AVB test-key attacks demonstrated on three production devices

    The article says AVBTestKeyInTheWild demonstrated complete attacks on three production devices across Qualcomm, MediaTek, and Unisoc SoCs by resigning modified AVB graphs with public AOSP test private keys.

    Breaking secure boot without breaking the crypto
  2. Reported Aug 19, 20263mo ago

    Production firmware found using AOSP AVB test keys

    The AVBTestKeyInTheWild research found AOSP AVB test keys in first-party production firmware and identified 69 potentially vulnerable device models by scanning official firmware images.

    Breaking secure boot without breaking the crypto
  3. Reported Aug 19, 20263mo ago

    Qualcomm Nokia 6 EDL boot-chain bypass research published

    The article describes Nokia 6 research showing that forcing a Qualcomm MSM8937 phone into EDL and using signed Firehose programmers with memory primitives enabled patching boot stages after verification and booting a modified kernel and ramdisk.

    Breaking secure boot without breaking the crypto
  4. Aug 19, 20263mo ago

    Reddit r/netsec post amplifies 0x434b secure boot article

    A Reddit post by user 0x00rick linked to the 0x434b.dev article and described it as an offensive-security-oriented walkthrough of secure boot, UEFI, Android Verified Boot, measured boot, and attestation.

    How to break secure boot without touching any cryptography : r/netsec
  5. Aug 19, 20263mo ago

    0x434b publishes secure boot failure-mode analysis

    0x434b published a technical analysis arguing that secure boot failures fall into enforcement, coverage, authority, and continuity classes, using public case studies rather than presenting a new zero-day.

    Breaking secure boot without breaking the crypto
  6. Reported Aug 18, 20263mo ago

    Solar Designer reposts disputed Secure Boot chain summary

    A belated oss-security summary reposted the previously embargoed discussion about the claimed shim fallback.efi/SBAT/memdisk bypass chain and noted prior discussion had suggested there was no security relevance.

    oss-sec: AI slop "Combined chain advisory - fallback.efi/SBAT/memdisk bypass"
  7. Reported Aug 18, 20263mo ago

    Maintainers dispute security relevance of claimed Secure Boot chain

    The oss-security thread records Red Hat and Oracle responders challenging Jeremy Erazo's proposed fallback.efi/SBAT/GRUB bypass chain, arguing it depended on privileges or trust conditions that already defeated the model and might not merit a CVE.

    oss-sec: AI slop "Combined chain advisory - fallback.efi/SBAT/memdisk bypass"
  8. Jul 1, 20265mo ago

    Public disclosure date set for claimed shim/GRUB bypass chain

    In the oss-security discussion, Solar Designer proposed July 1, 2026 for public disclosure because distros-list policy allowed a maximum 14-day embargo, and Jeremy Erazo accepted that date.

    oss-sec: AI slop "Combined chain advisory - fallback.efi/SBAT/memdisk bypass"
  9. 2024

    MCUboot unprotected TLV issue disclosed as CVE-2024-32883

    The article references CVE-2024-32883 affecting MCUboot, where security-relevant TLV types could remain unprotected and feed unauthenticated properties into attestation data.

    Breaking secure boot without breaking the crypto
  10. 2024

    Microsoft mitigates CVE-2024-7344 via UEFI dbx revocations

    According to the article, Microsoft mitigated CVE-2024-7344 by revoking old signed binaries through the UEFI dbx while the vendor fixed the loader; the analysis was attributed to ESET.

    Breaking secure boot without breaking the crypto
  11. 2024

    Microsoft-signed reloader.efi bypass disclosed as CVE-2024-7344

    The article cites CVE-2024-7344 involving a Microsoft-signed UEFI binary, reloader.efi, that manually loaded and executed cloak.dat without calling LoadImage(), bypassing the platform secure boot check for the child image.

    Breaking secure boot without breaking the crypto
  12. 2023

    U-Boot SPL FIT/FDT parsing flaw disclosed as CVE-2023-39902

    The article references CVE-2023-39902 on several NXP i.MX 8M families, where an unauthenticated FIT or FDT description was parsed before the FIT payload was authenticated, enabling writes over SPL memory.

    Breaking secure boot without breaking the crypto
  13. 2023

    Sonos Era 100 continuity flaw disclosed as CVE-2023-50810

    The article cites CVE-2023-50810 affecting the Sonos Era 100, where sonosboot verified a genuine signed kernel while unsigned metadata and boot arguments caused Linux to consume an attacker-controlled initramfs.

    Breaking secure boot without breaking the crypto
  14. 2023

    Chromecast boot-chain prerequisites and persistence issues identified

    The article states CVE-2023-48424 enabled the Chromecast chain by stalling eMMC boot long enough to interrupt U-Boot over UART, and CVE-2023-6181 later provided persistence by abusing insufficiently restricted Bootloader Control Block data from the misc partition during preboot.

    Breaking secure boot without breaking the crypto
  15. 2023

    Chromecast AVB result overwrite flaw disclosed as CVE-2023-48425

    The article says CVE-2023-48425 affected Google Chromecast devices using an Amlogic SoC because U-Boot overwrote an AVB verification result with success when the upgrade_step environment variable was set to 3.

    Breaking secure boot without breaking the crypto
  16. 2023

    MediaTek preloader parser mismatch disclosed as CVE-2023-20696

    The article references CVE-2023-20696 affecting MediaTek preloader, where the signature verifier and later parser interpreted the same certificate container differently, enabling forged firmware hashes to pass as authentic.

    Breaking secure boot without breaking the crypto
  17. 2022

    OP-TEE Raspberry Pi 3 fault-injection flaw documented

    The article cites OP-TEE-2022-0001 on Raspberry Pi 3, where an EM fault could clear a non-zero signature error to TEE_SUCCESS and cause acceptance of an invalid signature.

    Breaking secure boot without breaking the crypto
  18. 2019

    EDK II secure boot state check flaw disclosed as CVE-2019-14560

    The article references CVE-2019-14560 in EDK II, where the result of GetEfiGlobalVariable2() was not checked when determining whether secure boot was enabled.

    Breaking secure boot without breaking the crypto
  19. 2019

    Qualcomm boot keystore flaw disclosed as CVE-2019-2278

    The article says CVE-2019-2278 affected several Qualcomm Snapdragon families because a user-keystore signature verification failure during boot did not stop the rejected keystore from being used as an authority.

    Breaking secure boot without breaking the crypto
  20. 2018

    U-Boot FIT hashed-strings trust issue disclosed as CVE-2018-1000205

    The article cites CVE-2018-1000205 in U-Boot FIT, where a hashed-strings offset supplied by the FIT itself could influence what the verifier covered.

    Breaking secure boot without breaking the crypto
  21. 2018

    Neato Botvac hidden boot menu bypass documented as CVE-2018-20785

    The article references CVE-2018-20785 affecting the Neato Botvac Connected and related Vorwerk robot vacuums, where a hidden boot menu could XMODEM-upload and execute an unsigned QNX IFS.

    Breaking secure boot without breaking the crypto
  22. 2016

    Nexus 6 initrd injection flaw disclosed as CVE-2016-10277

    The article cites CVE-2016-10277 on the Nexus 6, where Motorola boot configuration allowed initrd injection so a signed kernel consumed an unauthorized initramfs.

    Breaking secure boot without breaking the crypto
Linked entities

Related entities

Vulnerabilities, threat actors, malware, products, organizations, and breaches Mallory has linked to this story.

Open in app →
Do you run this?Get the adversaries, campaigns, and ATT&CK mapping behind this technique, with detections ready to deploy.
See Who Uses This Technique
Mallory platform

See the full picture, correlated to your attack surface.

This page covers what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which threat actors are using it right now, and what to deploy next.

Exposure mappingMap indicators from this story to your assets and identify affected systems in minutes.
Threat actor evidenceEvery observed campaign, victim, and pivot linked to actors named in this story.
Associated malwareMalware, exploits, and IOCs connected to the activity described here.
Detection signaturesYARA, Sigma, and Snort rules deployed to your SIEM as soon as they’re published.
Scheduled alertsGet matching new stories delivered to your team as they break, not the next morning.
AI threadsAsk questions about this story and take action on the answers.