MirChecker: Detecting Bugs in Rust Programs via Static Analysis

Li, Zhuohua; Wang, Jincheng; Sun, Mingshen; Lui, John C. S.

doi:10.1145/3460120.3484541

Cited by 18 publications

(4 citation statements)

References 37 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…RQ2: How much overhead does SafeDrop introduce compared to the original compilation process? RQ3: Does SafeDrop perform better than other existing approaches, such as Rudra [7] and MirChecker [28]? RQ4: Is SafeDrop useful for helping developers in detecting unknown bugs from potentially many alarms?…”

Section: Methodsmentioning

confidence: 99%

“…Meanwhile, we measure the analysis time of SafeDrop and calculate the overhead compared with the original compiler to answer RQ2. To answer RQ3, we also apply, Rudra [7], MirChecker [28] and Miri [31] to these eight creates. Finally, we choose 50 more real-world Rust crates from GitHub for the usability study of RQ4.…”

Section: Methodsmentioning

confidence: 99%

“…Comparison with Other Tools. Now, we compare SafeDrop with existing tools that can also detect memory deallocation bugs for Rust programs, including Rudra [7], MirChecker [28], and Miri [31]. The result is shown in Table 1.…”

Section: 33mentioning

confidence: 99%

“…As Rust surges into popularity, it also attracts much attention from the research ield, especially those on formal veriication (e.g., [6,12,18,41]), usage of unsafe code [5], as well as how to deal with unsafe code [13,23,29]. Among all tools, Rudra [7] and MirChecker [28] are two static analysis tools that can also detect memory-safety bugs. We have already compared SafeDrop with them in Section 5.3.3.…”

Section: Existing Work On Rustmentioning

confidence: 99%

See 3 more Smart Citations

SafeDrop: Detecting Memory Deallocation Bugs of Rust Programs via Static Data-flow Analysis

Cui

Chen

et al. 2023

ACM Trans. Softw. Eng. Methodol.

View full text Add to dashboard Cite

Rust is an emerging programming language that aims to prevent memory-safety bugs. However, the current design of Rust also brings side effects, which may increase the risk of memory-safety issues. In particular, it employs OBRM (ownership-based resource management) and enforces automatic deallocation of unused resources without using the garbage collector. It may therefore falsely deallocate reclaimed memory and lead to use-after-free or double-free issues. In this paper, we study the problem of invalid memory deallocation and propose SafeDrop , a static path-sensitive data-flow analysis approach to detect such bugs. Our approach analyzes each function of a Rust crate iteratively in a flow-sensitive and field-sensitive way. It leverages a modified Tarjan algorithm to achieve scalable path-sensitive analysis and a cache-based strategy for efficient inter-procedural analysis. We have implemented our approach and integrated it into the Rust compiler. Experiment results show that the approach can successfully detect all such bugs in our experiments with a limited number of false positives and incurs a very small overhead compared to the original compilation time.

show abstract

Section: Methodsmentioning

confidence: 99%

Section: Methodsmentioning

confidence: 99%

Section: 33mentioning

confidence: 99%