Potential fix for code scanning alert no. 703: Arbitrary file write during tarfile extraction #2586
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.
Potential fix for https://github.com/Trusted-AI/adversarial-robustness-toolbox/security/code-scanning/703
To fix the problem, we need to ensure that the paths within the tar archive do not contain any directory traversal elements (
..
). This can be achieved by validating each entry in the tar archive before extracting it. Specifically, we should check that the entry name is not an absolute path and does not contain any..
elements._extract
function to include validation for each entry in the tar archive.Suggested fixes powered by Copilot Autofix. Review carefully before merging.