2020
DOI: 10.1109/lca.2020.2964212
|View full text |Cite
|
Sign up to set email alerts
|

Brutus: Refuting the Security Claims of the Cache Timing Randomization Countermeasure Proposed in CEASER

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
1
1
1

Citation Types

0
17
0

Year Published

2020
2020
2023
2023

Publication Types

Select...
4
3
1

Relationship

0
8

Authors

Journals

citations
Cited by 25 publications
(20 citation statements)
references
References 9 publications
0
17
0
Order By: Relevance
“…4) Shortcuts: With a case study on CEASER-S, we show with devastating consequences that the security of the randomization should not be taken for granted, even if its output is not directly observable. A similar study was conducted in concurrent work [5]. Instantiating a sound cryptographic algorithm thwarts all shortcuts but affects performance.…”
Section: A Prime+prune+probe On Specific Designsmentioning
confidence: 92%
See 1 more Smart Citation
“…4) Shortcuts: With a case study on CEASER-S, we show with devastating consequences that the security of the randomization should not be taken for granted, even if its output is not directly observable. A similar study was conducted in concurrent work [5]. Instantiating a sound cryptographic algorithm thwarts all shortcuts but affects performance.…”
Section: A Prime+prune+probe On Specific Designsmentioning
confidence: 92%
“…The LLC slicing function can be encapsulated in R (i.e., one randomized cache), or not (i.e., per-slice randomized caches). 5 The randomized cache is divided into P partitions, where 1 ≤ P ≤ n w . An input address a has, in general, a different index in each of these partitions.…”
Section: A Randomization-based Protected Cache Modelmentioning
confidence: 99%
“…Our analysis focuses on investigating the fundamental problems in the randomization schemes used by randomly mapped caches. Prior work [30] has shown that the mapping function used in CEASER [9] and Skewed-CEASER [10] only consists of linear functions and has a key invariant vulnerability, that is, changing the key used in the mapping function cannot change the collisions between addresses. This vulnerability can be fixed using non-linear hash functions.…”
Section: Threat Model and Scopementioning
confidence: 99%
“…This vulnerability can be fixed using non-linear hash functions. Note that, our analysis is independent of which hash function is used and studies new vulnerabilities that have not been explored in prior work [30]. Indeed, we focus on analyzing the fundamental problem that is intrinsic to randomly mapped caches.…”
Section: Threat Model and Scopementioning
confidence: 99%
“…While these defenses were shown effective against the eviction set construction algorithms and techniques at the time, subsequent more efficient eviction set construction algorithms [80] were able to undermine them. Consequently, enhancements to these defenses were proposed [80], only to be rendered ineffective again by yet another attack vector, e.g., weak low-latency cryptographic primitives [76], [10], or alternative attack techniques that exploited design/implementation flaws in the proposed defenses [88].…”
Section: Introductionmentioning
confidence: 99%