You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@empire-db.apache.org by "PJ Fanning (Jira)" <ji...@apache.org> on 2022/02/18 00:19:00 UTC

[jira] [Created] (EMPIREDB-374) replace log4jv1 usage - EOL and with multiple security vulnerabilities

PJ Fanning created EMPIREDB-374:
-----------------------------------

             Summary: replace log4jv1 usage - EOL and with multiple security vulnerabilities
                 Key: EMPIREDB-374
                 URL: https://issues.apache.org/jira/browse/EMPIREDB-374
             Project: Empire-DB
          Issue Type: Improvement
            Reporter: PJ Fanning


[https://github.com/apache/empire-db/blob/master/pom.xml] has dependency on log4j 1.2.17

Options include:
 * switching to latest log4j v2
 * switch to logback
 * switch to reload4j - a fork of log4j v1 but with security fixes



--
This message was sent by Atlassian Jira
(v8.20.1#820001)