Skip to content

[Snyk] Security upgrade org.apache.commons:commons-compress from 1.21 to 1.26.0 - #3308

Open
AndyDaniel1 wants to merge 12 commits into
developmentfrom
snyk-fix-24b7b35ed1a1e84cb99b22ec82cf2d94
Open

[Snyk] Security upgrade org.apache.commons:commons-compress from 1.21 to 1.26.0#3308
AndyDaniel1 wants to merge 12 commits into
developmentfrom
snyk-fix-24b7b35ed1a1e84cb99b22ec82cf2d94

Conversation

@AndyDaniel1

Copy link
Copy Markdown
Contributor

This PR was automatically created by Snyk using the credentials of a real user.


Snyk has created this PR to fix one or more vulnerable packages in the `maven` dependencies of this project.

Changes included in this PR

  • Changes to the following files to upgrade the vulnerable dependencies to a fixed version:
    • pom.xml

Vulnerabilities that will be fixed

With an upgrade:
Severity Priority Score (*) Issue Upgrade Breaking Change Exploit Maturity
high severity 691/1000
Why? Recently disclosed, Has a fix available, CVSS 8.1
Infinite loop
SNYK-JAVA-ORGAPACHECOMMONS-6254296
org.apache.commons:commons-compress:
1.21 -> 1.26.0
No No Known Exploit
medium severity 501/1000
Why? Recently disclosed, Has a fix available, CVSS 4.3
Allocation of Resources Without Limits or Throttling
SNYK-JAVA-ORGAPACHECOMMONS-6254297
org.apache.commons:commons-compress:
1.21 -> 1.26.0
No No Known Exploit

(*) Note that the real score may have changed since the PR was raised.

Check the changes in this PR to ensure they won't cause issues with your project.


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

For more information:
🧐 View latest project report

🛠 Adjust project settings

📚 Read more about Snyk's upgrade and patch logic


Learn how to fix vulnerabilities with free interactive lessons:

🦉 Allocation of Resources Without Limits or Throttling

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.

4 participants