Loading vulnerability…
CVE-2022-38691 is a critical vulnerability in the UNISOC BootROM secure boot verification logic affecting second-stage executable loading. According to the provided content, the BootROM performs improper validation when processing certificate type 0 during RSA-based secure boot verification. Specifically, when a certificate of type 0 is supplied, the BootROM fails to validate the public RSA key hash against the trusted key hash stored in eFuses. This breaks the intended chain-of-trust enforcement in BootROM and allows untrusted or attacker-controlled boot components to be accepted as valid. The issue is in BootROM, the immutable first-stage code in silicon, and was identified by NCC Group during analysis of UNISOC Android chipset secure boot implementations.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
1 valid exploit after Mallory filtered fakes, detection scripts, and README-only repos (1 hidden).
This repository provides a proof-of-concept exploit for CVE-2022-38691 and CVE-2022-38692, targeting several Unisoc/Spreadtrum SoCs (e.g., ud710, ums312, ums512, sc9820e, sc9832e, sc9863a). The main exploit is implemented in C (main.c) and is designed to patch unsigned bootloader images (FDL1/SPL) so they can be persistently booted on affected devices, bypassing signature verification. The exploit works by generating a forged certificate structure and manipulating image headers/footers, using SoC-specific configuration files found in the cfg/ directory. The process requires first removing signature checks from the boot chain images, then running the patcher tool with the appropriate configuration and unsigned image. The repository includes supporting cryptographic code (sha256.c, mincrypt/sha256.h, mincrypt/hash-internal.h) and detailed configuration files for each supported SoC. The exploit is not weaponized but provides a working proof-of-concept for local privilege escalation and secure boot bypass on affected platforms.
3 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.