Update Junit version to address CVE-2020-15250#163
Merged
pietrygamat merged 1 commit intomasterfrom Dec 15, 2023
Merged
Conversation
|
Why would maven flag us on a test dependency? Does it actually track to that level? |
Collaborator
Author
|
Heh, the beauty of automated security scans :) . On the plus side - that's actually not Maven Central's flags, but mvnrepository.com's. Sonatype's Maven Central scores jssc 9/10 with zero threats - even before the update. |
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
2 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.
Junit 4.12 is flagged as vulnerable to CVE-2020-15250. Although realistically this is not a threat to library users, it's worth updating to avoid being flagged on Maven Central.