PLSysSec / PLSysSec/cargo-scan
track information flow for arguments
Open
Nobody has claimed this yet.
roadmap-unplanned
- Dominant language
- Rust
- Stars
- 47
- Forks
- 7
- PR merge metrics
- No merged PRs in 30d
Description
Currently we are doing this only on the MIRAI backend, not the syn backend:
track possible value(s) that can flow into effectful sinks
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the existing argument-value tracking in the MIRAI backend and comparing it with the syn backend. Trace how effectful sinks are identified and how possible values are represented. Done means the syn backend tracks possible values flowing into effectful sinks with coverage comparable to MIRAI.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- compilers, security
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100