| ... |
... |
@@ -2,14 +2,13 @@ |
| 2 |
2 |
|
| 3 |
3 |
The {{formcycle/}} Versions 7.0.0 through 7.0.6 use a version of Log4j that contains the [[CVE-2021-44228>>https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-44228]] vulnerability disclosed on 12/10/2021. |
| 4 |
4 |
The {{formcycle/}} versions 7.0.0 through 7.0.7 use a version of Log4j that contains the [[CVE-2021-45046>>https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-45046]] vulnerability disclosed on 12/14/2021. |
| 5 |
|
-The {{formcycle/}} versions 7.0.0 through 7.0.8 use a version of Log4j that contains the [[CVE-2021-45105>>https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-45105]] vulnerability disclosed on 12/18/2021. |
| 6 |
6 |
|
| 7 |
|
-Currently, we are not aware of any scenario where these vulnerabilities in {{formcycle/}} can be exploited. **We still recommend to upgrade to {{formcycle/}} [[Version 7.0.9>>doc:Blog.WebHome]], which uses a new version of Log4j that no longer contains these vulnerabilities.** |
|
6 |
+Currently, we are not aware of any scenario where these vulnerabilities in {{formcycle/}} can be exploited. **We still recommend to upgrade to {{formcycle/}} [[Version 7.0.8>>doc:Blog.FORMCYCLE 708.WebHome]], which uses a new version of Log4j that no longer contains these vulnerabilities.** |
| 8 |
8 |
{{/info}} |
| 9 |
9 |
|
| 10 |
10 |
{{info}} |
| 11 |
11 |
|
| 12 |
|
-For installations where upgrading to the latest {{formcycle/}} version is not possible, we recommend implementing the [[vendor>>https://logging.apache.org/log4j/2.x/security.html]] recommended mitigation for __CVE-2021-44228__. For the Log4j version used by the potentially affected {{formcycle/}} versions this means setting the {{code language="none"}}-Dlog4j2.formatMsgNoLookups=true{{/code}} option in the Java options for the servlet container used. |
|
11 |
+For installations where upgrading to the latest {{formcycle/}} version is not possible, we recommend implementing the [[vendor>>https://logging.apache.org/log4j/2.x/security.html]] recommended mitigation for __CVE-2021-44228__. For the Log4j version used by the potentially affected {{formcycle/}} versions this means setting the {{code language="none"}}-Dlog4j2.formatMsgNoLookups=true{{/code}} option in the Java options for the servlet container which is used to run {{formcycle/}}. |
| 13 |
13 |
|
| 14 |
14 |
For example, for an Apache Tomcat running on Windows, this can be done in //Tomcat Monitor// at the following location: |
| 15 |
15 |
[[image:tomcat_log4j_settings.png||width="350"]] |
| ... |
... |
@@ -19,7 +19,7 @@ |
| 19 |
19 |
|
| 20 |
20 |
When using servlet containers other than Apache Tomcat, please consult the documentation for that servlet container for the location at which this parameter can be passed. |
| 21 |
21 |
|
| 22 |
|
-If an upgrade to the latest {{formcycle/}} version is not possible, mitigation of __CVE-2021-45046__ & __CVE-2021-45105__ is only necessary if logpatterns containing [[affected configurations>>https://logging.apache.org/log4j/2.x/security.html]] have been manually configured. In this case, the corresponding patterns should be removed. |
|
21 |
+If an upgrade to the latest {{formcycle/}} version is not possible, mitigation of __CVE-2021-45046__ is only necessary if logpatterns containing [[affected configurations>>https://logging.apache.org/log4j/2.x/security.html]] have been manually configured. In this case, the corresponding patterns should be removed. |
| 23 |
23 |
{{/info}} |
| 24 |
24 |
|
| 25 |
25 |
{{content/}} |