# 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:** 4

<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:45pm UTC](https://forum.inductiveautomation.com/t/log4j-on-linux-windows/54005/4 "2021-12-10T22:45:38Z")

</div>

Yes, should be good to go. The last version of Ignition that used log4j was 7.8, and it used something like log4j version 1.2.x, which isn’t affected by this CVE.

Those who snoop around may find an artifact called `log4j-over-slf4j`, but this just a bridge that let us move from log4j to slf4j/logback without modifying every single file that had used a log4j logger.

---

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