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] Security upgrade org.apache.hadoop:hadoop-client-api from 3.3.2 to 3.4.0 #27

Closed
wants to merge 1 commit into from

Conversation

onokatio
Copy link
Member

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:
    • java/adapter/orc/pom.xml

Vulnerabilities that will be fixed

With an upgrade:
Severity Priority Score (*) Issue Upgrade Breaking Change Exploit Maturity Reachability
medium severity 520/1000
Why? Proof of Concept exploit, Has a fix available, CVSS 5.9
Integer Overflow or Wraparound
SNYK-JAVA-ORGXERIALSNAPPY-5710959
org.apache.hadoop:hadoop-client-api:
3.3.2 -> 3.4.0
No Proof of Concept No Path Found
high severity 600/1000
Why? Proof of Concept exploit, Has a fix available, CVSS 7.5
Denial of Service (DoS)
SNYK-JAVA-ORGXERIALSNAPPY-5710960
org.apache.hadoop:hadoop-client-api:
3.3.2 -> 3.4.0
No Proof of Concept No Path Found
medium severity 520/1000
Why? Proof of Concept exploit, Has a fix available, CVSS 5.9
Integer Overflow or Wraparound
SNYK-JAVA-ORGXERIALSNAPPY-5710961
org.apache.hadoop:hadoop-client-api:
3.3.2 -> 3.4.0
No Proof of Concept No Path Found
high severity 600/1000
Why? Proof of Concept exploit, Has a fix available, CVSS 7.5
Allocation of Resources Without Limits or Throttling
SNYK-JAVA-ORGXERIALSNAPPY-5918282
org.apache.hadoop:hadoop-client-api:
3.3.2 -> 3.4.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:

🦉 Denial of Service (DoS)
🦉 Allocation of Resources Without Limits or Throttling

Copy link

Thanks for opening a pull request!

If this is not a minor PR. Could you open an issue for this pull request on GitHub? https://github.com/apache/arrow/issues/new/choose

Opening GitHub issues ahead of time contributes to the Openness of the Apache Arrow project.

Then could you also rename the pull request title in the following format?

GH-${GITHUB_ISSUE_ID}: [${COMPONENT}] ${SUMMARY}

or

MINOR: [${COMPONENT}] ${SUMMARY}

In the case of PARQUET issues on JIRA the title also supports:

PARQUET-${JIRA_ISSUE_ID}: [${COMPONENT}] ${SUMMARY}

See also:

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

Successfully merging this pull request may close these issues.

2 participants