<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Ojas Gupta Blog</title><link>https://gc0rp.github.io/</link><description>Recent content on Ojas Gupta Blog</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Fri, 08 May 2026 15:00:00 +1000</lastBuildDate><atom:link href="https://gc0rp.github.io/index.xml" rel="self" type="application/rss+xml"/><item><title>0CTF - BabyHeap</title><link>https://gc0rp.github.io/posts/0ctfbabyheap/</link><pubDate>Fri, 08 May 2026 15:00:00 +1000</pubDate><guid>https://gc0rp.github.io/posts/0ctfbabyheap/</guid><description>&lt;h2 id="introduction">Introduction&lt;/h2>
&lt;p>I will demonstrate how the fast-bin attack works. The 0ctf&amp;rsquo;s babyheap challenge will be used to showcase the attack. This CTF is using the glibc-2.23 library.&lt;/p>
&lt;p>For both of the files (0ctfbabyheap and libc-2.23.so) we will be dealing with PIE &amp;amp; NX. NX can stop us from executing shellcode in certain memory frames. PIE enabled will allow ASLR to randomize the base addresses. This means we will need an infoleak in order to get a shell.&lt;/p></description></item><item><title>HITCON’14 Stkof</title><link>https://gc0rp.github.io/posts/hitcon-14-stkof/</link><pubDate>Thu, 19 Mar 2026 15:27:13 +1000</pubDate><guid>https://gc0rp.github.io/posts/hitcon-14-stkof/</guid><description>&lt;h2 id="introduction">Introduction&lt;/h2>
&lt;p>This writeup will walkthrough the solution for HITCON 14&amp;rsquo;s Stkof problem. I demonstrate the solution by using the unsafe unlink technique and trigger the shell with onegadget.&lt;/p>
&lt;h2 id="the-unlink-process">The unlink process&lt;/h2>
&lt;p>The unsafe unlink is a heap exploitation technique that allows us to unlink a heap chunk and achieve an arbitrary write. An arbitrary write will then be used to modify function hooks which are used to call functions. In our post we will target the &lt;code>malloc&lt;/code> call to trigger the shell then modify the address &lt;code>strlen&lt;/code> to &lt;code>puts&lt;/code> for an info leak.&lt;/p></description></item><item><title>Objects in Disguise 🥷🏽: Unmasking V8’s Secret Operations Behind the Scenes</title><link>https://gc0rp.github.io/posts/objects-in-disguise/</link><pubDate>Thu, 19 Jun 2025 15:00:00 +1000</pubDate><guid>https://gc0rp.github.io/posts/objects-in-disguise/</guid><description>&lt;h1 id="introduction">Introduction&lt;/h1>
&lt;p>In this article we will explore some ways V8 optimizes your Javascript code. I will share some of the knowledge I have learnt over the past few weeks reading blogs.&lt;/p>
&lt;p>Bonus Points!! if you&amp;rsquo;re interested in using this knowledge to exploit web browsers (for educational purposes, obviously).&lt;/p>
&lt;h1 id="the-purpose-of-v8">The purpose of V8&lt;/h1>
&lt;p>As web applications become the new normal for many people around the globe. Google set out on a journey to make web browsers run applications as smoothly desktop applications. As a result of this, V8 was born.&lt;/p></description></item><item><title>IOT Secure CTF [Ret2Systems]</title><link>https://gc0rp.github.io/posts/ret2-mission1/</link><pubDate>Sun, 15 Jun 2025 15:27:13 +1000</pubDate><guid>https://gc0rp.github.io/posts/ret2-mission1/</guid><description>&lt;h2 id="problem-description">Problem Description&lt;/h2>
&lt;p>Even as modern desktops and servers gain more mitigations and protections, somehow Internet Of Things devices lag way behind.&lt;/p>
&lt;p>Yet people have started introducing countless &amp;ldquo;smart&amp;rdquo; devices into their home and onto their network.&lt;/p>
&lt;p>It is time to hack into these toasters, refrigerators, thermostats, and lightbulbs.&lt;/p>
&lt;h2 id="initial-analysis-of-the-challenge">Initial Analysis of the Challenge&lt;/h2>
&lt;p>I noticed some interesting function names when the file was loaded into Binary Ninja that I thought I may end up using later.&lt;/p></description></item></channel></rss>