# Apache Log4J Vulnerability - CVE-2021-44228

**URL:** <https://forum.inductiveautomation.com/t/apache-log4j-vulnerability-cve-2021-44228/54050>\
**Category:** Ignition\
**Tags:** ignition79, ignition80, ignition81\
**Created:** [December 13, 2021, 2:50pm UTC](https://forum.inductiveautomation.com/t/apache-log4j-vulnerability-cve-2021-44228/54050 "2021-12-13T14:50:51Z")\
**Posts on this page:** 1\
**Showing post:** 6

<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 14, 2021, 2:48am UTC](https://forum.inductiveautomation.com/t/apache-log4j-vulnerability-cve-2021-44228/54050/6 "2021-12-14T02:48:39Z")

</div>

> [@Log4j vulnerability and third-party modules](https://forum.inductiveautomation.com/t/log4j-vulnerability-and-third-party-modules/54025/2):
>
> We can talk to our strategic partners, but all the modules you listed are ours and they do not include log4j. The whole idea of a 3rd party bringing log4j as a dependency is very unusual - the logging backend is provided by the Ignition platform and anybody who knows what they are doing would log using the SLF4J logging API and not introduce a parallel logging backend, which would result in an additional set of logs/files being generated.

---

_[View the full topic](https://forum.inductiveautomation.com/t/apache-log4j-vulnerability-cve-2021-44228/54050)._