| F-Secure Policy Manager | Ja | Workaround vorhanden https://status.f-secure.com/ | Die Lücke würde bei Kunden mit MSX AntiVirus bereits am Wochenende gefixt. |
| Quest KACE SMA | Nein | | Kunden mit MSI Patchmanagement nicht daher nicht betroffen |
| CalvaDrive / Business File Manager | Nein | | |
| SEPPmail | Nein | | Kunden mit MSX E-Mailverschlüsselung nicht betroffen |
Dell
– EMC Unity
– Unisphere Central
– Wyse Management Suite | Ja | Noch kein Workaround vorhanden https://www.dell.com/support/kbdoc/en-us/000194414/dell-response-to-apache-log4j-remote-code-execution-vulnerability | |
| VMware vCenter | Ja | Workaround vorhanden https://kb.vmware.com/s/article/87081?lang=en_US | |
| PaperCut | Ja Ab Version 21 | Workaround vorhanden https://www.papercut.com/support/known-issues/#ng | |
| Splunk | Ja Version 8.1 und 8.2 wenn DFS aktiv ist | Workaround vorhanden https://www.splunk.com/en_us/blog/bulletins/splunk-security-advisory-for-apache-log4j-cve-2021-44228.html | |
| PRTG | Nein | https://kb.paessler.com/en/topic/90213-is-prtg-affected-by-cve-2021-44228 | Aussage von Hersteller fehlt noch |
| StarFace | Nein | https://support.starface.de/forum/showthread.php?9681-Sicherheitsl%FCcke-log4shell&highlight=log4j | Aussage von Hersteller fehlt noch |
| Sonicwall Firewalls, SMA | Nein | | |
| Sonicwall WAF | Ja | https://www.sonicwall.com/support/notices/security-notice-apache-log4j-remote-code-execution-rce-log4shell-vulnerability-cve-2021-44228-cve-2021-45046-cve-2021-45105/211214102517010/ | |
| Sonicwall Email Security | Ja | Noch kein Workaround https://psirt.global.sonicwall.com/vuln-detail/SNWLID-2021-0032 | |
| Sophos Firewalls | Nein | https://www.sophos.com/en-us/security-advisories/sophos-sa-20211210-log4j-rce | |
Citrix Gateway
Citrix StoreFront Citrix Director | Nein | https://support.citrix.com/article/CTX335705 | |
| APC PCNS | Ja | https://www.se.com/ww/en/download/document/SESB-2021-347-01/ | |
| Lancom Router Lancom Firewalls | Nein | https://www.lancom-systems.de/service-support/soforthilfe/allgemeine-sicherheitshinweise/ | |
| Lancom ePaper | Nein | https://www.lancom-systems.de/service-support/soforthilfe/allgemeine-sicherheitshinweise/ | |
| Unitrends Enterprise Backup Unitrends Office 365 Spanning | Nein | https://helpdesk.kaseya.com/hc/en-gb/articles/4413449967377-Log4j2-Vulnerability-Assessment | |
| Confluence/Jira | Ja | Workaround vorhanden https://confluence.atlassian.com/kb/faq-for-cve-2021-44228-1103069406.html | Aber nur bei einer abweichenden Konfiguration |
| Accantum | Nein | | |
| PasswordSafe | Nein | | |
| Synology | Nein | https://www.synology.com/en-global/security/advisory | |
| FTAPI | Ja | https://www.ftapi.com/blog/kritische-sicherheitslucke-in-log4j-ftapi-reagiert/ | |
| QNAP | Nein | https://www.qnap.com/en-uk/security-advisory/qsa-21-58 | |
| Igel UMS | Ja | Workaround vorhanden
https://kb.igel.com/securitysafety/en/isn-2021-11-ums-log4j-vulnerability-54086712.html | |
| DATEV | Ja | https://www.datev-community.de/t5/Freie-Themen/Log4-J-Schwachstelle/m-p/258272#_=_ | |
| Acronis Cyber Backup | Ja | Workaround vorhanden
https://security-advisory.acronis.com/advisories/SEC-3859 | |
| beA | Ja | Workaround vorhanden
https://portal.beasupport.de/external/c/aktuelles | |
| Blancco | Ja | Workaround vorhanden
https://support.blancco.com/display/NEWS/2021/12/12/CVE-2021-44228+-+Critical+vulnerability+in+Apache+Log4j+library | |
| Infor | Ja | Workaround vorhanden
https://support.infor.com/espublic/EN/AnswerLinkDotNet/SoHo/solutions/SoHoViewSolutionC.aspx?SolutionID=2229037 | |
| Teamviewer | Nein | https://www.teamviewer.com/en/trust-center/security-bulletins/hotfix-log4j2-issue/ | |
| Altaro | Nein | | |
| 7Zip | Nein | https://sourceforge.net/p/sevenzip/discussion/45797/thread/b977bbd4d1/ | |
