CVE-2024-13942: Rockchip RK3588s Secure BootROM TOCTOU (time-of-check to time-of-use) vulnerability leading to arbitrary code execution with highest privileges
Secure BootROM of RK3588s SoC is vulnerable to a time-of-check to time-of-use attack in case of booting from external media (SPI NOR or NAND, EMMC or SD).
The code reads the header of the next-stage loader twice. The header contains hashes of the executable modules and is signed with a private key, the public part of which is verified against the SHA256 digest blown in the OTP.
The first read is only partial and contains only the hashes of the executable modules. The second is complete, including the header signature.
Although the header is verified based on the fully read data, the authenticity of the executable modules is checked against the partial data from the first read.
An attacker with physical access to a device containing RK3588s SoC can easily modify the next-stage loader data on-the-fly using a low-cost SD-card or SPI NOR/NAND or EMMC emulator. Even a simple ultra low-cost circuit comprising two memory chips (containing the same data but different headers - the original and the modified one) and a multiplexer can be used to carry out an attack.
This can lead to arbitrary code execution with the highest privileges available (EL3). This issue affects RK3588s: RK3588s SoC BootROM (secure) 350B20210512V100 and possibly others.
As remediation apply mitigations per vendor instructions or discontinue use of the product if mitigations are unavailable https://www.rock-chips.com/a/en/products/RK35_Series/2022/0926/1660.html
Security readout for executives and security teams
Plain-English summary
A flaw in the RK3588s secure boot process can let someone with physical device access substitute untrusted startup code during boot. A successful attack could provide the highest processor privilege, undermining confidentiality, integrity, and availability despite signature verification.
Executive priority
Prioritize systems in exposed, unattended, hostile, or supply-chain-sensitive locations. The physical-access requirement reduces broad remote risk, but successful exploitation defeats secure boot and grants maximum privilege. Seek immediate vendor guidance; isolate or replace devices where physical control or mitigation cannot be assured.
Technical view
The BootROM reads the next-stage loader header twice. Module hashes come from an initial partial read, while signature verification uses the later complete read. An attacker able to change external-media data between those reads can make verified header data and module-authentication data differ, enabling EL3 arbitrary code execution.
Likely exposure
Exposure is limited to devices using Rockchip RK3588s, particularly secure BootROM version 350B20210512V100, that boot from SPI NOR, NAND, eMMC, or SD. Other versions may be affected, but the supplied sources do not confirm them. Physical access is required.
Exploitation context
The described attack requires physical access and hardware capable of changing loader data during boot. The CVE is not listed as KEV in the supplied bundle, and no cited source establishes active exploitation. Low-cost hardware may make targeted physical attacks practical.
Researcher notes
The record identifies CWE-367 and CVSS 3.1 score 7.6. Scope beyond BootROM 350B20210512V100 remains uncertain because the description says “possibly others.” No specific patch, fixed BootROM version, detection method, or confirmed exploitation campaign is supplied.
Mitigation direction
Obtain and apply Rockchip's vendor-prescribed mitigations for the affected BootROM and device configuration.
Restrict physical access to deployed RK3588s devices and their external boot media.
Prevent unauthorized replacement or manipulation of SPI, NAND, eMMC, and SD media.
Discontinue affected products where vendor mitigations are unavailable, as the CVE record advises.
Validation and detection
Inventory products containing RK3588s SoCs and record their secure BootROM versions.
Identify systems booting from SPI NOR, NAND, eMMC, or SD media.
Confirm whether version 350B20210512V100 is present; treat other versions as unresolved pending vendor confirmation.
Verify physical controls and tamper protections around devices and boot media.
Document vendor mitigation status and confirm implementation through authorized defensive testing.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · low confidence lookup
CWE-367: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
1CVSS vectors
3Timeline events
1ADP providers
4Source links
SSVC decision data
CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: total
CVSS vector scores
1 official score
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-367 · source CWE mapping
Time-of-check Time-of-use (TOCTOU) Race Condition
Time-of-check Time-of-use (TOCTOU) Race Condition represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.