Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

CH2: Added memory safety entry to adversarial model (logical attacks). #20

Merged
merged 1 commit into from
Jan 16, 2024
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
19 changes: 16 additions & 3 deletions specification/src/chapter2.adoc
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

for temporal memory safety, is use-after-free a clearer example ?

Original file line number Diff line number Diff line change
Expand Up @@ -344,10 +344,10 @@ models and requirements.
| Unrestricted access
| Direct +
Logical
| Direct access to unauthroized resources in normal operation.
| Unauthorized direct access to resources between isolated components.
a| * RISC-V privilege levels
* RISC-V isolation (for example: PMP/sPMP, MTT, supervisor domains)
* RISC-V hardware virtualization (H extension, MMU)
* RISC-V isolation (for example: PMP/ePMP, sPMP, MTT, supervisor domains)
* RISC-V hardware enforced virtualization (H extension, MMU)
|

| SR_LGC_002
Expand Down Expand Up @@ -400,6 +400,19 @@ a| * Shadow stacks (Zicfiss)
* Landing pads (Zicfilp)
|

| SR_LGC_006
| Memory safety
| Logical
| Unauthorized access to resources within an isolated component. For example, pointer or allocation errors (temporal memory safety), or buffer overflows (spacial memory safety).
| RISC-V pointer masking (J-extension) +
Shadow stacks (Zicfiss) +
Landing pads (Zicfilp) +
+
Memory safe programming, for example: +
https:/www.cisa.gov/sites/default/files/2023-12/CSAC_TAC_Recommendations-Memory-Safety_Final_20231205_508.pdf +
| Architectural sandboxing, such as HFI. +
Capability based architecture, such as CHERI.

|===

==== Physical and remote
Expand Down