Update commons-io to 2.17.0 #802
Merged
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
|
Hi @jowiho! Thanks for your contribution! This will require an update to our https://github.com/JLLeitschuh/ktlint-gradle/blob/main/CHANGELOG.md. Would you be so kind as to add a line to that doc? Other than that, I'm more than happy to merge this change! Thank you so much! |
|
@JLLeitschuh, sure! I've added a commit to update |
Update the `commons-io` library to the latest version to mitigate CVE-2024-47554. Though I don't believe that this CVE can be exploited through ktlint-gradle, it's still a good practice to avoid CVEs, if only to stop automated scanners from flagging this (as a false positive).
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.
Update the
commons-iolibrary to the latest version to mitigate CVE-2024-47554. Though I don't believe that this CVE can be exploited through ktlint-gradle, it's still a good practice to avoid CVEs, if only to stop automated scanners from flagging this (as a false positive).