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鈥檒l occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Snyk] Security upgrade org.apache.avro:avro from 1.8.2 to 1.9.0 #19

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

Conversation

ekmixon
Copy link
Owner

@ekmixon ekmixon commented Sep 27, 2023

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 Reachability
high severity 650/1000
Why? Proof of Concept exploit, Recently disclosed, Has a fix available, CVSS 7.5
Allocation of Resources Without Limits or Throttling
SNYK-JAVA-ORGXERIALSNAPPY-5918282
org.apache.avro:avro:
1.8.2 -> 1.9.0
No Proof of Concept No Path Found

(*) 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

@guardrails
Copy link

guardrails bot commented Sep 27, 2023

鈿狅笍 We detected 11 security issues in this pull request:

Vulnerable Libraries (11)
Severity Details
Medium pkg:maven/commons-net/[email protected] (t) upgrade to: 3.9.0
Critical pkg:maven/log4j/[email protected] (t) - no patch available
High pkg:maven/com.fasterxml.jackson.core/[email protected] (t) upgrade to: 2.13.2.1,2.12.6.1
Medium pkg:maven/org.apache.ivy/[email protected] (t) upgrade to: 2.5.1
High pkg:maven/org.apache.commons/[email protected] (t) upgrade to: 1.21
Medium pkg:maven/com.google.protobuf/[email protected] (t) upgrade to: 3.19.6,3.21.7,3.16.3,3.20.3
High pkg:maven/org.yaml/[email protected] (t) upgrade to: 1.31
Medium pkg:maven/org.apache.spark/[email protected] (t) - no patch available
Medium pkg:maven/org.apache.zookeeper/[email protected] (t) upgrade to: 3.4.14,3.5.5
High pkg:maven/org.apache.hadoop/[email protected] (t) upgrade to: 2.7.0
Medium pkg:maven/org.xerial.snappy/[email protected] (t) upgrade to: 1.1.10.1

More info on how to fix Vulnerable Libraries in Java.


馃憠 Go to the dashboard for detailed results.

馃摜 Happy? Share your feedback with us.

@secure-code-warrior-for-github

Micro-Learning Topic: Vulnerable library (Detected by phrase)

Matched on "Vulnerable Libraries"

What is this? (2min video)

Use of vulnerable components will introduce weaknesses into the application. Components with published vulnerabilities will allow easy exploitation as resources will often be available to automate the process.

Try a challenge in Secure Code Warrior

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
2 participants