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

Not working for log4j-1.x where JMSAppender.class exists #65

Open
prsng opened this issue Dec 21, 2021 · 1 comment
Open

Not working for log4j-1.x where JMSAppender.class exists #65

prsng opened this issue Dec 21, 2021 · 1 comment

Comments

@prsng
Copy link

prsng commented Dec 21, 2021

We are using logpresso scanner and it seems to be flagging a lot more files with potential vulnerability after log4j 1.x was added to the CVEs.
log4j-finder is however skipping those files entirely and not flagging anything.

I am curious as to which one is reliable and why is it that log4j-finder thinks that this one is not potentially vulnerable.

Attaching a file for reference
log4j.jar.zip
.

@yunzheng
Copy link
Member

This tool was mainly developed to catch vulnerable log4j 2.x versions. There is a ticket to add log4j 1.x support, see #14

next version will probably also have support for this and also other corner cases.

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