# Addressing log4j vulnerability for 1.x and 2.x elasticsearch

**URL:** <https://discuss.elastic.co/t/addressing-log4j-vulnerability-for-1-x-and-2-x-elasticsearch/292531>\
**Category:** Elasticsearch\
**Created:** [December 21, 2021, 7:42am UTC](https://discuss.elastic.co/t/addressing-log4j-vulnerability-for-1-x-and-2-x-elasticsearch/292531 "2021-12-21T07:42:32Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\
**Post date:** [December 21, 2021, 8:47am UTC](https://discuss.elastic.co/t/addressing-log4j-vulnerability-for-1-x-and-2-x-elasticsearch/292531/2 "2021-12-21T08:47:07Z")

</div>

[Apache Log4j2 Remote Code Execution (RCE) Vulnerability - CVE-2021-44228 - ESA-2021-31](https://discuss.elastic.co/t/apache-log4j2-remote-code-execution-rce-vulnerability-cve-2021-44228-esa-2021-31/291476) has details for anything \<5.0

But please do be aware that these have all been [EOL](https://www.elastic.co/support/eol) for quite a long time and are no longer supported.

---

_[View the full topic](https://discuss.elastic.co/t/addressing-log4j-vulnerability-for-1-x-and-2-x-elasticsearch/292531)._