[question] Checking for log4j vulnerabilities present in log4j-over-slf4j about slf4j HOT 3 CLOSED

log4j-over-slf4j is to take log4j1 and pipe it to slf4j. It is not vulnerable as it is not the logger. If your project is purely log4j2 usage, you would not be using this library. Its for legacy projects that still have not migrated to modern projects so that you don't lose logs.

from slf4j.

In addition to @hazendaz comments, I would like to mention the reload4j project which might be quite relevant here. Migrating from log4j 1.x to reload4j is very easy.

Here is a quote from the site:

Initiated by Ceki Gülcü, the original author of Apache log4j 1.x, the reload4j project is a fork of Apache log4j version 1.2.17 with the goal of fixing pressing security issues. Reload4j is a binary compatible, drop-in replacement for log4j version 1.2.17. By drop-in, we mean that you can replace log4j.jar with reload4j.jar in your build with no source code changes, no recompilation, nor rebuild being necessary.

from slf4j.

Thanks for y'all's help

from slf4j.