gh-112887: Fix tarfile FilterError handling to skip member extraction #112954
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.
In
tarfile
library, if a FilterError is raised for a member duringTarFile.extract()
orTarFile.extractall()
witherrorlevel
set to 0, a debugging message is correctly logged but the unsafe member is still extracted. Based on the documentation and a look at the code, it seems that the desired expectation witherrorlevel=0
is to not raise an exception, but skip member extraction and log the error.Updates
tarfile
to properly handleFilterError
and skip extraction on unsafe members even when an exception is not raised.This issue was reported on Python 3.11 and should likely be backported as it is a security issue.
From the docs: