Add detection for recursive decompression bombs #52
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Thanks! let me review this in details! |
|
I forgot that we have the quine as test archives! |
Signed-off-by: Stefan Rehm <stefan@rehm.email>
srehm
force-pushed
the
feature/zipBombDetection
branch
from
e2b286d
to
b7d5cb2
Compare
|
Added DCO |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The idea is to build a set containing the hashes of already extracted archives along each filesystem branch.
If a new archive is detected that is already present in the set, it will not be extracted a second time.
This solves cases like in issue #50.