Keyless Entry: Breaking and Entering eMMC RPMB with EMFI
Fuente:
arXiv
Saved in:
| Main Authors: | , |
|---|---|
| Format: | Preprint |
| Published: |
2025
|
| Subjects: | |
| Online Access: | |
| Tags: |
Add Tag
No Tags, Be the first to tag this record!
|
| _version_ | 1866914173297885184 |
|---|---|
| author | Fukami, Aya Buurke, Richard |
| author_facet | Fukami, Aya Buurke, Richard |
| contents | The Replay Protected Memory Block (RPMB) in modern storage systems provides a secure area where data integrity is ensured by authentication. This block is used in digital devices to store pivotal information that must be safeguarded against modification by potential attackers. This paper targets the authentication scheme of the RPMB in three different eMMCs from a major manufacturer. A glitch was injected by sending an electromagnetic pulse to the target chip. RPMB authentication was successfully glitched and the information stored in two target eMMCs was overwritten with arbitrary data, without affecting the integrity of other data. |
| format | Preprint |
| id |
arxiv_https___arxiv_org_abs_2511_22340 |
| institution | arXiv |
| publishDate | 2025 |
| record_format | arxiv |
| spellingShingle | Keyless Entry: Breaking and Entering eMMC RPMB with EMFI Fukami, Aya Buurke, Richard Cryptography and Security The Replay Protected Memory Block (RPMB) in modern storage systems provides a secure area where data integrity is ensured by authentication. This block is used in digital devices to store pivotal information that must be safeguarded against modification by potential attackers. This paper targets the authentication scheme of the RPMB in three different eMMCs from a major manufacturer. A glitch was injected by sending an electromagnetic pulse to the target chip. RPMB authentication was successfully glitched and the information stored in two target eMMCs was overwritten with arbitrary data, without affecting the integrity of other data. |
| title | Keyless Entry: Breaking and Entering eMMC RPMB with EMFI |
| topic | Cryptography and Security |
| url | https://arxiv.org/abs/2511.22340 |