# Elasticsearch&Logstash Log4j Vulnerabilities **URL:** https://discuss.elastic.co/t/elasticsearch-logstash-log4j-vulnerabilities/304640 **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:** 1 **Showing post:** 5
### 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. --- _[View the full topic](https://discuss.elastic.co/t/elasticsearch-logstash-log4j-vulnerabilities/304640)._