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 1.2.17 and CVE-2019-17571 #4

Open
jonathan-dill-nih opened this issue Jan 18, 2022 · 2 comments
Open

log4j 1.2.17 and CVE-2019-17571 #4

jonathan-dill-nih opened this issue Jan 18, 2022 · 2 comments

Comments

@jonathan-dill-nih
Copy link

Just an FYI that this package contains a vulnerable version of log4j. It's not a huge showstopper for me as it's mainly a bit more convenient to use than instantclient, but if there is something else you have been using recently, any recommendation would be much appreciated. Thanks for your work on this project thus far.

@aimtiaz11
Copy link
Owner

@jonathan-dill-nih - Hi no I don't have a workaround currently.

However I did check what that vulnerability is about. It becomes an issue when listening in network traffic & performing logging which this CLI tool does not do.
https://www.whitesourcesoftware.com/vulnerability-database/CVE-2019-17571

So while the log4j library may contain the specified vulnerability, I dont think it can be exploited through this tool due to the way it works.

@kapcus
Copy link

kapcus commented Nov 7, 2022

still it would be great to fix it. In enterprise environment, there are automated filesystem scans searching for all potentially vulnerable and this tool is now being reported as vulnerable and removed by administrators afterwards - just because it is including vulnerable 3rd party component no matter if some function is called or not.

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

3 participants