MSWasm: Soundly Enforcing Memory-Safe Execution of Unsafe Code
cseweb.ucsd.edu · 8,818 words · saved by 1 readers
N/A
MSWasm: Soundly Enforcing Memory-Safe Execution of Unsafe Code ALEXANDRA E. MICHAEL∗ , UCSD, USA and University of Washington, USA ANITHA GOLLAMUDI∗ , University of Massachusetts Lowell, USA JAY BOSAMIYA, CMU, USA EVAN JOHNSON, UCSD and Arm Ltd, USA AIDAN DENLINGER, UCSD, USA CRAIG DISSELKOEN, UCSD, USA CONRAD WATT, University of Cambridge, UK BRYAN PARNO, CMU, USA MARCO PATRIGNANI, University of Trento, Italy MARCO VASSENA, Utrecht University, Netherlands DEIAN STEFAN, UCSD, USA Most programs compiled to WebAssembly (Wasm) today are written in unsafe languages like C and C++. Unfortunately,…
saved by
related reading
- Multiprogramming a 64kB ComputerSafely and Efficientlytockos.org
- Tiered Trust for Useful Embedded Systems Securitytockos.org
- rsmsrsms.me
- Mitigating Memory-Safety Vulnerabilities | Computer Securitytextbook.cs161.org
- Formally Verifying WebAssembly - A Soroban Case Studycertora.com
- A shallow dive into formal verificationvitalik.eth.limo
- A Mere Mortal's Guide to Webassemblyuptointerpretation.com
- [2312.06942] AI Control: Improving Safety Despite Intentional Subversionarxiv.org
- Eliminating Memory Safety Vulnerabilities Once and For Alldarpa.mil
- Eliminating Memory Safety Vulnerabilities Once and For Alldarpa.mil
- Wasmi 2.0 - Engineering of the Fastest Wasm Interpreterswasmi-labs.github.io
- [KO] CosmWasm 101 와씀 1편: Counter 컨트랙트 톺아보기 | by Sigrid Jin | DSRV | Mediummedium.com