<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Home on phakeobj</title><link>/</link><description>Recent content in Home on phakeobj</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Tue, 20 Jul 2021 15:11:14 +0000</lastBuildDate><atom:link href="/index.xml" rel="self" type="application/rss+xml"/><item><title>GoogleCTF 2021 - Compress</title><link>/posts/googlectf-2021-compress/</link><pubDate>Tue, 20 Jul 2021 15:11:14 +0000</pubDate><guid>/posts/googlectf-2021-compress/</guid><description>&lt;blockquote>
&lt;p>My friend developed a custom compression algorithm, but doesn&amp;rsquo;t want
to share the format documentation. He keeps it on his demo server -
why don&amp;rsquo;t you try to steal it?&lt;/p>&lt;/blockquote>
&lt;h2 id="reconnaissance">Reconnaissance&lt;/h2>
&lt;p>The challenge zip file consisted a single binary executable file called &lt;code>compress&lt;/code>. we started off conservatively, by running &lt;code>checksec&lt;/code> to understand what are we dealing with here.&lt;/p>
&lt;pre tabindex="0">&lt;code>phakeobj@localbox:~/ctf/google-2021/compress$checksec compress
[*] &amp;#39;/home/phakeobj/ctf/google-2021/compress/compress&amp;#39;
 Arch: amd64-64-little
 RELRO: Full RELRO
 Stack: Canary found
 NX: NX enabled
 PIE: PIE enabled
 FORTIFY: Enabled
&lt;/code>&lt;/pre>&lt;p>After getting to know the security properties of the executable, we played around with it, in hope to get some understanding of the functionality and where would it make sense to find a bug. We started off by trying out the 3 available options in the menu.&lt;/p></description></item><item><title>Gigacage</title><link>/posts/gigacage/</link><pubDate>Sun, 25 Aug 2019 16:13:30 +0300</pubDate><guid>/posts/gigacage/</guid><description>A WebKit Exploit Mitigation Technique</description></item></channel></rss>