[
https://issues.apache.org/jira/browse/CASSANDRA-17204?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17474974#comment-17474974
]
Brandon Williams commented on CASSANDRA-17204:
----------------------------------------------
Both 4.0 and trunk look good, unsurprisingly. 3.0 and 3.11 needed a test fix
from CASSANDRA-14183 to handle AggregationTest.testLogbackReload, which I've
added, leaving the only failing test to be
DatabaseDescriptorRefTest.testDatabaseDescriptorRef which is failing due to:
{quote}
[junit-timeout] Testsuite:
org.apache.cassandra.config.DatabaseDescriptorRefTest Tests run: 1, Failures:
1, Errors: 0, Skipped: 0, Time elapsed: 0.29 sec
[junit-timeout]
[junit-timeout] ------------- Standard Output ---------------
[junit-timeout] ERROR [main] 2022-01-12 20:58:48,769 SubstituteLogger.java:250
- SLF4J: stderr
[junit-timeout] ------------- ---------------- ---------------
[junit-timeout] ------------- Standard Error -----------------
[junit-timeout]
[junit-timeout]
[junit-timeout] VIOLATION:
org.apache.cassandra.distributed.shared.InstanceClassLoader
[junit-timeout] java.lang.Exception
{quote}
I'm not really sure how this is exposing a dtest class, and I don't see it
being excluded in 4.0. [~mck] do you have any ideas?
> Upgrade to Logback 1.2.8 (security)
> -----------------------------------
>
> Key: CASSANDRA-17204
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17204
> Project: Cassandra
> Issue Type: Improvement
> Components: Dependencies
> Reporter: Jochen Schalanda
> Assignee: Brandon Williams
> Priority: Normal
> Fix For: 3.0.x, 3.11.x, 4.0.x, 4.x
>
>
> Logback 1.2.8 has been released with a fix for a potential vulnerability in
> its JNDI lookup.
> * [http://logback.qos.ch/news.html]
> * [https://jira.qos.ch/browse/LOGBACK-1591]
> {quote}*14th of December, 2021, Release of version 1.2.8*
> We note that the vulnerability mentioned in LOGBACK-1591 requires write
> access to logback's configuration file as a prerequisite.
> * • In response to LOGBACK-1591, we have disabled all JNDI lookup code in
> logback until further notice. This impacts {{ContextJNDISelector}} and
> {{<insertFromJNDI>}} element in configuration files.
> * Also in response to LOGBACK-1591, we have removed all database (JDBC)
> related code in the project with no replacement.
> We note that the vulnerability mentioned in LOGBACK-1591 requires write
> access to logback's configuration file as a prerequisite. A successful RCE
> requires all of the following to be true:
> * write access to logback.xml
> * use of versions < 1.2.8
> * reloading of poisoned configuration data, which implies application restart
> or scan="true" set prior to attack
> Therefore and as an additional precaution, in addition to upgrading to
> version 1.2.8, we also recommend users to set their logback configuration
> files as read-only.
> {quote}
> This is not as bad as CVE-2021-44228 in Log4j <2.15.0 (Log4Shell), but should
> probably be fixed anyway.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
