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

Posted to notifications@logging.apache.org by "Matt Sicker (Jira)" <ji...@apache.org> on 2021/12/28 19:30:00 UTC

[jira] [Updated] (LOG4J2-3293) JDBC Appender should use JNDI Manager and JNDI access should be limited.

     [ https://issues.apache.org/jira/browse/LOG4J2-3293?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Matt Sicker updated LOG4J2-3293:
--------------------------------
    Description: 
JDBC Appender should use JndiManager when accessing JNDI. JNDI access should be controlled via a system property.

Related to [CVE-2021-44832|https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-44832] where an attacker with permission to modify the logging configuration file can construct a malicious configuration using a JDBC Appender with a data source referencing a JNDI URI which can execute remote code.

  was:JDBC Appender should use JndiManager when accessing JNDI. JNDI access should be controlled via a system property.


> JDBC Appender should use JNDI Manager and JNDI access should be limited.
> ------------------------------------------------------------------------
>
>                 Key: LOG4J2-3293
>                 URL: https://issues.apache.org/jira/browse/LOG4J2-3293
>             Project: Log4j 2
>          Issue Type: Bug
>          Components: Appenders
>    Affects Versions: 2.17.0
>            Reporter: Ralph Goers
>            Priority: Major
>             Fix For: 2.17.1
>
>
> JDBC Appender should use JndiManager when accessing JNDI. JNDI access should be controlled via a system property.
> Related to [CVE-2021-44832|https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-44832] where an attacker with permission to modify the logging configuration file can construct a malicious configuration using a JDBC Appender with a data source referencing a JNDI URI which can execute remote code.



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