log4shell-tools vs log4j2-without-jndi

log4shell-tools

Tool that runs a test to check whether one of your applications is affected by the recent vulnerabilities in log4j: CVE-2021-44228 and CVE-2021-45046 (by alexbakker)

Source Code

log4shell.alexbakker.me

Suggest alternative

Edit details

log4j2-without-jndi

log4j2-core JAR w/o JndiLookup.class (by zhangyoufu)

Suggest topics

DISCONTINUED

Suggest alternative

Edit details

Our great sponsors

WorkOS - The modern identity platform for B2B SaaS

InfluxDB - Power Real-Time Data Analytics at Scale

SaaSHub - Software Alternatives and Reviews

Our great sponsors

log4shell-tools		log4j2-without-jndi
	Project
8	Mentions	1
84	Stars	60
-	Growth	-
4.5	Activity	0.0
23 days ago	Latest Commit	over 2 years ago
Go	Language	Shell
MIT License	License	-

The number of mentions indicates the total number of mentions that we've tracked plus the number of user suggested alternatives.
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.

log4shell-tools

Posts with mentions or reviews of log4shell-tools. We have used some of these posts to build our list of alternatives and similar projects. The last one was on 2022-07-20.

Log4j: The Pain Just Keeps Going and Going
8 projects | news.ycombinator.com | 20 Jul 2022

I'm seeing this as well. While the amount of traffic has certainly decreased compared to the first couple of days after the CVE was announced, https://log4shell.tools is still being used by people every day.
How to send similar payload to different http headers?
1 project | /r/HowToHack | 6 Apr 2022

e.g. from log4j. Taken from https://log4shell.tools/
Received a visit from the infamous Dejmnok420 today. Can anyone ELI5 the steps to take now?
1 project | /r/admincraft | 1 Mar 2022

I run tests with https://log4shell.tools, and it seems I'm vulnerable on client side, but my server is safe, which makes sense as I compiled the .jar 2 weeks ago with BuildTools as indicated here https://www.spigotmc.org/threads/spigot-security-releases-%E2%80%94-1-8-8%E2%80%931-18.537204/
Log4Shell Vulnerability Test Tool
2 projects | news.ycombinator.com | 16 Dec 2021

You're right, but this has always been the trade off with tools like this. You put some trust in the tool's authors and gain some insight in return. Remember the services that tested for Heartbleed (e.g. https://filippo.io/Heartbleed/)? Fairly similar trade-off, but still these tools were widely used.
If you really don't trust me and have some technical know-how, you can self host the service. It's open source: https://github.com/alexbakker/log4shell-tools.
Log4j 2.15.0 – Previously suggested mitigations may not be enough
7 projects | news.ycombinator.com | 16 Dec 2021

I can't say I'm feeling the same. Still lots of people testing over at https://log4shell.tools almost a week after this vulnerability became widely known. Plenty of people still discovering they're vulnerable as well. I think it's likely that these are just the people who know they're using log4j. If you're running a black box product from a vendor you'll have no clue you're vulnerable until it's too late.
Analysis of the 2nd Log4j CVE published earlier (CVE-2021-45046 / Log4Shell2)
11 projects | news.ycombinator.com | 14 Dec 2021

I have a feeling this vulnerability is going to be with us for years. Shameless plug: I built a tool that assists in detecting whether you're vulnerable to this or the previous CVE: https://log4shell.tools. Just enter the JNDI URI it gives you anywhere you suspect it ends up causing a message lookup in log4j. If log4j does so much as a DNS lookup, this tool will tell you about it.
log4shell.tools - Check if you're vulnerable to an egregious case of log4shell
1 project | /r/netsec | 13 Dec 2021

Done! https://github.com/alexbakker/log4shell-tools

log4j2-without-jndi

Posts with mentions or reviews of log4j2-without-jndi. We have used some of these posts to build our list of alternatives and similar projects. The last one was on 2021-12-14.

Analysis of the 2nd Log4j CVE published earlier (CVE-2021-45046 / Log4Shell2)
11 projects | news.ycombinator.com | 14 Dec 2021

What about this patch https://github.com/zhangyoufu/log4j2-without-jndi/blob/maste... of removing JndiLookup.class , seems still right

What are some alternatives?

When comparing log4shell-tools and log4j2-without-jndi you can also consider the following projects:

ysoserial - A proof-of-concept tool for generating payloads that exploit unsafe Java object deserialization.

log4shell-ldap - A tool for checking log4shell vulnerability mitigations

lunasec - LunaSec - Dependency Security Scanner that automatically notifies you about vulnerabilities like Log4Shell or node-ipc in your Pull Requests and Builds. Protect yourself in 30 seconds with the LunaTrace GitHub App: https://github.com/marketplace/lunatrace-by-lunasec/

Apache Log4j 2 - Apache Log4j 2 is a versatile, feature-rich, efficient logging API and backend for Java.

log4j-affected-db - A community sourced list of log4j-affected software

log4j-log4shell-affected - Lists of affected components and affected apps/vendors by CVE-2021-44228 (aka Log4shell or Log4j RCE). This list is meant as a resource for security responders to be able to find and address the vulnerability

aegis4j - A Java agent that disables platform features you don't use, before an attacker uses them against you.

log4jshell-pdf - The purpose of this project is to demonstrate the Log4Shell exploit with Log4J vulnerabilities using PDF as delivery channel

Logout4Shell - Use Log4Shell vulnerability to vaccinate a victim server against Log4Shell