Skip to main content
VulnerabilityPublished Updated

CVE-2024-25077: Code Injection

Source CVE Database V5

0

Not known to be exploited · CVSS 9.8 Critical.

Data as of 26 Oct 2026, 12:54 UTC

CVSS 3.1 base score
9.8Critical
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.4% chance of exploitation in 30 days – higher than 35% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 10 Jul 2024

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

AI-suggested

Until official patches are released by Renesas, organizations should implement several mitigations: 1) Restrict network access to devices using these MCUs, especially from untrusted networks, to reduce remote exploitation risk. 2) Employ network-level monitoring and anomaly detection to identify unusual device behavior indicative of compromise. 3) Use hardware-based security features or external secure elements to enforce code integrity checks beyond the vulnerable secure boot mechanism. 4) Where possible, disable or limit firmware update capabilities to trusted sources only. 5) Engage with Renesas support channels to obtain early access to patches or firmware updates. 6) For new designs, consider alternative MCUs with robust secure boot implementations that include authenticated encryption modes. 7) Conduct thorough security audits of devices incorporating these MCUs to identify potential attack vectors and prepare incident response plans.

Description

An issue was discovered on Renesas SmartBond DA14691, DA14695, DA14697, and DA14699 devices. The Nonce used for on-the-fly decryption of flash images is stored in an unsigned header, allowing its value to be modified without invalidating the signature used for secureboot image verification. Because the encryption engine for on-the-fly decryption uses AES in CTR mode without authentication, an attacker-modified Nonce can result in execution of arbitrary code.

References

Community reviews

Loading reviews…