You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@pulsar.apache.org by GitBox <gi...@apache.org> on 2021/12/18 15:13:14 UTC
[GitHub] [pulsar] lhotari opened a new pull request #13392: [Security] Upgrade to Log4J 2.17.0 to mitigate CVE-2021-45105
lhotari opened a new pull request #13392:
URL: https://github.com/apache/pulsar/pull/13392
### Motivation
- more details at https://logging.apache.org/log4j/2.x/security.html
description of CVE-2021-45105
> Apache Log4j2 versions 2.0-alpha1 through 2.16.0 did not protect from uncontrolled recursion from self-referential lookups. When the logging configuration uses a non-default Pattern Layout with a Context Lookup (for example, $${ctx:loginId}), attackers with control over Thread Context Map (MDC) input data can craft malicious input data that contains a recursive lookup, resulting in a StackOverflowError that will terminate the process. This is also known as a DOS (Denial of Service) attack.
- default Pulsar configurations aren't impacted
### Modifications
- upgrade Log4J version from 2.16.0 to 2.17.0
--
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: commits-unsubscribe@pulsar.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [pulsar] lhotari merged pull request #13392: [Security] Upgrade to Log4J 2.17.0 to mitigate CVE-2021-45105
Posted by GitBox <gi...@apache.org>.
lhotari merged pull request #13392:
URL: https://github.com/apache/pulsar/pull/13392
--
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: commits-unsubscribe@pulsar.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org