-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
Avoid Log4J "Log4Shell" exploit #5910
Conversation
cbeams
commented
Dec 10, 2021
This is in preparation for addressing log4j 2 zero day exploit described at https://www.lunasec.io/docs/blog/log4j-zero-day/. See full details in the next commit. Bringing in the dependency-management plugin results in many changes to our Gradle verification metadata file, but all are BOM / POM / Module manifests. No additional jar or code dependencies have been whitelisted with this change.
This commit upgrades our transitive dependency on Log4J 2 from 2.14.1 to the newly-released 2.15.0 to avoid the CVE described at https://www.lunasec.io/docs/blog/log4j-zero-day/. We do not use log4j directly anywhere in our codebase, so our exposure to this exploit was already mitigated if not eliminated, but Spring Boot depends on Log4J 2 internally. This commit upgrades Spring Boot's underlying dependency on Log4J to 2.15.0 in the manner recommended at spring-projects/spring-boot#28958.
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.
utACK - running a local build worked. I'll continue testing this in the release branch on multiple plattforms.
utACK |
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.
Post merge ACK, running fine on wizpriceje6q5tdrxkyiazsgu7irquiqjy2dptezqhrtu7l2qelqktid
Should it be updated again to 2.16.0? https://www.zdnet.com/article/second-log4j-vulnerability-found-apache-log4j-2-16-0-released/ |
Yes, will submit another PR shortly. |
See #5928 |