<?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>Purpleteam on kimobu</title><link>https://www.kimobu.space/tags/purpleteam/</link><description>Recent content in Purpleteam on kimobu</description><generator>Hugo</generator><language>en-us</language><copyright>Copyright Kimo B</copyright><lastBuildDate>Fri, 10 Dec 2021 00:00:00 +0000</lastBuildDate><atom:link href="https://www.kimobu.space/tags/purpleteam/index.xml" rel="self" type="application/rss+xml"/><item><title>log4j JNDI Exploitation</title><link>https://www.kimobu.space/posts/log4j-JDNI-Exploitation/</link><pubDate>Fri, 10 Dec 2021 00:00:00 +0000</pubDate><guid>https://www.kimobu.space/posts/log4j-JDNI-Exploitation/</guid><description>&lt;h1 id="situation"&gt;Situation&lt;/h1&gt;
&lt;p&gt;A &lt;a href="https://www.lunasec.io/docs/blog/log4j-zero-day/"&gt;remote code execution (RCE) bug was found in log4j&lt;/a&gt;. &lt;a href="https://nvd.nist.gov/vuln/detail/CVE-2021-44228"&gt;CVE 2021-44228&lt;/a&gt; has been assigned to it. The vulnerability lies in how log4j interprets Java Naming and Directory Interface (JNDI) URLs. JNDI lets an application look up a service. An attacker can craft a string that looks like &amp;ldquo;${jndi:proto://host/a}&amp;rdquo; where &lt;code&gt;proto&lt;/code&gt; is ldap or rmi, and log4j will connect to the &lt;code&gt;host&lt;/code&gt; to retrieve &lt;code&gt;a&lt;/code&gt;, which would specify how to process the log entry. However, &lt;code&gt;a&lt;/code&gt; can instead provide Java bytecode that log4j will execute.&lt;/p&gt;</description></item></channel></rss>