Главная
Study mode:
on
1
Intro
2
HSM: size and prize
3
HSM: key aspects
4
FIPS 140-2
5
HSM: inside
6
HSM: PCle Card
7
HSM under investigations
8
Research Objectives
9
HSM: Admin Tools - Binary Analysis
10
HSM: Admin Tools - cmd injection
11
HSM: TEE Threat Model
12
HSM: Java Archive
13
HSM: JAR Signature
14
JAR: The Files
15
JAR: Signature Verification (11)
16
Threat Model Invalidation (III)
17
Threat Model Invalidation by ZIP rewrite
18
Threat Model Invalidation by ZIP patching
19
Threat Model Invalidation (IV)
20
Failed Attempts
21
Disclosure Process
Description:
Explore a novel attack against the verification code of digital signature schemes in Gemalto's LunaSP Hardware Security Module. Delve into the methodology for executing arbitrary, unsigned code within the HSM's protected application layer. Examine key aspects of HSMs, FIPS 140-2 compliance, and internal components. Investigate research objectives, binary analysis of admin tools, and command injection techniques. Analyze the HSM's Trusted Execution Environment threat model, Java Archive structure, and JAR signature verification process. Learn about threat model invalidation through ZIP rewriting and patching. Discuss failed attempts and the disclosure process for this security vulnerability. Gain insights into potential implications for similar systems and the broader field of hardware security.

Hardware Security Module - Executing Unsigned Code in HSM TEE

Black Hat
Add to list
0:00 / 0:00