# How to detect log4shell in the application logs?

**URL:** <https://discuss.elastic.co/t/how-to-detect-log4shell-in-the-application-logs/291947>\
**Category:** Elasticsearch\
**Created:** [December 15, 2021, 10:40am UTC](https://discuss.elastic.co/t/how-to-detect-log4shell-in-the-application-logs/291947 "2021-12-15T10:40:21Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Kosodrom](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/kosodrom/32/99278_2.png) [@Kosodrom](https://discuss.elastic.co/u/Kosodrom)\
**Post date:** [December 15, 2021, 10:40am UTC](https://discuss.elastic.co/t/how-to-detect-log4shell-in-the-application-logs/291947/1 "2021-12-15T10:40:21Z")

</div>

Hi folks,

I wonder if anyone of you guys have already tried to find possible log4shell exploit based on the logs in your elastic cluster using kibana. I am aware that this can be done using the Elastic Security as described here: [Detecting Exploitation of CVE-2021-44228 (log4j2) with Elastic Security | Elastic Blog](https://www.elastic.co/blog/detecting-log4j2-with-elastic-security)

But for those you must have a auditbeat or endgame infrastructure setup, which I do not have for example.

But I also think there should be a possibility to detect this vulnarability based on the plain applcation logs (for example collected from a kubernetes cluster)?

Any ideas on that how to achive this?

Thanks

---

<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 12, 2022, 10:40am UTC](https://discuss.elastic.co/t/how-to-detect-log4shell-in-the-application-logs/291947/2 "2022-01-12T10:40:48Z")

</div>

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