Fixes #201 - update xerces and xalan to versions without CVEs #218
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
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.
CVEs are being reported against compile time dependencies of JDOM. Whilst this is fairly minor, as these dependencies are optional at runtime, it does still have the potential to show up in security scans which can be a problem for anyone using JDOM, particularly in a regulated or security conscious domain.
To fix this I did the following:
This should resolve issue #201, issue #203 looks to be a duplicate and should also be resolved.
Note: also issue #216 is a different issue but if making a new build to release this change then the suggested fix in that issue should also be included to ensure a clean bill of health in security scans.
Thanks
Ben