---
title: "CWE-1319: Improper Protection against Electromagnetic Fault Injection (EM-FI)"
url: https://radicalnotion.ai/cwe/cwe-1319
type: cwe
description: "The device is susceptible to electromagnetic fault injection attacks, causing device internal information to be compromised or security mechanisms to be bypassed."
updated: 2026-11-10
source: RadicalNotion.AI
license: CC BY-NC 4.0 (https://creativecommons.org/licenses/by-nc/4.0/)
---

# CWE-1319: Improper Protection against Electromagnetic Fault Injection (EM-FI)

- **Abstraction:** Base
- **Structure:** Simple
- **Status:** Incomplete
- **CVEs with this as primary weakness:** 5
- **Of those, in CISA KEV:** 0
- **New in 2026:** 0
- **CWE catalog version:** 4.21

## Description

The device is susceptible to electromagnetic fault injection attacks, causing device internal information to be compromised or security mechanisms to be bypassed.

## Modes of introduction

| Phase | Note |
| --- | --- |
| Architecture and Design | - |
| Implementation | - |

## Applicable platforms

**Technologies:** System on Chip (Undetermined), Microcontroller Hardware (Undetermined), Memory Hardware (Undetermined), Power Management Hardware (Undetermined), Processor Hardware (Undetermined), Test/Debug Hardware (Undetermined), Sensor Hardware (Undetermined)

## Common consequences

| Scope | Impact | Note |
| --- | --- | --- |
| Confidentiality, Integrity, Access Control, Availability | Modify Memory, Read Memory, Gain Privileges or Assume Identity, Bypass Protection Mechanism, Execute Unauthorized Code or Commands | - |

## Potential mitigations

### Architecture and Design, Implementation

- 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.

## Demonstrative examples

### Example 1

In many devices, security related information is stored in fuses. These fuses are loaded into shadow registers at boot time. Disturbing this transfer phase with EM-FI can lead to the shadow registers storing erroneous values potentially resulting in reduced security.

Colin O'Flynn has demonstrated an attack scenario \[REF-1144\] that uses electro-magnetic glitching during booting to bypass security and gain read access to flash, read and erase access to shadow memory area (where the private password is stored). Most devices in the MPC55xx and MPC56xx series that include the Boot Assist Module (BAM) (a serial or CAN bootloader mode) are susceptible to this attack. In this paper, a GM ECU was used as a real life target. While the success rate appears low (less than 2 percent), in practice a success can be found within 1-5 minutes once the EMFI tool is setup. In a practical scenario, the author showed that success can be achieved within 30-60 minutes from a cold start.

## Observed examples

| CVE | Description |
| --- | --- |
| CVE-2020-27211 | Chain: microcontroller system-on-chip uses a register value stored in flash to set product protection state on the memory bus, but it does not contain protection against fault injection (CWE-1319), which leads to an incorrect initialization of the memory bus (CWE-1419), leading the product to be in an unprotected state. |

## Real CVEs with this weakness

| CVE | Title | Severity | CVSS | EPSS | CISA KEV | Published |
| --- | --- | --- | --- | --- | --- | --- |
| CVE-2022-26131 | ICSA-22-063-01 Improper Protection against Electromagnetic Fault Injection in Trailer Power Line Communications (PLC) J2497 | critical | 9.8 | - | No | 2022-03-07 |
| CVE-2022-42784 | Affected devices are vulnerable to an electromagnetic fault injection. This could allow an attacker to dump and debug the firmware, including the manipulation of memory. Further actions could allow to inject public keys of custom created key pairs which are then signed by the product CA. The generation of a custom certificate allows communication with, and impersonation of, any device of the same version. | high | 7.6 | - | No | 2023-12-12 |
| CVE-2025-1566 | - | high | 7.5 | - | No | 2025-04-16 |
| CVE-2023-42465 | sudo: Targeted Corruption of Register and Stack Variables | high | 7.0 | - | No | 2023-12-22 |
| CVE-2023-5138 | Glitch detection not active by default in Silicon Labs Secure Vault High devices | medium | 6.8 | - | No | 2024-01-03 |

## Related attack patterns (CAPEC)

- [CAPEC-624](https://radicalnotion.ai/capec/capec-624): Hardware Fault Injection
- [CAPEC-625](https://radicalnotion.ai/capec/capec-625): Mobile Device Fault Injection

## Related weaknesses

| Relationship | CWE | Name |
| --- | --- | --- |
| Parent | [CWE-693](https://radicalnotion.ai/cwe/cwe-693) | Protection Mechanism Failure |

## Frequently asked questions

### What is CWE-1319?

The device is susceptible to electromagnetic fault injection attacks, causing device internal information to be compromised or security mechanisms to be bypassed.

### What CVEs are caused by CWE-1319?

5 recorded CVEs are attributed to CWE-1319, including CVE-2022-26131, CVE-2022-42784 and CVE-2025-1566.

### What are the consequences of CWE-1319?

Exploiting CWE-1319 can lead to: Modify Memory, Read Memory, Gain Privileges or Assume Identity, Bypass Protection Mechanism, Execute Unauthorized Code or Commands.

### Is CWE-1319 actively exploited?

5 recorded CVEs are caused by CWE-1319; none are currently in CISA's KEV catalog of actively exploited flaws.

Primary source: [MITRE CWE](https://cwe.mitre.org/data/definitions/1319.html)

---

Source: [RadicalNotion.AI](https://radicalnotion.ai/cwe/cwe-1319). Licensed CC BY-NC 4.0; attribute RadicalNotion.AI and link the source page when you reuse this data.
