Update Directory.Build.targets - #2468
#2468Merged
Merged
Update Directory.Build.targets#2468
Conversation
Updated SharpZip package version to 1.4.2
|
|
Member
|
Hi @Pashkinz92 thanks for this. Would it be possible for you to sign the CLA? We're unable to accept submissions without it. |
Contributor
Author
|
Of course :-) I Sorry, I missed that requirement |
This was referenced Jul 30, 2025
This was referenced Sep 29, 2025
This was referenced Nov 17, 2025
This was referenced Mar 23, 2026
This was referenced Apr 26, 2026
This was referenced Jun 2, 2026
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
Updated SharpZip package version to 1.4.2
There is malware
SharpZipLib (or #ziplib) is a Zip, GZip, Tar and BZip2 library. Prior to version 1.3.3, a TAR file entry
../evil.txtmay be extracted in the parent directory ofdestFolder. This leads to arbitrary file write that may lead to code execution. The vulnerability was patched in version 1.3.3.