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

CVE-2021-4104 QID #45

Open
surbo opened this issue Jan 12, 2022 · 0 comments
Open

CVE-2021-4104 QID #45

surbo opened this issue Jan 12, 2022 · 0 comments

Comments

@surbo
Copy link
Contributor

surbo commented Jan 12, 2022

Hello, are we able to get a new QID that will pick up CVE-2021-4104 when using the out of band scanner?

From the example readme file:
Log4j Found: 'D:\Temp\log4j-1.2.17.jar' ( Manifest Vendor: Apache Software Foundation, Manifest Version: 1.2.17, JNDI Class: NOT Found, Log4j Vendor: log4j, Log4j Version: 1.2.17, CVE Status: Potentially Vulnerable ( CVE-2021-4104: Found ) )
Log4j Found: 'D:\Temp\log4j-1.2.17.zip!apache-log4j-1.2.17/log4j-1.2.17.jar' ( Manifest Vendor: Apache Software Foundation, Manifest Version: 1.2.17, JNDI Class: NOT Found, Log4j Vendor: log4j, Log4j Version: 1.2.17, CVE Status: Potentially Vulnerable ( CVE-2021-4104: Found ) )

When the out of band scanner runs and the Qualys agent picks up the out of band scan data from the host, CVE-2021-4104 is being listed under QIDs 376193, 376160, 376195 ,376210 which have a different CVE associated with them.

Example:

Can we get a new QID created specifically for CVE-2021-4104 utilizing the out of band scanner?

Thank you

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

1 participant