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

Posted to notifications@logging.apache.org by GitBox <gi...@apache.org> on 2021/12/13 15:55:01 UTC

[GitHub] [logging-log4j2] sushain-pandit commented on pull request #608: Restrict LDAP access via JNDI

sushain-pandit commented on pull request #608:
URL: https://github.com/apache/logging-log4j2/pull/608#issuecomment-992617101


   > > @asokolov-flex
   > > Log4J 1.2.17 is only (potentially) vulnerable if you choose to use the JMS Appender. If you are, you will have to migrate to Log4J2 / Logback.
   > 
   > If you use the JMS Appender AND you configure it with JNDI. If you configure logback with JMS and JNDI, I am guessing you'll have the same issue.
   
   Apologies if this has been ans prior: re log4j 1.2.17, is it a certainty that the only appender with the issue is JMS?


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: notifications-unsubscribe@logging.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org

Re: [GitHub] [logging-log4j2] sushain-pandit commented on pull request #608: Restrict LDAP access via JNDI

Posted by Gary Gregory <ga...@gmail.com>.

1.2 has been EOL for years so it has not received any attention, but the
JMS Appender is the only one that uses the JNDI API in 1.2, so it should be
OK otherwise.

Gary

On Mon, Dec 13, 2021 at 10:55 AM GitBox <gi...@apache.org> wrote:

>
> sushain-pandit commented on pull request #608:
> URL:
> https://github.com/apache/logging-log4j2/pull/608#issuecomment-992617101
>
>
>    > > @asokolov-flex
>    > > Log4J 1.2.17 is only (potentially) vulnerable if you choose to use
> the JMS Appender. If you are, you will have to migrate to Log4J2 / Logback.
>    >
>    > If you use the JMS Appender AND you configure it with JNDI. If you
> configure logback with JMS and JNDI, I am guessing you'll have the same
> issue.
>
>    Apologies if this has been ans prior: re log4j 1.2.17, is it a
> certainty that the only appender with the issue is JMS?
>
>
> --
> This is an automated message from the Apache Git Service.
> To respond to the message, please log on to GitHub and use the
> URL above to go to the specific comment.
>
> To unsubscribe, e-mail: notifications-unsubscribe@logging.apache.org
>
> For queries about this service, please contact Infrastructure at:
> users@infra.apache.org
>
>
>