Memory safety CVEs differ between Rust and C/C++
Summary
The post argues that memory-safety CVEs are treated differently in Rust versus C/C++. Using curl as an example, it shows how a safe Rust API should not cause memory bugs, whereas in C/C++ such issues are often attributed to misuse rather than the library itself. The author explains that Rust’s safety guarantees mean a potential memory safety issue implicates the library (a soundness hole) if it can occur without unsafe, and explains why CVEs per line of code can be misleading when comparing languages.