-
Notifications
You must be signed in to change notification settings - Fork 4.7k
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
HIVE-28671 : Upgrade MySQL connector jar version to 8.2.0 #5580
Conversation
5eb238e
to
fba28ca
Compare
fba28ca
to
f44e1be
Compare
87a9b18
to
90a24f8
Compare
90a24f8
to
f09197f
Compare
f09197f
to
521c6a4
Compare
Quality Gate passedIssues Measures |
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.
LGTM. Thanks for wrapping up the current situation and potential options. I also confirmed 8.3.0 requires MySQL 8.0.
https://dev.mysql.com/doc/relnotes/connector-j/en/news-8-3-0.html
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.
LGTM
What changes were proposed in this pull request?
MySQL version upgrade from 8.0.31 to 8.2.0
Why are the changes needed?
The current version of MySQL connector jar is 8.0.31, which has the following vulnerabilities associated with it:
Direct vulnerabilities:
CVE-2023-22102
Vulnerabilities from dependencies:
CVE-2024-7254
CVE-2022-3510
CVE-2022-3509
CVE-2022-3171
So, this issue is to remedy this with the version upgrade as a fix.
https://dev.mysql.com/doc/relnotes/connector-j/en/news-8-2-0.html
Mysql connector/J version 8.2.0 is the smallest upgrade that fixes the CVEs and can be used against MySQL Server version 5.7 and later.
Versions 8.3.0 and above are compatible with mysql server versions 8.0 and above, and since the current version is 5.7.37 (at least as long as #5525 is not merged and upgrades it to 8.4.3) upgrading mysql connecter jar version to 8.2.0 instead of 8.4.0 is the present solution.
Does this PR introduce any user-facing change?
No
Is the change a dependency upgrade?
Yes
How was this patch tested?
Existing tests