cve-rs allows you to introduce common memory vulnerabilities (such as buffer overflows and segfaults) into your Rust program in a memory safe manner.
- 🩸 Bleeding edge technology
- 🕹️ Paradigm-changing (no more unsafe code!)
- 🔥 Blazingly fast
- 💡 Easy to use
- 🏆 Featuring way 👋 too 2️⃣ many 🤯 emojis in the 📖 readme 🔥 🦀 💨
- 🦀 Built in 100% memory-safe Rust
Rust is an amazing language. You can program a lot of useful things while ensuring that your program will stay safe. Unfortunately, safe Rust is quite limiting. For example, you cannot introduce code that could corrupt the program's memory. Now, with cve-rs, you can corrupt your program's memory without corrupting your program's memory.
We are very committed to making sure cve-rs is memory-safe. We know that unsafe code can have unintended consequences, such as memory unsafety that causes bugs like segmentation faults, use-after-frees, and buffer overflows.
That is why cve-rs uses #![deny(unsafe_code)] in the entire codebase. There is not a single block of unsafe code (except for some tests) in this project.
cve-rs implements the following bugs in safe Rust:
- Use after free
- Buffer overflow
- Segmentation fault
cve-rs also contains safe reimplementations of:
std::mem::transmutestd::ptr::null()/null_mut()but for references
cve-rs can be used directly with Cargo.
To use it as a library:
cargo add cve-rsOr to run our example binary:
cargo install cve-rs
cve-rscve-rs supports WASM through the WASI API, and also to Webassembly that you can run in a browser.
You can compile it and run it using Wasmer with the following commands:
cargo build --target wasm32-wasi
wasmer run target/wasm32-wasi/debug/cve-rs.wasmSpecial thanks to @Bright-Shard and @Creative0708, and everyone else who contributed to cve-rs.
This project is licensed under the GLWTSPL.
This project is licensed under the GLWTSPL.
This project is licensed under the GLWTSPL.
...and godspeed.