🚨 [security] Update tar 4.4.13 → 6.2.1 (major) #95
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
![depfu[bot]](https://avatars.githubusercontent.com/in/715?s=60&v=4){kind=small}
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.
🚨 Your current dependencies have known security vulnerabilities 🚨
This dependency update fixes known security vulnerabilities. Please see the details below and assess their impact carefully. We recommend to merge and deploy this as soon as possible!
Here is everything you need to know about this upgrade. Please take a good look at what changed and the test results before merging this pull request.
What changed?
✳️ tar (4.4.13 → 6.2.1) · Repo · Changelog
Security Advisories 🚨
🚨 Denial of service while parsing a tar file due to lack of folders count validation
🚨 Arbitrary File Creation/Overwrite on Windows via insufficient relative path sanitization
🚨 Arbitrary File Creation/Overwrite via insufficient symlink protection due to directory cache poisoning using symbolic links
🚨 Arbitrary File Creation/Overwrite on Windows via insufficient relative path sanitization
🚨 Arbitrary File Creation/Overwrite via insufficient symlink protection due to directory cache poisoning using symbolic links
🚨 Arbitrary File Creation/Overwrite on Windows via insufficient relative path sanitization
🚨 Arbitrary File Creation/Overwrite via insufficient symlink protection due to directory cache poisoning using symbolic links
🚨 Arbitrary File Creation/Overwrite via insufficient symlink protection due to directory cache poisoning using symbolic links
🚨 Arbitrary File Creation/Overwrite via insufficient symlink protection due to directory cache poisoning using symbolic links
🚨 Arbitrary File Creation/Overwrite via insufficient symlink protection due to directory cache poisoning using symbolic links
🚨 Arbitrary File Creation/Overwrite due to insufficient absolute path sanitization
🚨 Arbitrary File Creation/Overwrite due to insufficient absolute path sanitization
🚨 Arbitrary File Creation/Overwrite via insufficient symlink protection due to directory cache poisoning
🚨 Arbitrary File Creation/Overwrite via insufficient symlink protection due to directory cache poisoning
🚨 Arbitrary File Creation/Overwrite due to insufficient absolute path sanitization
🚨 Arbitrary File Creation/Overwrite via insufficient symlink protection due to directory cache poisoning
Release Notes
6.1.13
6.1.12
Does any of this look wrong? Please let us know.
Commits
See the full diff on Github. The new version differs by more commits than we can show here.
Depfu will automatically keep this PR conflict-free, as long as you don't add any commits to this branch yourself. You can also trigger a rebase manually by commenting with
@depfu rebase.All Depfu comment commands