ppkarwasz commented on code in PR #6:
URL: https://github.com/apache/logging-site/pull/6#discussion_r3764415957


##########
_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:
   This is hard to argue since CVE-2021-44832 does not violate any property in 
our threat model, but if we define allowing the operator to delegate 
configuration of a JDBC appender to a potentially malicious LDAP server, then I 
guess you are right and we should restore the higher 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:
   As above.



-- 
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]

Reply via email to