Add check for decompression bomb vulnerabilities
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 8.3k
- Forks
- 836
- Avg merge
- 5d 3h
- Merged PRs (30d)
- 1
Description
Is your feature request related to a problem? Please describe.
Bandit currently does not detect potential decompression bomb vulnerabilities.
Describe the solution you'd like
Add a new check (for example, B114) that detects:
-
Direct dangerous calls:
gzip.decompress()zlib.decompress()bz2.decompress()lzma.decompress()- and other standard libs.
-
Reading from compressed files without size limit:
gzip.open()followed by.read()without size argument
Describe alternatives you've considered
gosec (Go security checker) has a similar rule (G110).
Additional context
- CWE-409: Improper Handling of Highly Compressed Data (Data Amplification)
- I'm happy to submit a PR if this feature is welcomed
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 with the linked gosec G110 rule and CWE-409 context, then review Bandit’s existing check conventions for standard-library decompression calls. Done means the requested direct calls and unbounded compressed-file reads are detected with appropriate coverage for the supported cases.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- security
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 52/100