Impact
Apache Log4j2 versions 2.0-alpha1 through 2.16.0, excluding 2.12.3, 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.
METViewer uses Log4j2 library for logging.
Patches
The problem has been patched by upgrading log4j library to the latest version 2.17.0. Users should upgrade to METviewer v4.0.2.
References
https://metviewer.readthedocs.io/en/latest/Users_Guide/overview.html#metviewer-release-notes
https://logging.apache.org/log4j/2.x/security.html
For more information
If you have any questions or comments about this advisory:
Impact
Apache Log4j2 versions 2.0-alpha1 through 2.16.0, excluding 2.12.3, 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.
METViewer uses Log4j2 library for logging.
Patches
The problem has been patched by upgrading log4j library to the latest version 2.17.0. Users should upgrade to METviewer v4.0.2.
References
https://metviewer.readthedocs.io/en/latest/Users_Guide/overview.html#metviewer-release-notes
https://logging.apache.org/log4j/2.x/security.html
For more information
If you have any questions or comments about this advisory: