CWE-1319
Improper Protection against Electromagnetic Fault Injection (EM-FI)
The device is susceptible to electromagnetic fault injection attacks, causing device internal information to be compromised or security mechanisms to be bypassed.
CVE-2025-9709 (GCVE-0-2025-9709)
Vulnerability from cvelistv5
Vendor | Product | Version | ||
---|---|---|---|---|
Nordic Semiconductor | nRF52810 |
Version: 0 |
{ "containers": { "adp": [ { "metrics": [ { "other": { "content": { "id": "CVE-2025-9709", "options": [ { "Exploitation": "poc" }, { "Automatable": "no" }, { "Technical Impact": "total" } ], "role": "CISA Coordinator", "timestamp": "2025-09-05T18:07:39.209816Z", "version": "2.0.3" }, "type": "ssvc" } } ], "providerMetadata": { "dateUpdated": "2025-09-05T18:07:49.930Z", "orgId": "134c704f-9b21-4f2e-91b3-4a467353bcc0", "shortName": "CISA-ADP" }, "title": "CISA ADP Vulnrichment" } ], "cna": { "affected": [ { "collectionURL": "https://www.nordicsemi.com/Products/nRF52810", "defaultStatus": "unaffected", "product": "nRF52810", "vendor": "Nordic Semiconductor", "versions": [ { "status": "affected", "version": "0" } ] } ], "credits": [ { "lang": "en", "type": "finder", "value": "Milena Mangiola" } ], "descriptions": [ { "lang": "en", "supportingMedia": [ { "base64": false, "type": "text/html", "value": "On-Chip Debug and Test Interface With Improper Access Control and Improper Protection against Electromagnetic Fault Injection (EM-FI) in Nordic Semiconductor nRF52810 allow attacker to perform EM Fault Injection and bypass APPROTECT at runtime, requiring the least amount of modification to the hardware system possible." } ], "value": "On-Chip Debug and Test Interface With Improper Access Control and Improper Protection against Electromagnetic Fault Injection (EM-FI) in Nordic Semiconductor nRF52810 allow attacker to perform EM Fault Injection and bypass APPROTECT at runtime, requiring the least amount of modification to the hardware system possible." } ], "impacts": [ { "capecId": "CAPEC-624", "descriptions": [ { "lang": "en", "value": "CAPEC-624: Hardware Fault Injection" } ] } ], "metrics": [ { "cvssV4_0": { "Automatable": "NOT_DEFINED", "Recovery": "NOT_DEFINED", "Safety": "PRESENT", "attackComplexity": "LOW", "attackRequirements": "NONE", "attackVector": "PHYSICAL", "baseScore": 8.6, "baseSeverity": "HIGH", "privilegesRequired": "NONE", "providerUrgency": "NOT_DEFINED", "subAvailabilityImpact": "HIGH", "subConfidentialityImpact": "HIGH", "subIntegrityImpact": "HIGH", "userInteraction": "NONE", "valueDensity": "NOT_DEFINED", "vectorString": "CVSS:4.0/AV:P/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H/S:P", "version": "4.0", "vulnAvailabilityImpact": "HIGH", "vulnConfidentialityImpact": "HIGH", "vulnIntegrityImpact": "HIGH", "vulnerabilityResponseEffort": "NOT_DEFINED" }, "format": "CVSS", "scenarios": [ { "lang": "en", "value": "GENERAL" } ] } ], "problemTypes": [ { "descriptions": [ { "cweId": "CWE-1191", "description": "CWE-1191: On-Chip Debug and Test Interface With Improper Access Control", "lang": "en", "type": "CWE" } ] }, { "descriptions": [ { "cweId": "CWE-1319", "description": "CWE-1319: Improper Protection against Electromagnetic Fault Injection (EM-FI)", "lang": "en", "type": "CWE" } ] }, { "descriptions": [ { "description": "Runtime Hardware Protection Bypass", "lang": "en" } ] } ], "providerMetadata": { "dateUpdated": "2025-09-05T17:16:16.345Z", "orgId": "1c6b5737-9389-4011-8117-89fa251edfb2", "shortName": "Toreon" }, "references": [ { "url": "https://raelize.com/upload/research/2022/No_Hat_2022_-_Glitching_devices_for_code_execution_v1.1.pdf" }, { "url": "https://raelize.com/upload/research/2025/Dartmouth_202505_False-Injections-Tales-of-Physics-Misconceptions-and-Weird-Machines_v1.1.pdf" }, { "url": "https://nvd.nist.gov/vuln/detail/CVE-2020-27211" }, { "url": "https://www.toreon.com/cve-2025-9709-major-vulnerability-in-common-chip/" } ], "source": { "discovery": "UNKNOWN" }, "title": "NRF52810 Runtime EM Fault Injection APPROTECT Bypass", "x_generator": { "engine": "Vulnogram 0.2.0" } } }, "cveMetadata": { "assignerOrgId": "1c6b5737-9389-4011-8117-89fa251edfb2", "assignerShortName": "Toreon", "cveId": "CVE-2025-9709", "datePublished": "2025-09-05T17:16:16.345Z", "dateReserved": "2025-08-29T16:27:34.512Z", "dateUpdated": "2025-09-05T18:07:49.930Z", "state": "PUBLISHED" }, "dataType": "CVE_RECORD", "dataVersion": "5.1" }
Mitigation
Phases: Architecture and Design, Implementation
Description:
- 1. Redundancy - By replicating critical operations and comparing the two outputs can help indicate whether a fault has been injected.
- 2. Error detection and correction codes - Gay, Mael, et al. proposed a new scheme that not only detects faults injected by a malicious adversary but also automatically corrects single nibble/byte errors introduced by low-multiplicity faults.
- 3. Fail by default coding - When checking conditions (switch or if) check all possible cases and fail by default because the default case in a switch (or the else part of a cascaded if-else-if construct) is used for dealing with the last possible (and valid) value without checking. This is prone to fault injection because this alternative is easily selected as a result of potential data manipulation [REF-1141].
- 4. Random Behavior - adding random delays before critical operations, so that timing is not predictable.
- 5. Program Flow Integrity Protection - The program flow can be secured by integrating run-time checking aiming at detecting control flow inconsistencies. One such example is tagging the source code to indicate the points not to be bypassed [REF-1147].
- 6. Sensors - Usage of sensors can detect variations in voltage and current.
- 7. Shields - physical barriers to protect the chips from malicious manipulation.
CAPEC-624: Hardware Fault Injection
The adversary uses disruptive signals or events, or alters the physical environment a device operates in, to cause faulty behavior in electronic devices. This can include electromagnetic pulses, laser pulses, clock glitches, ambient temperature extremes, and more. When performed in a controlled manner on devices performing cryptographic operations, this faulty behavior can be exploited to derive secret key information.
CAPEC-625: Mobile Device Fault Injection
Fault injection attacks against mobile devices use disruptive signals or events (e.g. electromagnetic pulses, laser pulses, clock glitches, etc.) to cause faulty behavior. When performed in a controlled manner on devices performing cryptographic operations, this faulty behavior can be exploited to derive secret key information. Although this attack usually requires physical control of the mobile device, it is non-destructive, and the device can be used after the attack without any indication that secret keys were compromised.