2014 ACM/IEEE 41st International Symposium on Computer Architecture (ISCA) 2014
DOI: 10.1109/isca.2014.6853201
|View full text |Cite
|
Sign up to set email alerts
|

The CHERI capability model: Revisiting RISC in an age of risk

Abstract: Motivated by contemporary security challenges, we reeval uate and refine capability-based addressing for the RISC era. We present CHERI, a hybrid capability model that extends the 64-bit MIPS ISA with byte-granularity memory protection. We demonstrate that CHERI enables language memory model enforcement and fault isolation in hardware rather than soft ware, and that the CHERI mechanisms are easily adopted by existing programs for efficient in-program memory safety.In contrast to past capability models, CHERI c… Show more

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
1
1
1

Citation Types

0
175
0

Year Published

2015
2015
2023
2023

Publication Types

Select...
5
2
1

Relationship

1
7

Authors

Journals

citations
Cited by 176 publications
(175 citation statements)
references
References 35 publications
0
175
0
Order By: Relevance
“…CHERI [24], [85], [86] is an alternative hardware-based security model. It uses capabilities, instead of rich per-word tags, to enforce memory safety [86]; nevertheless, like the PUMP, its core capability-based model can be extended to implement other security policies.…”
Section: Memory Safety Micro-policymentioning
confidence: 99%
“…CHERI [24], [85], [86] is an alternative hardware-based security model. It uses capabilities, instead of rich per-word tags, to enforce memory safety [86]; nevertheless, like the PUMP, its core capability-based model can be extended to implement other security policies.…”
Section: Memory Safety Micro-policymentioning
confidence: 99%
“…Version 2 of the CHERI ISA [35] was created based on initial experiences attempting to build a capability system that was a usable compiler target for C. For example, this change propagated tag bits into capability tag bits, rather than preventing memory without tag bits from being loaded into capability registers. This was motivated by the need for memcpy() (which is called explicitly by the user and implicitly by the compiler) to be able to copy data without being aware of whether it contained pointers.…”
Section: Refining the Cheri Modelmentioning
confidence: 99%
“…The Olden benchmarks were run with the parameters in the CHERI ISCA paper [35]. The Olden results are shown in Figure 1.…”
Section: Whole Program Testingmentioning
confidence: 99%
See 1 more Smart Citation
“…However, given that this compartment is likely to be several orders of magnitude smaller than the parser compartment, the probability that such an exploitable vulnerability can be found is limited. Such constructs are a well-known advantage of capability systems [21][22][23].…”
Section: Introductionmentioning
confidence: 99%