“Seems persuasive to me.”
Memory-Safety Challenge Considered Solved? An In-Depth Study with All Rust CVEs
人工分析 186 个 Rust 内存安全漏洞,检验 Rust 的安全承诺
论文调查截至 2020 年 12 月 31 日所有与内存安全相关的 Rust CVE,共 186 份真实漏洞报告,逐一人工分析并提取成因模式。结果显示 Rust 的承诺基本成立:所有内存安全漏洞都需要 unsafe 代码,且不少只是轻微的健全性(soundness)问题。作者归纳出三类典型漏洞:自动内存回收、不健全的函数、不健全的泛型或 trait,并提出两个提升 Rust 开发安全性的方向,包括使用特定 API 的最佳实践和检测涉及 unsafe 代码的 bug 的方法。
HN 上的人引用它争论 Rust 的内存安全:有人用它强调 unsafe 的风险和 Rust 仍会出现内存安全问题(如与 C++ 的 FFI 边界),也有人认为它恰恰支持了 Rust 的安全主张。
HN 书评
推荐在前,同类按时间 · 每篇最多保留 20 条,统计用全部提及“Use unsafe{} at your own risk.”
“it is no safer in both safe Rust and unsafe Rust according to this memory saftey assessment study”
“Yet once the Chromium team goes down that Rust to C++ FFI route, they will encounter the same old bugs outlined in this paper.”
“After all, it seems rust still has memory safety issues despite the borrow checker: Memory-Safety Challenge Considered Solved? An In-Depth Study with All Rust CVEs”
“Rust is an emerging programing language that aims at preventing memory-safety bugs without sacrificing much efficiency.”
- An In-Depth Experience Report with All Rust CVEs ↗mwindow · 2020-06-03 · 2 分
- Memory-safety challenge considered solved? An empirical study of Rust CVEs ↗fanf2 · 2020-06-12 · 2 分
- Memory-Safety Challenge Considered Solved? Experience Report with All Rust CVEs ↗ingve · 2020-07-07 · 1 分
- Memory-Safety Challenge Considered Solved? An In-Depth Study with All Rust CVEs ↗projct · 2021-01-04 · 3 分