Memory-safety violations are the primary cause of security and reliability issues in software
systems written in unsafe languages. Given the limited adoption of decades-long research in …

Shielded execution based on Intel SGX provides strong security guarantees for legacy
applications running on untrusted platforms. However, memory safety attacks such as …

We present Solythesis, a source to source Solidity compiler which takes a smart contract
code and a user specified invariant as the input and produces an instrumented contract that …

As control flow hijacking attacks become more challenging due to the deployment of various
exploit mitigation technologies, the leakage of sensitive process data through the …

Good programming languages provide helpful abstractions for writing secure code, but the
security properties of the source language are generally not preserved when compiling a …

Memory sanitizers are powerful tools to detect spatial and temporal memory errors, such as
buffer overflows and use-after-frees. Fuzzers and software testers often rely on these tools to …

Applications written in C/C++ are prone to memory corruption, which allows attackers to
extract secrets or gain control of the system. With the rise of strong control-flow hijacking …

Today, a vast amount of sensitive data worth millions of dollars is processed in untrusted
data centers; hence, the confidentiality and integrity of the code and data are of paramount …

A memory safety violation occurs when a program has an out-of-bound (spatial safety) or
use-after-free (temporal safety) memory access. Given its importance as a security …

Failing to properly isolate components in the same address space has resulted in a
substantial amount of vulnerabilities. Enforcing the least privilege principle for memory …