-
Notifications
You must be signed in to change notification settings - Fork 11.2k
fix(archives): wrap the bare EOFError a truncated tar.gz raises #3938
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Open
Noor-ul-ain001
wants to merge
2
commits into
github:main
Choose a base branch
from
Noor-ul-ain001:fix/tar-truncation-eoferror
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
+180
−3
Open
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or 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
This file contains hidden or 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
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Good catch — the
zlib.errorarm genuinely had no coverage. Fixed in ef49acc, with one correction to the claim the PR made about it.zlib.erroris reachable, but only at the twosafe_extract_tarsites.tarfileconverts it toReadErrorwhen it surfaces while reading a member header, but the forward seek it performs to skip member data (tarfile.next,tarfile.py:2829-2834) sits outside that conversion, so a corrupt region past the first header escapes raw:Reaching that seek needs members larger than the gzip read buffer — with small members the whole stream is decompressed during the first header read and the error gets wrapped, which is why single-byte corruption of the original 2.5 KiB fixture only ever produced
ReadError. The new fixture uses two 256 KiB members atcompresslevel=1(a ~7 KiB archive, ~20 ms) corrupted past the midpoint so the first header still reads clean.Four tests added: both
safe_extract_tarsites (plain and with a caller-suppliederror_type),safe_extract_archivewith a caller-suppliederror_type, and a guard asserting the fixture still reaches the module as a barezlib.error— so if a future Python wraps it, that fails loudly rather than the coverage silently decaying into a duplicate of theEOFErrorcases.Test-the-test: the three wrapping tests fail against unmodified
_download_security.pywith the rawzlib.errorabove, and pass with the fix.Correction to the original PR description: it implied the probe in
detect_archive_formatneeded thezlib.errorarm too. It doesn't.tarfile.openalone only ever performs the header read thattarfilealready converts, so I fuzzed 2800 corrupt archives against it and got zero barezlib.error— onlyReadError(610) or clean opens (2190). That arm is defensive at the probe site, not load-bearing. The tuple comment and the detection test now state this explicitly instead of implying coverage that can't exist. The probe still needs itsEOFErrorarm, which the existing truncation test covers.tests/test_download_security.py: 193 passed. TheEOFErrorbehavior and the deliberateOSError-only-on-extraction split are unchanged.