Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Investigate if RMC can detect memory corruption errors found in the Rust standard library #411

Closed
1 of 2 tasks
chinmaydd opened this issue Aug 10, 2021 · 1 comment
Closed
1 of 2 tasks

Investigate if RMC can detect memory corruption errors found in the Rust standard library #411

chinmaydd opened this issue Aug 10, 2021 · 1 comment
Labels
[C] Internal Tracks some internal work. I.e.: Users should not be affected.

Comments

@chinmaydd
Copy link

chinmaydd commented Aug 10, 2021 •
edited by celinval
Loading

RMC aims to be a bit-precise model checker for Rust. It would be useful to check if it can detect bugs previously found by the community in the Rust Standard Library. A possible way to go about this would be to pick up a version of the library before and after then change and test the vulnerable example.

This issue aims to track this exercise. Some initial CVEs which might be interesting to look at are :

  • Buffer Overflow vulnerability in std::collections::vec_deque::VecDeque::reserve() CVE-2018-1000657
  • Use-after-free or double free in VecDeque CVE-2020-36318

Repository with Rust CVEs: Link
@chinmaydd chinmaydd self-assigned this Aug 10, 2021
@chinmaydd chinmaydd removed their assignment Sep 10, 2021
@celinval celinval added [C] Internal Tracks some internal work. I.e.: Users should not be affected. and removed Area: verification labels Nov 9, 2022
@zhassan-aws
Copy link
Contributor

This was done for several CVEs. This blog post describes one of the cases. Closing.

@github-actions github-actions bot mentioned this issue Feb 11, 2025
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
[C] Internal Tracks some internal work. I.e.: Users should not be affected.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@chinmaydd @celinval @zhassan-aws