CRSep 12, 2019

Taking a Look into Execute-Only Memory

arXiv:1909.05771v119 citations
Originality Incremental advance
AI Analysis

This work exposes critical security flaws in execute-only memory implementations, posing a significant threat to firmware developers and manufacturers.

The paper tackles the problem of insufficient intellectual property protection in microcontroller firmware due to shared hardware resources, demonstrating an attack that automatically recovers protected firmware from devices of different manufacturers.

The development process of microcontroller firmware often involves multiple parties. In such a scenario, the Intellectual Property (IP) is not protected against adversarial developers which have unrestricted access to the firmware binary. For this reason, microcontroller manufacturers integrate eXecute-Only Memory (XOM) which shall prevent an unauthorized read-out of third-party firmware during development. The concept allows execution of code but disallows any read access to it. Our security analysis shows that this concept is insufficient for firmware protection due to the use of shared resources such as the CPU and SRAM. We present a method to infer instructions from observed state transitions in shared hardware. We demonstrate our method via an automatic recovery of protected firmware. We successfully performed experiments on devices from different manufacturers to confirm the practicability of our attack. Our research also reveals implementation flaws in some of the analyzed devices which enables an adversary to bypass the read-out restrictions. Altogether, the paper shows the insufficient security of the XOM concept as well as several implementations.

Foundations

The foundational work for this paper's niche, ranked by how specifically the neighbourhood builds on it — not by global fame.

Your Notes