<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Unraveling Log4Shell: Analyzing the Impact and Response to the Log4j Vulnerabil · HackerPapers discussions</title><link>https://hackerpaper.kaipfister.de/p/2501.17760/</link><description>Collected HN comments and submissions linking this paper.</description><language>en</language><lastBuildDate>Mon, 02 Nov 2026 11:16:22 GMT</lastBuildDate><atom:link href="https://hackerpaper.kaipfister.de/p/2501.17760/feed.xml" rel="self" type="application/rss+xml" /><item><title>Unraveling Log4Shell: Analyzing the Impact and Response to the Log4j Vulnerabil — mentioned by Nemo_bis</title><link>https://news.ycombinator.com/item?id=50193096</link><guid isPermaLink="false">urn:hackerpapers:mention:2501.17760:50193096</guid><pubDate>Thu, 22 Oct 2026 09:18:20 GMT</pubDate><description>&lt;p&gt;I&amp;#x27;m tempted to agree but at the same time we never (?) had news of confirmed data breaches due to log4shell exploits either, so perhaps people are just good at staying quiet when they get attacked. &amp;gt; Despite the high volume of exploit attempts following the discovery of the Log4Shell vulnerability, reports of major breaches were relatively few. One of the first significant attacks targeted the Belgian Ministry of Defense. Reported on December 12th, just three days after the vulnerability became widely known, the Ministry did not disclose specific details but confirmed the Log4J vulnerability…&lt;/p&gt;&lt;p&gt;&lt;a href="https://hackerpaper.kaipfister.de/p/2501.17760/"&gt;Paper and discussion history&lt;/a&gt;. A mention is not an endorsement.&lt;/p&gt;</description><category>cs.CR</category></item></channel></rss>
