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

provenance tracking for memory regions #162

Open
bollu opened this issue Sep 18, 2024 · 0 comments
Open

provenance tracking for memory regions #162

bollu opened this issue Sep 18, 2024 · 0 comments

Comments

@bollu
Copy link
Collaborator

bollu commented Sep 18, 2024

As requested by @pennyannn , we want to be able to ensure that reads and writes in our memory model only occur from pre-defined memory regions.

This automatically ensures that the program does not read from or write to memory locations that are outside of the permissible ones.

For an example issue that was caused without such tracking, see The OpenSSL advisory on Input buffer over-read in AES-XTS implementation on 64 bit ARM

The AES-XTS cipher decryption implementation for 64 bit ARM platform will read
past the end of the ciphertext buffer if the ciphertext size is 4 mod 5 in 16
byte blocks, e.g. 144 bytes or 1024 bytes. If the memory after the ciphertext
buffer is unmapped, this will trigger a crash which results in a denial of
service.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant