Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Snyk] Upgrade commons-io:commons-io from 2.6 to 2.17.0 #22

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

marcoandries
Copy link

snyk-top-banner

Snyk has created this PR to upgrade commons-io:commons-io from 2.6 to 2.17.0.

ℹ️ Keep your dependencies up-to-date. This makes it easier to fix existing vulnerabilities and to more quickly identify and fix newly disclosed vulnerabilities when they affect your project.


  • The recommended version is 13 versions ahead of your current version.

  • The recommended version was released on 23 days ago.

Issues fixed by the recommended upgrade:

Issue Score Exploit Maturity
medium severity Directory Traversal
SNYK-JAVA-COMMONSIO-1277109
651 Mature
medium severity Uncontrolled Resource Consumption
SNYK-JAVA-COMMONSIO-8161190
651 No Known Exploit

Important

  • Check the changes in this PR to ensure they won't cause issues with your project.
  • This PR was automatically created by Snyk using the credentials of a real user.
  • Max score is 1000. Note that the real score may have changed since the PR was raised.

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open upgrade PRs.

For more information:

Snyk has created this PR to upgrade commons-io:commons-io from 2.6 to 2.17.0.

See this package in maven:
commons-io:commons-io

See this project in Snyk:
https://app.snyk.io/org/itext/project/fccba090-a933-44be-81ef-16058c83db07?utm_source=github&utm_medium=referral&page=upgrade-pr
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants