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.

Sign up for GitHub

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

Jump to bottom

Patch for log4j vulnerability - upgrade log4j #83

Open
akachru-github opened this issue Dec 16, 2021 · 2 comments
Open

Patch for log4j vulnerability - upgrade log4j #83

akachru-github opened this issue Dec 16, 2021 · 2 comments
Assignees
@jaserud

Comments

@akachru-github
Copy link

akachru-github commented Dec 16, 2021 •
edited
Loading

https://docs.google.com/spreadsheets/d/1SmGbsT0zFRb1EBkGV0AO71ZAtuiCzeUhBH_5Y5o_0vQ/edit#gid=0

patch wfgn services as they are exploitable.
@akachru-github
Copy link
Author

@blabadi , it looks like we may need to do another upgrade for the wfgn services in addition to the upgrade you have already done (log4j core 2.16 is what I believe you upgraded to). Looks like there is still a problem with 2.16 we want to solve by going to 2.17: https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-44832

I think either yourself or @jaserud can take a look at doing one more upgrade here?

@jaserud
Copy link
Contributor

jaserud commented Jan 7, 2022

@akachru-github I can take a look at this.

@jaserud jaserud assigned jaserud and unassigned blabadi Jan 7, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@jaserud jaserud

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@blabadi @jaserud @akachru-github