Currently json schema validator is using com.sun.mail which depends on Java Mail API 1.6.2 and has vulnerabilities , should use jakarta mail instead. #411
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
… been moved Using jakarta mail latest instead of com.sun as mailapi artificat has been moved.
…s has been moved to jakarta. Uisng Jakarta mail imports instead of javax mail as mail api artifacts has been moved to jakarta.
naveengujjar29
changed the title
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.
Json shcema validator is using internally AddressException and InternetAddress for mail field validation from javax.mail.internet package which has dependency on Java Mail API (https://mvnrepository.com/artifact/com.sun.mail/javax.mail/1.6.2) and this version has the vulnerabilities.
If you see this has been moved to a new artifact https://mvnrepository.com/artifact/com.sun.mail/jakarta.mail which has more latest version and does not have any vulnerabilities.
We should also use the same in this repo. This PR has been raised for the same changes.