# Log4J on Linux & Windows

**URL:** <https://forum.inductiveautomation.com/t/log4j-on-linux-windows/54005>\
**Category:** Ignition\
**Created:** [December 10, 2021, 10:39pm UTC](https://forum.inductiveautomation.com/t/log4j-on-linux-windows/54005 "2021-12-10T22:39:52Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![Kevin.Herron](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/kevin.herron/32/7259_2.png) [@Kevin.Herron](https://forum.inductiveautomation.com/u/Kevin.Herron)\
**Post date:** [December 10, 2021, 10:41pm UTC](https://forum.inductiveautomation.com/t/log4j-on-linux-windows/54005/2 "2021-12-10T22:41:19Z")

</div>

Nothing to worry about, we don't use log4j as the logging backend. The log4j.properties files are artifacts from the past and are not used.

> [@Java Zero Day Question](https://forum.inductiveautomation.com/t/java-zero-day-question/54003/2):
>
> I think we’re crafting some kind of official statement, but there’s nothing to worry about. Ignition doesn’t use log4j as its logging backend. Both 7.9 and 8.x versions use a different backend called logback instead. Even old unsupported versions of Ignition that did use log4j used version 1.x, which isn’t affected. For anyone interested this is the CVE: [CVE - CVE-2021-44228](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-44228)

---

_[View the full topic](https://forum.inductiveautomation.com/t/log4j-on-linux-windows/54005)._