[
https://issues.apache.org/jira/browse/LOG4J2-3293?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17468049#comment-17468049
]
Eric Everman edited comment on LOG4J2-3293 at 1/3/22, 3:05 PM:
---------------------------------------------------------------
Could someone please clarify this detail in the [vulnerability related to this
issue|https://logging.apache.org/log4j/2.x/security.html]:
{quote}...vulnerable to a remote code execution (RCE) attack where an attacker
with permission to modify the logging configuration file can construct a
malicious configuration using a JDBC Appender
{quote}
I _think_ what this means to say is that a JDBC appender must be configured to
be vulnerable to a RCE attack. As it currently reads, it sounds like a RCE
attacker needs access to the configuration file, which would not really be an
RCE attack.
was (Author: [email protected]):
Could someone please clarify this detail in the [vulnerability related to this
issue|https://logging.apache.org/log4j/2.x/security.html]:
{quote}vulnerable to a remote code execution (RCE) attack where an attacker
with permission to modify the logging configuration file
{quote}
I _think_ what this means to say is that a JDBC appender must be configured to
be vulnerable to a RCE attack. As it currently reads, it sounds like a RCE
attacker needs access to the configuration file, which would not really be an
RCE attack.
> 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, 2.12.3, 2.3.1
> Reporter: Ralph Goers
> Assignee: Gary D. Gregory
> Priority: Major
> Fix For: 2.17.1, 2.3.2, 2.12.4
>
>
> 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.
> Fixed in
> [https://github.com/apache/logging-log4j2/commit/05db5f9527254632b59aed2a1d78a32c5ab74f16]
>
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
