<?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>Offsec on kimobu</title><link>https://www.kimobu.space/tags/offsec/</link><description>Recent content in Offsec 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/offsec/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><item><title>Hacking a Computer Remotely through a Phone</title><link>https://www.kimobu.space/posts/Hacking-a-Computer-Remotely-through-a-Phone/</link><pubDate>Sat, 01 May 2021 00:00:00 +0000</pubDate><guid>https://www.kimobu.space/posts/Hacking-a-Computer-Remotely-through-a-Phone/</guid><description>&lt;p&gt;In a recent demonstration of cyber and electronic warfare capabilities, I had the opportunity to enable access into a network by exploiting a computer remotely through a cell phone. In this blog post, I’ll document some of the challenges that were encountered and how they were overcome.&lt;/p&gt;
&lt;h1 id="scenario"&gt;Scenario&lt;/h1&gt;
&lt;p&gt;The scenario for this demonstration was: an offensive cyber operations team wants to gain access into a targeted computer network which includes a wireless access point. The targeted network is firewalled and NAT’d, and social engineering techniques such as spear phishing have been unsuccessful. In order to gain access into the network, a human source is used to approach the facility that houses the network (think a residential building) and gains close enough proximity to sense the radio frequency (RF) emissions from the facility.&lt;/p&gt;</description></item></channel></rss>