Skip to content

Log4j 2.17 for CVE-2021-45105 #11727

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
PaulStoffregen opened this issue Dec 18, 2021 · 3 comments · Fixed by #11730
Closed

Log4j 2.17 for CVE-2021-45105 #11727

PaulStoffregen opened this issue Dec 18, 2021 · 3 comments · Fixed by #11730
Labels
security Security fixes / bugs / improvements

Comments

@PaulStoffregen
Copy link
Contributor

PaulStoffregen commented Dec 18, 2021

Yet another log4j update for another vulnerability!

Not a duplicate of #11722 / #11723 version 2.16 for CVE-2021-44228.

Version 2.17 addresses CVE-2021-45105.

https://logging.apache.org/log4j/2.x/security.html

@per1234 per1234 added the security Security fixes / bugs / improvements label Dec 18, 2021
cmaglie added a commit to cmaglie/Arduino that referenced this issue Dec 20, 2021
@cmaglie cmaglie linked a pull request Dec 20, 2021 that will close this issue
@per1234 per1234 pinned this issue Dec 20, 2021
@PaulStoffregen
Copy link
Contributor Author

PaulStoffregen commented Dec 20, 2021

1.8.19? Edit - oh, now I see 5e38fe2

@PaulStoffregen
Copy link
Contributor Author

@cmaglie - Your fix for future log4j CVEs is paying dividends today, with CVE-2021-44832

@cmaglie
Copy link
Member

cmaglie commented Dec 29, 2021

Heh, I felt it, there are too many eyes on log4j right now...

@per1234 per1234 unpinned this issue Jan 7, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
security Security fixes / bugs / improvements
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants