| ... |
... |
@@ -1,5 +1,5 @@ |
| 1 |
1 |
{{info}} |
| 2 |
|
-The {{formcycle/}} versions 7.0.0 to 7.0.6 use a version of Log4j that contains the vulnerability disclosed on 12/10/2021. Currently, we are not aware of any scenario where this vulnerability can be exploited in {{formcycle/}}. In the meantime, we still recommend implementing the [[vendor>>https://logging.apache.org/log4j/2.x/security.html]] recommended mitigation for the Log4j version used and setting the {{code language="none"}}-Dlog4j2.formatMsgNoLookups=true{{/code}} option in the Java options for the servlet container used. |
|
2 |
+The {{formcycle/}} versions 7.0.0 to 7.0.6 use a version of Log4j that contains the vulnerability disclosed on 12/10/2021. Currently, we are not aware of any scenario where this vulnerability can be exploited in {{formcycle/}}. In the meantime, we still recommend implementing the [[vendor>>https://logging.apache.org/log4j/2.x/security.html]] recommended mitigation for the Log4j version used by {{formcycle/}} and therefore setting the {{code language="none"}}-Dlog4j2.formatMsgNoLookups=true{{/code}} option in the Java options for the servlet container used. |
| 3 |
3 |
|
| 4 |
4 |
For example, for an Apache Tomcat running on Windows, this can be done in //Tomcat Monitor// at the following location: |
| 5 |
5 |
[[image:tomcat_log4j_settings.png||width="350"]] |