Memory-Safety Challenge Considered Solved? An In-Depth Study with All Rust CVEs · HackerPapers discussions

Memory-Safety Challenge Considered Solved? An In-Depth Study with All Rust CVEs — mentioned by timschmidt

Tue, 16 Jul 2024 23:13:12 GMT

Microsoft: 70% of all security bugs are memory safety issues: https://www.zdnet.com/article/microsoft-70-percent-of-all-se... Chrome: 70% of all security bugs are memory safety issues: https://www.zdnet.com/article/chrome-70-of-all-security-bugs... "Rust is an emerging programing language that aims at preventing memory-safety bugs without sacrificing much efficiency. The claimed property is very attractive to developers, and many projects start using the language. However, can Rust achieve the memory-safety promise? This paper studies the question by surveying 186 real-world bug reports…

Paper and discussion history. A mention is not an endorsement.

Memory-Safety Challenge Considered Solved? An In-Depth Study with All Rust CVEs — mentioned by timschmidt

Tue, 31 Jan 2023 01:14:12 GMT

https://arxiv.org/abs/2003.03296 "Rust is an emerging programing language that aims at preventing memory-safety bugs without sacrificing much efficiency. The claimed property is very attractive to developers, and many projects start using the language. However, can Rust achieve the memory-safety promise? This paper studies the question by surveying 186 real-world bug reports collected from several origins which contain all existing Rust CVEs (common vulnerability and exposures) of memory-safety issues by 2020-12-31. We manually analyze each bug and extract their culprit patterns. Our analysis…

Paper and discussion history. A mention is not an endorsement.

Memory-Safety Challenge Considered Solved? An In-Depth Study with All Rust CVEs — mentioned by Arch-TK

Fri, 19 Feb 2021 13:11:20 GMT

Here is a good summary of how Ada deals with safety in the context of memory management: https://news.ycombinator.com/item?id=14216128 It's not rust but at the same time I think rust has sacrificed general safety in favor of memory safety which has produced a tendency towards a false sense of security. After all, it seems rust still has memory safety issues despite the borrow checker: https://arxiv.org/pdf/2003.03296.pdf

Paper and discussion history. A mention is not an endorsement.

Memory-Safety Challenge Considered Solved? An In-Depth Study with All Rust CVEs — HN submission

Mon, 04 Jan 2021 21:20:51 GMT

Memory-Safety Challenge Considered Solved? An In-Depth Study with All Rust CVEs

3 points; 0 discussion replies on HN. Paper and source history. A submission is not an endorsement.

Memory-Safety Challenge Considered Solved? An In-Depth Study with All Rust CVEs — mentioned by rvz

Wed, 19 Aug 2020 23:36:05 GMT

Yet once the Chromium team goes down that Rust to C++ FFI route, they will encounter the same old bugs outlined in this paper. [0] They might as well fork Servo and create their own engine from that, but even that is still a prototype worked on for years with zero C++ at least. It's too early to see how the Chromium team will begin to work on this given it's only a plan, but maybe the unsafety and security issues are enough motivation to actually use Rust to C++ interop or a rewrite. But once again, this has been tried by some other projects and by just looking at the effort of a rewrite…

Paper and discussion history. A mention is not an endorsement.

Memory-Safety Challenge Considered Solved? An In-Depth Study with All Rust CVEs — mentioned by rvz

Sun, 12 Jul 2020 15:39:52 GMT

Don't let your feelings get in the way of your valid argument about C++. The Linux kernel will eventually going use the FFI route from Rust and C someday, but it is no safer in both safe Rust and unsafe Rust according to this memory saftey assessment study that has Rust CVEs [0] [0] https://arxiv.org/pdf/2003.03296.pdf

Paper and discussion history. A mention is not an endorsement.

Memory-Safety Challenge Considered Solved? An In-Depth Study with All Rust CVEs — HN submission

Tue, 07 Jul 2020 11:18:42 GMT

Memory-Safety Challenge Considered Solved? Experience Report with All Rust CVEs

1 point; 0 discussion replies on HN. Paper and source history. A submission is not an endorsement.

Memory-Safety Challenge Considered Solved? An In-Depth Study with All Rust CVEs — mentioned by rvz

Sat, 13 Jun 2020 17:00:59 GMT

That's if you use 'Safe Rust', then the safety guarantees hold true. However, the risks increase as soon as you start using unsafe{} or import a crate that also has unsafe{} code which is why I like using cargo-geiger on my projects to see the unsafe{} uses in my code and dependencies [0]. Use unsafe{} at your own risk. [1] [0] https://github.com/rust-secure-code/cargo-geiger [1] https://arxiv.org/abs/2003.03296

Paper and discussion history. A mention is not an endorsement.

Memory-Safety Challenge Considered Solved? An In-Depth Study with All Rust CVEs — HN submission

Fri, 12 Jun 2020 14:43:05 GMT

Memory-safety challenge considered solved? An empirical study of Rust CVEs

2 points; 0 discussion replies on HN. Paper and source history. A submission is not an endorsement.

Memory-Safety Challenge Considered Solved? An In-Depth Study with All Rust CVEs — HN submission

Wed, 03 Jun 2020 04:52:09 GMT

An In-Depth Experience Report with All Rust CVEs

2 points; 0 discussion replies on HN. Paper and source history. A submission is not an endorsement.