max-mapper / max-mapper/extract-zip
Possible security concern
Open
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 398
- Forks
- 144
- PR merge metrics
- No merged PRs in 30d
Description
The library uses yauzl in the back which itself does not protect from zip bomb attacks. To avoid this, make sure the compression size is checked, the number of files and also prevent recursively going thourgh the archives when extracting.
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
No file, test, or entry point is named. Start by tracing the extraction path and its yauzl integration, then determine appropriate limits for compression size and file count and how recursive archives are identified. Done means extraction enforces those limits and does not recursively traverse nested archives.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- security
- Issue type
- Bug
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100