Skip to content

CVE-2021-44228 upgrade log4j to 2.16.0 (fixes #190) #191

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

Closed

Conversation

SalesforceBrian
Copy link

@SalesforceBrian SalesforceBrian commented Dec 14, 2021

upgrade log4j to 2.16.0 (fixes #190)

It was found that the fix to address CVE-2021-44228 in Apache Log4j 2.15.0 was incomplete

https://www.cve.org/CVERecord?id=CVE-2021-45046

@SalesforceBrian SalesforceBrian changed the title upgrade log4j to 2.16.0 (fixed #190) upgrade log4j to 2.16.0 (fixes #190) Dec 14, 2021
@SalesforceBrian SalesforceBrian changed the title upgrade log4j to 2.16.0 (fixes #190) CVE-2021-44228 upgrade log4j to 2.16.0 (fixes #190) Dec 14, 2021
@SalesforceBrian
Copy link
Author

#195

@SalesforceBrian SalesforceBrian deleted the log4j-2.16.0 branch December 17, 2021 23:52
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

CVE-2021-44228: Upgrade log4j to 2.16.0
1 participant