<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>Log4j on lcz's Blog</title><link>https://book.llcczz.org/tags/log4j/</link><description>Recent content in Log4j on lcz's Blog</description><generator>Hugo</generator><language>en-US</language><lastBuildDate>Wed, 15 Dec 2021 00:00:00 +0000</lastBuildDate><atom:link href="https://book.llcczz.org/tags/log4j/index.xml" rel="self" type="application/rss+xml"/><item><title>Log4Shell (CVE-2021-44228): Exploitation, Detection, and Mitigation</title><link>https://book.llcczz.org/posts/log4shell-cve-2021-44228/</link><pubDate>Wed, 15 Dec 2021 00:00:00 +0000</pubDate><guid>https://book.llcczz.org/posts/log4shell-cve-2021-44228/</guid><description>A week after disclosure, what we knew about the Log4j JNDI flaw, why the blast radius was so large, and how to find affected systems.</description></item></channel></rss>