# Regarding log4j vulnerability

**URL:** <https://discuss.elastic.co/t/regarding-log4j-vulnerability/291749>\
**Category:** Elasticsearch\
**Tags:** docker\
**Created:** [December 14, 2021, 6:33am UTC](https://discuss.elastic.co/t/regarding-log4j-vulnerability/291749 "2021-12-14T06:33:37Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![mohammed.sabil](https://avatars.discourse-cdn.com/v4/letter/m/f17d59/32.png) [@mohammed.sabil](https://discuss.elastic.co/u/mohammed.sabil)\
**Post date:** [December 14, 2021, 6:33am UTC](https://discuss.elastic.co/t/regarding-log4j-vulnerability/291749/1 "2021-12-14T06:33:37Z")

</div>

Hello Team,

I am using/running ELK 7.13 version on my environment using docker compose along with Filebeat 7.14 and have enabled xpack security option.

I have restarted all three containers using docker compose and completed successfully.

I just wanted to know do I need to do anything to remediate the log4j vulnerability for my ELK stack.

Kindly suggest.

Thank you.  
Sabil.

---

<div class="post-metadata">

**Author:** ![FALEN](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/falen/32/82754_2.png) [@FALEN](https://discuss.elastic.co/u/FALEN)\
**Post date:** [December 14, 2021, 8:03am UTC](https://discuss.elastic.co/t/regarding-log4j-vulnerability/291749/2 "2021-12-14T08:03:06Z")

</div>

For proper fix, you need to update

> **[Elasticsearch version 7.16.1 | Elasticsearch Guide \[7.16\] | Elastic](https://www.elastic.co/guide/en/elasticsearch/reference/7.16/release-notes-7.16.1.html)**

- Disable JNDI lookups via the `log4j2.formatMsgNoLookups` system property [#81622](https://github.com/elastic/elasticsearch/pull/81622)
- Patch log4j jar to remove the `JndiLookup` class from the classpath [#81629](https://github.com/elastic/elasticsearch/pull/81629)

---

<div class="post-metadata">

**Author:** ![mohammed.sabil](https://avatars.discourse-cdn.com/v4/letter/m/f17d59/32.png) [@mohammed.sabil](https://discuss.elastic.co/u/mohammed.sabil)\
**Post date:** [December 14, 2021, 10:47am UTC](https://discuss.elastic.co/t/regarding-log4j-vulnerability/291749/3 "2021-12-14T10:47:55Z")

</div>

Hello @FALEN ,

Thank you for your reply. Let me update my ELK stack to 7.16.1 version.

Will update once done.

Regards,  
Sabil.

---

<div class="post-metadata">

**Author:** ![mohammed.sabil](https://avatars.discourse-cdn.com/v4/letter/m/f17d59/32.png) [@mohammed.sabil](https://discuss.elastic.co/u/mohammed.sabil)\
**Post date:** [January 3, 2022, 9:47am UTC](https://discuss.elastic.co/t/regarding-log4j-vulnerability/291749/4 "2022-01-03T09:47:44Z")

</div>

Hello Team,

May I know do we have updates on log4j 2.17.1 for elk stack?

Thank you.

---

<div class="post-metadata">

**Author:** ![Vashiru](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/vashiru/32/99623_2.png) [@Vashiru](https://discuss.elastic.co/u/Vashiru)\
**Post date:** [January 5, 2022, 5:30pm UTC](https://discuss.elastic.co/t/regarding-log4j-vulnerability/291749/5 "2022-01-05T17:30:12Z")

</div>

Logstash v2.17.1 is mitigate against CVE-2021-44832 from the 28th of December. I've asked about it here: [Log4j CVE-2021-44832 (released 28th dec) - is ES vulnerable?](https://discuss.elastic.co/t/log4j-cve-2021-44832-released-28th-dec-is-es-vulnerable/293076) but thus far no conclusive answer.

I don't know about Logstash, but I do know no update containing log4j 2.17.1 has been released yet for Elasticsearch (it would be released in 7.16.3, but the latest as of writing is 7.16.2).

---

<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:** [February 2, 2022, 5:31pm UTC](https://discuss.elastic.co/t/regarding-log4j-vulnerability/291749/6 "2022-02-02T17:31:12Z")

</div>

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