# Elasticsearch&Logstash Log4j Vulnerabilities **URL:** \ **Category:** Logstash\ **Created:** [May 13, 2022, 6:44am UTC](https://discuss.elastic.co/t/elasticsearch-logstash-log4j-vulnerabilities/304640 "2022-05-13T06:44:24Z")\ **Posts on this page:** 7\ **Page:** 1
**Author:** ![kyarali](https://avatars.discourse-cdn.com/v4/letter/k/9de053/32.png) [@kyarali](https://discuss.elastic.co/u/kyarali)\ **Post date:** [May 13, 2022, 6:44am UTC](https://discuss.elastic.co/t/elasticsearch-logstash-log4j-vulnerabilities/304640/1 "2022-05-13T06:44:24Z")
Hello, We have log4j vulnerabilities for Elasticsearch and Logstash in the following paths: Path : /usr/share/Elasticsearch/lib/log4j-core-2.11.1.jar Path : /usr/share/logstash/logstash-core/lib/jars/log4j-core-2.14.0.jar Is there a workaround to fix the vulnerabilities? Otherwise, Is the only solution to upgrade the application version? Logstash and Elasticsearch version: 7.13 Could you help me to solve the problem? Thanks ---
**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:** [May 16, 2022, 12:29am UTC](https://discuss.elastic.co/t/elasticsearch-logstash-log4j-vulnerabilities/304640/2 "2022-05-16T00:29:30Z")
Welcome to our community! 😃 If you are referring to the log4shell vulnerabilities then please see 7-0-0-7-16-0-log4j-cve-2021-44228-cve-2021-45046-remediation/292343 ---
**Author:** ![Badger](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/badger/32/25190_2.png) [@Badger](https://discuss.elastic.co/u/Badger)\ **Post date:** [May 16, 2022, 2:31am UTC](https://discuss.elastic.co/t/elasticsearch-logstash-log4j-vulnerabilities/304640/3 "2022-05-16T02:31:04Z")
> [@warkolm](#): > > 7-0-0-7-16-0-log4j-cve-2021-44228-cve-2021-45046-remediation/292343 I think Mark meant to link to [this](https://discuss.elastic.co/t/logstash-5-0-0-6-8-20-and-7-0-0-7-16-0-log4j-cve-2021-44228-cve-2021-45046-remediation/292343) thread. ---
**Author:** ![kyarali](https://avatars.discourse-cdn.com/v4/letter/k/9de053/32.png) [@kyarali](https://discuss.elastic.co/u/kyarali)\ **Post date:** [May 16, 2022, 3:19am UTC](https://discuss.elastic.co/t/elasticsearch-logstash-log4j-vulnerabilities/304640/4 "2022-05-16T03:19:20Z")
Hello Thanks for your updates. The link you provided for me is about Logstash. Is there a solution for Elasticsearch too? Thanks ---
**Author:** ![Badger](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/badger/32/25190_2.png) [@Badger](https://discuss.elastic.co/u/Badger)\ **Post date:** [May 16, 2022, 3:27am UTC](https://discuss.elastic.co/t/elasticsearch-logstash-log4j-vulnerabilities/304640/5 "2022-05-16T03:27:02Z")
> [@kyarali](#): > > Is there a solution for Elasticsearch too? Of course. The overall elastic view of the vulnerability can be found in [this](https://discuss.elastic.co/t/apache-log4j2-remote-code-execution-rce-vulnerability-cve-2021-44228-esa-2021-31/291476?ultron=log4js-exploit&blade=announcement&hulk=email&mkt_tok=ODEzLU1BTS0zOTIAAAGBU8N1ZUOwzTcRbJCOiByHmeYiopMnarq-QPWBIyhPI3Vvsp6w-4q4PBbTGZ3fZ0sB75cpaUdOddA1k-6-yh3QwAicvJTgafdJWv_-9Cn2GoKLvsmt&utm_source=log4j+hub+blog&utm_medium=embed+link&utm_campaign=log4j_hub_blog&utm_id=log4j&utm_content=log4j2+advisory) blog post. I do not run elasticsearch, but I would start [here](https://discuss.elastic.co/t/apache-log4j2-remote-code-execution-rce-vulnerability-cve-2021-44228-esa-2021-31/291476?ultron=log4js-exploit&blade=announcement&hulk=email&mkt_tok=ODEzLU1BTS0zOTIAAAGBU8N1ZUOwzTcRbJCOiByHmeYiopMnarq-QPWBIyhPI3Vvsp6w-4q4PBbTGZ3fZ0sB75cpaUdOddA1k-6-yh3QwAicvJTgafdJWv_-9Cn2GoKLvsmt&utm_source=log4j+hub+blog&utm_medium=embed+link&utm_campaign=log4j_hub_blog&utm_id=log4j&utm_content=log4j2+advisory#elasticsearch-announcement-esa-2021-31-29). There is a ton of detail about versions and configuration variations. If an upgrade is viable then I would certainly recommend it. ---
**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:** [May 16, 2022, 5:08am UTC](https://discuss.elastic.co/t/elasticsearch-logstash-log4j-vulnerabilities/304640/6 "2022-05-16T05:08:26Z")
Yeah, that was a copy paste error! ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [June 13, 2022, 5:08am UTC](https://discuss.elastic.co/t/elasticsearch-logstash-log4j-vulnerabilities/304640/7 "2022-06-13T05:08:27Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.