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.

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

log4j vulnerability #46

Open
shawneeboyote opened this issue Apr 1, 2022 · 0 comments
Open

log4j vulnerability #46

shawneeboyote opened this issue Apr 1, 2022 · 0 comments

Comments

@shawneeboyote
Copy link

Hi, I saw sherlock demoed at the 2021 Druid conference and it really stoked my interest. I haven't used it yet because I noticed the log4j version is within the range of versions vulnerable to the JNDI lookup vulnerability that was discovered earlier this year(https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-44228). I was curious: is the corresponding lookup feature currently disabled in sherlock and/or are there are plans to upgrade to log4j2.15 or later?
Thanks!
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@shawneeboyote