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/14 10:53:17 UTC

[GitHub] [logging-log4j2] kmindi edited a comment on pull request #608: Restrict LDAP access via JNDI

kmindi edited a comment on pull request #608:
URL: https://github.com/apache/logging-log4j2/pull/608#issuecomment-993399258


   Following up on my question if this fixes usage with other property substitutions like ctx: https://github.com/apache/logging-log4j2/pull/608#issuecomment-992427010
   
   Apparently I could confirm my assumption regarding the usage of Thread Context Map, I created a PR here (https://github.com/lunasec-io/lunasec/pull/298) and made changes to the demonstration app to demonstrate the vulnerability even with `formatMsgNoLookups=true` set shown here: https://github.com/kmindi/log4shell-vulnerable-app. 
   
   Here is also the diff to see what I changed to demonstrate vulnerable `${ctx.apiversion}` usage in the log pattern: https://github.com/kmindi/log4shell-vulnerable-app/commit/e539f7e9a0c81e2c580d63caff5f4eae14033f19
   
   Can someone confirm this?


-- 
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