adoptium.net VS Apache Log4j 2

1.18 requires Java 17. (Java link if you need it)

Note: In order for JarFix to work, you needed add all options when installing Java (Picture).

Did you actually install a Java Development Kit? Because this sounds like you only installed a text editor. You can download it here: https://adoptium.net/ (download the latest version for your OS and install it)

Try this https://adoptium.net/

Make sure you have Java fully installed (select all components when installing). Link to Java download if you need it: (Link)

if you downloaded Java from adoptopenjdk/adoptium/temurin/whatever they call it now, you do have it.

I had the same issue and I fixed it with downloading openjdk 17. you can download it here https://adoptium.net/

Which was recently rebranded as Eclipse Temurin

if they are using Windows, have them reinstall java https://adoptium.net/

e.g https://adoptium.net/

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...

The official website. The vulnerability was introduced in 2.0-beta7 which was released in 2013.

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.

What you need is log4j-core, what you downloaded is some kind of connector between log4j and JUL. Tbh I don't know what JUL is, but that's not important. You can get log4j-core on from the official website - https://logging.apache.org/log4j/2.x/ or in maven repo. In case you're not using maven, I highly, highly recommend you using it for managing your dependencies.

> 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)