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

Upgrade vulnerable version of reload4j and aws-java-sdk dependencies #24606

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

Conversation

ShahimSharafudeen
Copy link
Contributor

Upgrade the aws-java-sdk version to 1.12.640 to fix the ion-java vulnerability
Upgrade the reload4j version to 1.2.22 to fix the vulnerability

Description

Motivation and Context

Impact

Test Plan

Contributor checklist

  • Please make sure your submission complies with our contributing guide, in particular code style and commit standards.
  • PR description addresses the issue accurately and concisely. If the change is non-trivial, a GitHub Issue is referenced.
  • Documented new properties (with its default value), SQL syntax, functions, or other functionality.
  • If release notes are required, they follow the release notes guidelines.
  • Adequate tests were added if applicable.
  • CI passed.

Release Notes

Please follow release notes guidelines and fill in the release notes below.

== RELEASE NOTES ==

General Changes
* ... 
* ... 

Hive Connector Changes
* ... 
* ... 

If release note is NOT required, use:

== NO RELEASE NOTE ==

@prestodb-ci prestodb-ci added the from:IBM PR from IBM label Feb 21, 2025
Upgrade the aws-java-sdk version to 1.12.640 to fix the ion-java vulnerability
Upgrade the reload4j version to 1.2.22 to fix the vulnerability.
@ShahimSharafudeen ShahimSharafudeen force-pushed the prestodb_forwardfit_CVE_fix_ion-java branch from 70da419 to ca2dee0 Compare February 21, 2025 15:09
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
from:IBM PR from IBM
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants