CVE-2024-13942

HIGHPre-NVD 7.67.6
EchelonGraph scoreHIGH confidence

Score 7.6 from GitHub Security Advisory (severity: HIGH) published 2026-08-19. a secondary CVSS source baseline 7.6; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 4 sources updated this week
7.6EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.6Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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

CVSS v3
7.6
EG Score
7.6(high)
EG Risk
34(Track)
EG Risk 34/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity76% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
6%
KEV
Not listed

Published

August 19, 2026

Last Modified

August 19, 2026

Advisory Details (2)

Auto-updated Aug 19, 2026
No patch confirmed yet.
generic

Rockchip-瑞芯微电子股份有限公司

https://www.rock-chips.com/a/en/psirt/vdp.html
generic

Rockchip-瑞芯微电子股份有限公司

https://www.rock-chips.com/a/en/products/RK35_Series/2022/0926/1660.html

Vendor Advisories for CVE-2024-13942(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 12× in last 7d / 12× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-08-21 08:46 UTCEG score recompute
  2. 2026-08-21 08:46 UTCGHSA enrichment
  3. 2026-08-20 22:53 UTCEPSS rescore
  4. 2026-08-20 20:38 UTCGHSA enrichment
  5. 2026-08-20 08:29 UTCGHSA enrichment
  6. 2026-08-19 20:22 UTCEG score recompute
  7. 2026-08-19 20:22 UTCGHSA enrichment
  8. 2026-08-19 19:18 UTCEG score recompute
  9. 2026-08-19 19:18 UTCGHSA enrichment
  10. 2026-08-19 17:23 UTCEG score recompute
  11. 2026-08-19 16:52 UTCEG score recompute
  12. 2026-08-19 16:52 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2024-13942?
CVE-2024-13942 is a high vulnerability published on August 19, 2026. 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,…
When was CVE-2024-13942 disclosed?
CVE-2024-13942 was first published in the National Vulnerability Database on August 19, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2024-13942 actively exploited?
CVE-2024-13942 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 94.0% of all scored CVEs.
What is the CVSS score of CVE-2024-13942?
CVE-2024-13942 has a CVSS v3 base score of 7.6 (NVD).
How do I remediate CVE-2024-13942?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2024-13942, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2024-13942

Explore →

Is Your Infrastructure Affected by CVE-2024-13942?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.