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

HIVE-26568: Upgrade log4j to 2.18.0 due to CVEs (Naveen Gangam) #3623

Closed
wants to merge 1 commit into from

Conversation

nrg4878
Copy link
Contributor

@nrg4878 nrg4878 commented Sep 27, 2022

Why are the changes needed?

CVEs

Does this PR introduce any user-facing change?

No

How was this patch tested?

Unit tests

@sonarcloud
Copy link

sonarcloud bot commented Sep 27, 2022

Kudos, SonarCloud Quality Gate passed!    Quality Gate passed

Bug A 0 Bugs
Vulnerability A 0 Vulnerabilities
Security Hotspot A 0 Security Hotspots
Code Smell A 7 Code Smells

No Coverage information No Coverage information
No Duplication information No Duplication information

Copy link
Member

@ayushtkn ayushtkn left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

+1, Pending tests.
Same as #3624

Copy link
Contributor

@zabetak zabetak left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I didn't see a CVE in 2.18.0 so the summary here and description in JIRA are misleading.

Moreover, I that the 2.19.0 version is already out. Maybe it makes sense to upgrade directly to the latest if it doesn't break stuff.

@github-actions
Copy link

This pull request has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs.
Feel free to reach out on the dev@hive.apache.org list if the patch is in need of reviews.

@github-actions github-actions bot added the stale label Nov 27, 2022
@github-actions github-actions bot closed this Dec 5, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
4 participants