Skip to content

Using CodeQL to find out Log4j CVE-2021-44228 - 4xpl0r3r's blog #17

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
Open
4xpl0r3r opened this issue Feb 14, 2023 · 0 comments
Open

Using CodeQL to find out Log4j CVE-2021-44228 - 4xpl0r3r's blog #17

4xpl0r3r opened this issue Feb 14, 2023 · 0 comments
Labels
2c370edb59219031067bc04af42043a1 Gitalk

Comments

@4xpl0r3r
Copy link
Owner

https://4xpl0r3r.com/Experience/Using-CodeQL-to-find-out-Log4j-CVE-2021-44228/

Although there is a experimental CWE-020 query used for “Potential Log4J LDAP JNDI injection (CVE-2021-44228)” already, but at this time, I want to refit the CWE-074 to make it could find out CVE-202
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
2c370edb59219031067bc04af42043a1 Gitalk
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@4xpl0r3r