# Delete JndiLookup.class

**URL:** <https://discuss.elastic.co/t/delete-jndilookup-class/291507>\
**Category:** Logstash\
**Tags:** elastic-stack-security\
**Created:** [December 11, 2021, 1:23pm UTC](https://discuss.elastic.co/t/delete-jndilookup-class/291507 "2021-12-11T13:23:14Z")\
**Posts on this page:** 1\
**Showing post:** 6

<div class="post-metadata">

**Author:** ![Kami](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/kami/32/98757_2.png) [@Kami](https://discuss.elastic.co/u/Kami)\
**Post date:** [December 12, 2021, 12:10pm UTC](https://discuss.elastic.co/t/delete-jndilookup-class/291507/6 "2021-12-12T12:10:22Z")

</div>

Here is a workaround / temporary mitigation I'm using from another thread which utilizes a Dockerfile - [Zero-day-exploit in log4j2 which is part of elasticsearch - #35 by Kami](https://discuss.elastic.co/t/zero-day-exploit-in-log4j2-which-is-part-of-elasticsearch/291439/35).

Keep in mind that glob expansion approach didn't work for me so I use full absolute path - make sure the full path is the same in your case (it may be different with older logstash versions, but I didn't dig in).

---

_[View the full topic](https://discuss.elastic.co/t/delete-jndilookup-class/291507)._