Hacker GitHub

← All repos

Speykious/cve-rs

View on GitHub ↗ ★ 5,446 Rust

Blazingly 🔥 fast 🚀 memory vulnerabilities, written in 100% safe Rust. 🦀

25 mentions on Hacker News by 22 people: 3 stories, 22 comments · first 2024-02-20 · latest 2026-04-22

Mentions per year 25 mentions · busiest year 2025 (17)
20082026
AllStoriesComments NewestTopOldest
  1. …rust at last. With no unsafe allowed, even type safe. Unless you forget about their type bugs: https://github.com/Speykious/cve-rs . So maybe eliminate type and concurrency unsafeties also then in the next decades or so.
    comment by rurban · 2026-04-22 · in Garbage collection without unsafe code
  2. ▲ 2
    Fast memory vulnerabilities, written in 100% safe Rust
    story by airhangerf15 · 2025-12-18 · 1 comment
  3. …the boundary of the compiler, but it says absolute nothing to the effect of "Rust is unsafe". [1] https://github.com/Speykious/cve-rs
    comment by krukah · 2025-11-13 · in Rust in Android: move fast and fix things
  4. …of them made a claim along those lines? [0]: https://github.com/rust-lang/rust/issues/57893 [1]: https://github.com/Speykious/cve-rs
    comment by aw1621107 · 2025-10-15 · in Why Is SQLite Coded In C
  5. rustc and Rust have some rather serious type system holes and other kinds of issues. https://github.com/Speykious/cve-rs https://github.com/lcnr/solver-woes/issues
    comment by linuxissortof · 2025-10-06 · in A comparison of Ada and Rust, using solutions to the Advent of Code
  6. https://github.com/Speykious/cve-rs
    comment by gre · 2025-09-20 · in Git: Introduce Rust and announce it will become mandatory in the build system
  7. > Consider Rust. What about advertising actual memory safe languages instead. https://github.com/Speykious/cve-rs
    comment by rurban · 2025-09-16 · in What is memory safety and why does it matter?
  8. > https://github.com/Speykious/cve-rs Caution: Lifetime may not live long enough https://github.com/Speykious/cve-rs/issues/48
    comment by Ygg2 · 2025-09-07 · in C++26: Erroneous behaviour
  9. > Safe rust doesn't segfault ever . https://github.com/Speykious/cve-rs > 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…
    comment by jjmarr · 2025-09-07 · in C++26: Erroneous behaviour
  10. I like the license: https://github.com/Speykious/cve-rs/blob/main/LICENSE
    comment by fainpul · 2025-07-14 · in Fast memory vulnerabilities, written in 100% safe Rust
  11. ▲ 7
    Fast memory vulnerabilities, written in 100% safe Rust
    story by rc00 · 2025-07-14 · 3 comments
  12. …for some crazy propaganda, rust devs believes that any rust code is safe and sound no matter what. https://github.com/Speykious/cve-rs/issues/49
    comment by caim · 2025-07-07 · in My first verified imperative program
  13. And how would you conclude that "fast"? You can have UB in "safe rust". https://github.com/Speykious/cve-rs You can even disable the Type check, trait check and borrow check in "safe rust" And all of this is unsound.…
    comment by caim · 2025-06-27 · in Weird Expressions in Rust
  14. Safe Rust is demonstrably not memory-safe: https://github.com/Speykious/cve-rs/tree/main
    comment by ummonk · 2025-06-26 · in Why is the Rust compiler so slow?
  15. > Even validators have bugs Yep! For example, https://github.com/Speykious/cve-rs is an example of a bug in the Rust compiler, which allows something that it shouldn't. It's on its way to being fixed. > or miss things no? This is the…
    comment by steveklabnik · 2025-03-16 · in Zlib-rs is faster than C
  16. I love Rust, but you can play exactly the same game with Rust: https://github.com/Speykious/cve-rs
    comment by dimitropoulos · 2025-03-11 · in A 10x Faster TypeScript
  17. https://github.com/Speykious/cve-rs
    comment by deadliftdouche · 2025-02-07 · in It is time to standardize principles and practices for software memory safety
  18. …Rust as a whole is a dishonest line of thinking and I'm not going to engage with it further. [1]: https://github.com/Speykious/cve-rs
    comment by zamalek · 2025-02-05 · in Zig; what I think after months of using it
  19. You might be thinking of CVE-RS[0] which is exploiting bugs in the compiler. [0] https://github.com/Speykious/cve-rs
    comment by Measter · 2024-10-18 · in Smart pointers for the kernel
  20. https://github.com/Speykious/cve-rs They can be fixed, but as always, there’s a lot of work to do. The bug that the above package relies on has never been seen in the wild, only from handcrafted code to invoke it, and so is less of a…
    comment by steveklabnik · 2024-09-26 · in Rewriting Rust
  21. …[4]: https://github.com/rust-lang/rust/issues?q=is%3Aissue+is%3Ao... [5]: https://github.com/Speykious/cve-rs
    comment by raphlinus · 2024-05-15 · in Translation of Rust's core and alloc crates to Coq for formal verification
  22. When there is industry consensus, there is often much humour that precedes it, including https://github.com/Speykious/cve-rs
    comment by jasoneckert · 2024-03-05 · in Mark Russinovich: "There is industry consensus on moving away from C/C++"
  23. What a wonderful license! https://github.com/Speykious/cve-rs/blob/main/LICENSE
    comment by foolswisdom · 2024-02-20 · in Cve-rs: Fast memory vulnerabilities, written in safe Rust
  24. …function![0] Does it crash safely as well? I did not test it, I more than 640 KB of ram. - [0] https://github.com/Speykious/cve-rs/blob/d51f52dd64f148a086e...
    comment by hpb42 · 2024-02-20 · in Cve-rs: Fast memory vulnerabilities, written in safe Rust
  25. ▲ 317
    Cve-rs: Fast memory vulnerabilities, written in safe Rust
    story by npalli · 2024-02-20 · 154 comments