-
Notifications
You must be signed in to change notification settings - Fork 28.5k
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
[SPARK-41030][BUILD][3.2] Upgrade Apache Ivy
to 2.5.1
#39371
[SPARK-41030][BUILD][3.2] Upgrade Apache Ivy
to 2.5.1
#39371
Conversation
I will ping Sean, Hyukjin and dongjoon-hyun when all the tests have passed. |
Apache Ivy
to 2.5.1
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
+1, LGTM (Pending CIs).
Thank you, @bjornjorgensen .
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I fixed the linter failure here.
Merged to branch-3.2.
### What changes were proposed in this pull request? Upgrade `Apache Ivy` from 2.5.0 to 2.5.1 [Release notes](https://ant.apache.org/ivy/history/2.5.1/release-notes.html) ### Why are the changes needed? [CVE-2022-37865](https://nvd.nist.gov/vuln/detail/CVE-2022-37865) This is a [9.1 CRITICAL](https://nvd.nist.gov/vuln-metrics/cvss/v3-calculator?name=CVE-2022-37865&vector=AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:H&version=3.1&source=NIST) and [CVE-2022-37866](https://nvd.nist.gov/vuln/detail/CVE-2022-37866) ### Does this PR introduce _any_ user-facing change? No. ### How was this patch tested? Pass GA Closes #39371 from bjornjorgensen/ivy.version_2.5.1. Lead-authored-by: Bjørn Jørgensen <[email protected]> Co-authored-by: Bjørn <[email protected]> Signed-off-by: Dongjoon Hyun <[email protected]>
Thank you, @bjornjorgensen and @HyukjinKwon |
Thanks everyone. Will this be released in a new Spark 3.2.4 image? |
@kyle-ai2 Yes, this PR is a part of the 3.2 branch now. |
BTW, |
Before
|
Apache Spark community always recommends to use the latest one. In case of SPARK-41030, |
### What changes were proposed in this pull request? Upgrade `Apache Ivy` from 2.5.0 to 2.5.1 [Release notes](https://ant.apache.org/ivy/history/2.5.1/release-notes.html) ### Why are the changes needed? [CVE-2022-37865](https://nvd.nist.gov/vuln/detail/CVE-2022-37865) This is a [9.1 CRITICAL](https://nvd.nist.gov/vuln-metrics/cvss/v3-calculator?name=CVE-2022-37865&vector=AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:H&version=3.1&source=NIST) and [CVE-2022-37866](https://nvd.nist.gov/vuln/detail/CVE-2022-37866) ### Does this PR introduce _any_ user-facing change? No. ### How was this patch tested? Pass GA Closes apache#39371 from bjornjorgensen/ivy.version_2.5.1. Lead-authored-by: Bjørn Jørgensen <[email protected]> Co-authored-by: Bjørn <[email protected]> Signed-off-by: Dongjoon Hyun <[email protected]>
What changes were proposed in this pull request?
Upgrade
Apache Ivy
from 2.5.0 to 2.5.1Release notes
Why are the changes needed?
CVE-2022-37865 This is a 9.1 CRITICAL
and
CVE-2022-37866
Does this PR introduce any user-facing change?
No.
How was this patch tested?
Pass GA