Apache Log4j2 versions 2.0-alpha1 through 2.16.0 (excluding 2.12.3 and 2.3.1) did not protect from uncontrolled recursion from self-referential lookups. This allows an attacker with control over Thread Context Map data to cause a denial of service when a crafted string is interpreted. This issue was fixed in Log4j 2.17.0, 2.12.3, and 2.3.1.
https://thehackernews.com/2023/12/behind-scenes-of-matveevs-ransomware.html
https://www.tenable.com/blog/oracle-january-2022-critical-patch-update-addresses-266-cves
https://www.zerodayinitiative.com/advisories/ZDI-21-1541/
https://www.oracle.com/security-alerts/cpujul2022.html
https://www.oracle.com/security-alerts/cpujan2022.html
https://www.oracle.com/security-alerts/cpuapr2022.html
https://www.kb.cert.org/vuls/id/930724
https://www.debian.org/security/2021/dsa-5024
https://tools.cisco.com/security/center/content/CiscoSecurityAdvisory/cisco-sa-apache-log4j-qRuKNEbd
https://security.netapp.com/advisory/ntap-20211218-0001/
https://psirt.global.sonicwall.com/vuln-detail/SNWLID-2021-0032
https://logging.apache.org/log4j/2.x/security.html
https://cert-portal.siemens.com/productcert/pdf/ssa-501673.pdf
https://cert-portal.siemens.com/productcert/pdf/ssa-479842.pdf