2017 IEEE/ACM International Conference on Computer-Aided Design (ICCAD) 2017
DOI: 10.1109/iccad.2017.8203771
|View full text |Cite
|
Sign up to set email alerts
|

A novel cache bank timing attack

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
1

Citation Types

0
2
0

Year Published

2018
2018
2021
2021

Publication Types

Select...
4
2
1

Relationship

1
6

Authors

Journals

citations
Cited by 12 publications
(2 citation statements)
references
References 9 publications
0
2
0
Order By: Relevance
“…Not only GPUs, modern high-performance CPUs (e.g., Intel's SandyBridge and ARM's Cortex-A) are also designed with multi-banked L1 and L2 caches. Yarom et al [40] and Jiang et al [12] investigate how sensitive information can be leaked when a cryptographic application runs on a CPU with multi-banked caches. A GPU generates a much more complex access pattern to Shared Memory banks, and our prior work [14] is the first one that identified the memory bank conflictbased timing channel and exploited it for a successful timing attack.…”
Section: Introductionmentioning
confidence: 99%
“…Not only GPUs, modern high-performance CPUs (e.g., Intel's SandyBridge and ARM's Cortex-A) are also designed with multi-banked L1 and L2 caches. Yarom et al [40] and Jiang et al [12] investigate how sensitive information can be leaked when a cryptographic application runs on a CPU with multi-banked caches. A GPU generates a much more complex access pattern to Shared Memory banks, and our prior work [14] is the first one that identified the memory bank conflictbased timing channel and exploited it for a successful timing attack.…”
Section: Introductionmentioning
confidence: 99%
“…In [28], Weiβ et al perform Bernstein's cache-timing attack on a virtualization environment, which runs on an ARM CPU platform. In a recent research that claims a novel attack [29], the stalling delay caused by cache bank conflicts is exploited to infer the secret key. In [30], Moghimi et al conduct a cache attack on a Software Guard eXtensions (SGX) 2 supported Intel platform with different AES implementations.…”
mentioning
confidence: 99%