---
title: "EDM115 Telegram blog"
canonical_url: "https://edm115.dev/blog/telegram/2021/12/21/log4j-vulnerability"
last_updated: "2026-08-30T03:11:33.543Z"
meta:
  description: "Find all infos about EDM115, my projects, blog posts, ..."
  "og:description": "[log4j-vulnerability] Okay, so y'all have probably heard about this 10/10 critical security breach 💀 Here some sources about it : • Run a vulnerable log4j instance (at your own risks !) • Cloudflare b..."
  "og:title": "EDM115 Telegram blog"
  "twitter:title": "EDM115 Telegram blog"
---

Home](https://edm115.dev/)

](https://edm115.dev/projects)](https://edm115.dev/blog)](https://edm115.dev/codex)](https://edm115.dev/unzip)

![log4j-vulnerability](https://edm115.dev/img/blog/2021/12-21-log4j-vulnerability.webp)  
Okay, so y’all have probably heard about this 10/10 critical security breach 💀  
  

Here some sources about it :  
  

• [Run a vulnerable log4j instance (at your own risks !)](https://github.com/christophetd/log4shell-vulnerable-app)  
 • [Cloudflare blog article for a better understanding](https://blog.cloudflare.com/inside-the-log4j2-vulnerability-cve-2021-44228/) (complete, as usual 😌)  
 • [Another good article](https://www.lunasec.io/docs/blog/log4j-zero-day/)  
 • Some lists of IP’s catched for using the breach [\[1\]](https://gist.github.com/blotus/f87ed46718bfdc634c9081110d243166/raw/148e8e3b8e24fb248f281d6c64f7484d06f540f7/log4j_exploitation_attempts_crowdsec.csv) [\[2\]](https://gist.github.com/gnremy/c546c7911d5f876f263309d7161a7217/raw/1b9dc2ce127681bae5fc02c3f5f77a3ff9f57ea6/CVE-2021-44228_IPs.csv) (regularly updated)  
 • [A vaccine for it](https://github.com/Cybereason/Logout4Shell)  
 • [fail2ban filter rule](https://jay.gooby.org/2021/12/13/a-fail2ban-filter-for-the-log4j-cve-2021-44228) (blocks anyone who wants to use the exploit)  
 • [Full list of infos/ressources about it ❗](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-44228)  
 • [Another complete list of ressources ❗](https://gist.github.com/SwitHak/b66db3a06c2955a9cb71a8718970c592/raw/6552a01148d5dbd8c9c44dabf9767032637b3540/20211210-TLP-WHITE_LOG4J.md)  
 • [Tool for finding if the breach is present on your organization \[tool made by the CISA 😳\]](https://github.com/cisagov/log4j-scanner)  
 • [Unusual : the exploit can be used through iPhones and Tesla 😂🥲](https://www.theverge.com/2021/12/13/22832552/iphone-tesla-sms-log4shell-log4j-exploit-researchers-test)  
 • [A variant of the breach](https://checkmarx.com/blog/cve-2021-44832-apache-log4j-2-17-0-arbitrary-code-execution-via-jdbcappender-datasource-element/)  
 • [6 months after, this flaw is still actively used](https://www.bleepingcomputer.com/news/security/cisa-log4shell-exploits-still-being-used-to-hack-vmware-servers/)  
  

The solution is obviously to update Apache 🤓  
 Good luck if you’re facing this