Updated vulnerable dependencies System.Security.Cryptography and SharpZipLib #905
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.
Summary of the changes (Less than 80 chars)
SECURITY: Bumped System.Security.Cryptography to 6.0.1 and SharpZipLib to 1.4.2
Description
GHSA-2m65-m22p-9wjw
GHSA-m22m-h4rf-pwq3
GHSA-mm6g-mmq6-53ff
This has been tested in Azure DevOps to ensure .NET Framework can resolve dependency version conflicts with these changes.
I didn't see these in the SonarCloud control panel, but they were appearing in the logs.