This issue may lead to remote code execution (RCE) via use of JNDI.
- Vendor: Apache Software Foundation
- Product: Apache Log4j
- <=2.14.1: affects 2.14.1 and prior versions
- Product: Apache Log4j
Fix: log4j 2.15.0

To list all JAR files on your system containing the vulnerable class file (including fat JARs), you can use:
for f in $(find . -name '*.jar' 2>/dev/null); do echo "Checking $f…"; unzip -l "$f" | grep -F org/apache/logging/log4j/core/lookup/JndiLookup.class; done
Additional details here:
Pingback: Links 13/12/2021: Kdenlive 21.12, digiKam 7.4 | Techrights