crytic/slither

Identify missed reentrancy exploits by Slither

Open

#1,840 opened on Apr 14, 2023

View on GitHub
 (0 comments) (0 reactions) (0 assignees)Python (4,769 stars) (886 forks)batch import
enhancementhelp wanted

Description

Describe the desired feature

Identify which reentrancy exploits in my collection repo are currently overlooked by Slither and report them individually. Based on these findings, the reentrancy detectors can be (hopefully) improved.

Contributor guide

Tech stack
python
Domain
securityblockchain
Issue type
feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
4
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
over 1 week
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
clear
Prerequisites
Understanding of reentrancy attacksKnowledge of SolidityFamiliarity with Slither's codebase
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
20
Research direction
First, clone the repository at https://github.com/pcaversaccio/reentrancy attacks and run Slither on each contract to detect reentrancy vulnerabilities. Then, manually review each contract for reentrancy vulnerabilities that Slither missed. Document the findings in individual reports and submit them as issues on this repository for potential improvements to the reentrancy detectors.