# How do I Mitigate LOG4J CVE on Elasticsearch 7.4.0?

**URL:** <https://discuss.elastic.co/t/how-do-i-mitigate-log4j-cve-on-elasticsearch-7-4-0/320632>\
**Category:** Elasticsearch\
**Created:** [December 7, 2022, 1:19am UTC](https://discuss.elastic.co/t/how-do-i-mitigate-log4j-cve-on-elasticsearch-7-4-0/320632 "2022-12-07T01:19:09Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![kashahyah](https://avatars.discourse-cdn.com/v4/letter/k/a8b319/32.png) [@kashahyah](https://discuss.elastic.co/u/kashahyah)\
**Post date:** [December 7, 2022, 1:19am UTC](https://discuss.elastic.co/t/how-do-i-mitigate-log4j-cve-on-elasticsearch-7-4-0/320632/1 "2022-12-07T01:19:09Z")

</div>

I have a 3-node ELK cluster in linux. Carbon Black scan picked up some vulnerable jar files. Should I:

1. Upgrade Elasticsearch to 7.16 or later ?
2. Remove the vulnerable JAR files ?
3. Upgrade LOG4J components bundled in Elastic ad-hoc (to LOG4J2?)

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [December 7, 2022, 1:19am UTC](https://discuss.elastic.co/t/how-do-i-mitigate-log4j-cve-on-elasticsearch-7-4-0/320632/2 "2022-12-07T01:19:09Z")

</div>

Elasticsearch 7.4 is [EOL](https://www.elastic.co/support/eol) and no longer supported. Please upgrade ASAP.

(This is an automated response from your friendly Elastic bot. Please report this post if you have any suggestions or concerns :elasticheart: )

---

<div class="post-metadata">

**Author:** ![stephenb](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/stephenb/32/40856_2.png) [@stephenb](https://discuss.elastic.co/u/stephenb)\
**Post date:** [December 7, 2022, 1:36am UTC](https://discuss.elastic.co/t/how-do-i-mitigate-log4j-cve-on-elasticsearch-7-4-0/320632/3 "2022-12-07T01:36:16Z")

</div>

Please Refer to the Official Thread on this.

> [@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):
>
> Subject: Apache Log4j2 Vulnerability - CVE-2021-44228, CVE-2021-45046, CVE-2021-45105, CVE-2021-44832 - ESA-2021-31 ​​Note - We will update this announcement with new details as they emerge from our analysis. Please check back periodically. Update Log Dec 16, 2021 - 04:20 UTC - Update Summary: ECK 1.9 released which automatically adds the JVM option to impacted Elasticsearch clusters managed by ECK. Dec 17, 2021 - 23:50 UTC - Update latest release of APM Java Agent to 1.28.2. Statement of pl…

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [January 4, 2023, 1:36am UTC](https://discuss.elastic.co/t/how-do-i-mitigate-log4j-cve-on-elasticsearch-7-4-0/320632/4 "2023-01-04T01:36:42Z")

</div>

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.
