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

Log4j vulnerability - CVE-2019-17571 #3022

Open
dgnyshn opened this issue Dec 13, 2021 · 2 comments
Open

Log4j vulnerability - CVE-2019-17571 #3022

dgnyshn opened this issue Dec 13, 2021 · 2 comments

Comments

@dgnyshn
Copy link

dgnyshn commented Dec 13, 2021

Azkaban use log4j 1.2.16 version (which is oldest) and in this version vulnerability is kind of CVE-2021-44228.

Included in Log4j 1.2 is a SocketServer class that is vulnerable to deserialization of untrusted data which can be exploited to remotely execute arbitrary code when combined with a deserialization gadget when listening to untrusted network traffic for log data. This affects Log4j versions up to 1.2 up to 1.2.17.

With this task log4j version should be the 2.15.0.

If its ok, I'm willing to upgrade version.

@pavel-kalmykov
Copy link

Any updates on this? I think this might need some further attention. 🤔

@dgnyshn dgnyshn closed this as completed Jan 15, 2022
@dgnyshn dgnyshn reopened this Jan 15, 2022
@dgnyshn
Copy link
Author

dgnyshn commented Jan 15, 2022

Any updates on this? I think this might need some further attention. 🤔

I opened a pull request. #3033

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants