SR-G commented on pull request #607: URL: https://github.com/apache/logging-log4j2/pull/607#issuecomment-993513692
Does anyone knows when exactly inside the LOG4J2 stack this bug may be triggered ? Is it only at "rendering" level, or may it be before ? For the context, in my case : all logs are routed by LOG4J2 (2.14.0), but trapped by a specific appender in which LoggingEvent are transformed into something else, and these transformed objects are then stored into an ElasticSearch database. After that, the display of these logs is done in a proprietary way (without LOG4J2 being involved in any way). So my feeling is that in this very specific situation, this security issue could not be triggered ... assuming the problematic code is only triggered inside LOG4J2 layout rendering. Hence this question, any ideas about "when" this problem can be triggered ? -- 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: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
