MOLE: Breaking GPU TEE with GPU-Embedded MCU

Project Repo

Responses from the authors of affected GPU TEEs

Responses from the vendors about supply-chain risk

Project Repo

Project Repo:

https://anonymous.4open.science/r/Mole-Open-6D48/README.md

Responses from the authors of affected GPU TEEs

Wang Chenxu - Author of StrongBox / Cage [1,2]

Jinsoo Jang - Author of MyTEE [3]

References:

[1] https://dl.acm.org/doi/10.1145/3548606.3560627

[2] https://www.ndss-symposium.org/ndss-paper/cage-complementing-arm-cca-with-gpu-extensions/

[3] https://www.ndss-symposium.org/ndss-paper/mytee-own-the-trusted-execution-environment-on-embedded-devices/

Responses from the vendors about supply-chain risk

Arm responded that they had discussed this issue and decided to start providing checksums for any binary image made available outside of their secure partner delivery hub soon.

Rockchip acknowledged the possibility of firmware containing malicious code, but they believe it is the user's responsibility to distinguish between authoritative and malicious sources.

Moreover, although Rockchip claims that they do not use GitHub to distribute their firmware, there are 41 downstream references to their GitHub, where the GPU MCU firmware is hosted.

We're currently discussing with Rockchip about the risks of someone creating a deceptively similar name (e.g., JeffyCN v.s. JefffyCN, the former is Rockchip's official account hosting MCU firmware)

MediaTek responded that it should be Arm's responsibility to provide an authoritative way to verify the GPU MCU firmware.

Page updated

Google Sites

Report abuse