Copilot commented on code in PR #6: URL: https://github.com/apache/logging-site/pull/6#discussion_r3764334328
########## _vulnerabilities.adoc: ########## @@ -32,8 +32,8 @@ We only extend this mathematical notation with set union operator (i.e., `∪`) |Summary |JDBC appender is vulnerable to remote code execution in certain configurations |CVSS 3.x Score & Vector |6.6 MEDIUM (CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:U/C:H/I:H/A:H) |Components affected |`log4j-core` -|Versions affected |`[2.0-beta7, 2.3.2) ∪ [2.4, 2.12.4) ∪ [2.13.0, 2.17.1)` -|Versions fixed |`2.3.2` (for Java 6), `2.12.4` (for Java 7), or `2.17.1` (for Java 8 and later) +|Versions affected |`[2.0-beta7, 2.3.1) ∪ [2.4, 2.12.3) ∪ [2.13.0, 2.17.0)` +|Versions fixed |`2.3.1` (for Java 6), `2.12.3` (for Java 7), or `2.17.0` (for Java 8 and later) Review Comment: These releases do not contain the JDBC-specific fix. In the `rel/2.3.1`, `rel/2.12.3`, and `rel/2.17.0` tags, `DataSourceConnectionSource` still passes the configured name directly to `InitialContext.lookup`; routing it through the restricted `JndiManager` first appears in 2.3.2, 2.12.4, and 2.17.1. Restore those affected ranges and fixed versions. ########## _vulnerabilities.adoc: ########## @@ -45,13 +45,14 @@ This issue is fixed by limiting JNDI data source names to the `java` protocol. [#CVE-2021-44832-mitigation] ==== Mitigation -Upgrade to `2.3.2` (for Java 6), `2.12.4` (for Java 7), or `2.17.1` (for Java 8 and later). +Upgrade to `2.3.1` (for Java 6), `2.12.3` (for Java 7), or `2.17.0` (for Java 8 and later). Review Comment: This mitigation recommends releases that still perform the vulnerable JDBC data-source lookup without protocol filtering. Users need 2.3.2, 2.12.4, or 2.17.1 for CVE-2021-44832; recommending the earlier versions leaves them exposed. -- 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]
