Apache Log4j 2 VS log4j-patch

I don't think that's a good example. While Apache devs are volunteers and Microsoft devs are employees, they were criticized for their slow response time and seeming lack of urgency until it was far too late.

https://github.com/apache/logging-log4j2/pull/608#issuecomme...

However, there are many open source projects that are widely used but not well-known, including cURL, ImageMagick, MyCLI, Homebrew, Apache Log4j, and OpenSSL. This article will take a closer look at these unsung heroes of the open source world. I do not want to give them a business model or financial advice in this article. This largely depends on the author's personal experience and values. I just want to raise more awareness about these open source projects.

> When it was first revealed in early December 2021, the Log4Shell bug was described as one of the most severe security vulnerabilities ever.

> The Apache Software Foundation, which maintains the open-source tool, quickly released a patch...

Apache horribly mismanaged this and did not release a patch until it was already widely known and being exploited in the wild. They also messed up and had to release several subsequent patches to actually fix the vulnerability.

Remember: this vulnerability was disclosed to them in November.

https://github.com/apache/logging-log4j2/pull/608#issuecomme...

Think back to the Log4J event, were you affected? (https://github.com/apache/logging-log4j2)

Log4J(https://logging.apache.org/log4j/2.x/) is a Java-based logging framework. It is a part of Apache Logging Services. It was also the most popular and widely used Java logging solution until the exposure of its Log4Shell vulnerability last year.

Most applications currently use Log4J2 or SLF4J. Both provide a compatible System.Logger implementation.

In software, you can go and see exactly who did what, when. How the Log4Shell vulnerability was patched, its detailed history and can work out how long that vulnerability was there for. Same with Wikipedia, where you can see every edit and discuss those that were made. It should not take a law degree and weeks of examination to find some bullshit is being slid into a bill, this is criminal.

There is also log4j-patch which might allow you to resolve issues with it.

https://github.com/Glavo/log4j-patch

This is a non-intrusive patch that allows you to block this vulnerability without modifying the program code/updating the dependent. So you can use it to patch third-party programs, such as Minecraft.

The principle of the library is simple: It provides an empty JndiLookup to override the implementation in log4j. Log4j2 can handle this situation and safely disable JNDI lookup.

It is compatible with all versions of log4j2 (2.0~2.15).

Note that the formatMsgNoLookups workaround only applies to recent versions of the log4j library, while it's still unclear how far back this bug may stretch. Other options for patching are detailed in the thread: https://github.com/apache/logging-log4j2/pull/608#issuecomme... mentions that just removing the class providing the vulnerable behavior works well, and https://github.com/Glavo/log4j-patch is a JAR that you can add to your classpath to simply override the same class.

See https://github.com/apache/logging-log4j2/pull/608#issuecomme... for more details.