Taint tracking
Open
Nobody has claimed this yet.
enhancement
- Dominant language
- Python
- Stars
- 8.3k
- Forks
- 835
- Avg merge
- 5d 3h
- Merged PRs (30d)
- 1
Description
Transfer of OpenStack blueprint:
https://blueprints.launchpad.net/bandit/+spec/taint-tracking
Perform static taint tracking. At first this would be within a function. Make a best effort to detect when input is being cleaned before being passed to dangerous functions. Detect when input is not being cleaned before being passed to dangerous functions.
Contributor guide
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 reading the linked Launchpad blueprint for the intended taint-tracking scope. Then identify Bandit’s relevant analysis entry points; done means detecting, within a function, whether input is cleaned before it reaches dangerous functions, including reporting uncleaned flows.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- security
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100