<?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 Swarnim Bandekar on Medium]]></title>
        <description><![CDATA[Stories by Swarnim Bandekar on Medium]]></description>
        <link>https://medium.com/@swarnimbandekar?source=rss-242059e90f66------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*tYlpUgXKa2Uzqja_qIOGqA.jpeg</url>
            <title>Stories by Swarnim Bandekar on Medium</title>
            <link>https://medium.com/@swarnimbandekar?source=rss-242059e90f66------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 18 Nov 2026 21:08:20 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@swarnimbandekar/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[ASCP Review: My APIsec University Exam Experience]]></title>
            <link>https://medium.com/@swarnimbandekar/ascp-51ed4fea2cf8?source=rss-242059e90f66------2</link>
            <guid isPermaLink="false">https://medium.com/p/51ed4fea2cf8</guid>
            <category><![CDATA[ascp-review]]></category>
            <category><![CDATA[bug-bounty]]></category>
            <category><![CDATA[cybersecurity-certificate]]></category>
            <category><![CDATA[infosec]]></category>
            <dc:creator><![CDATA[Swarnim Bandekar]]></dc:creator>
            <pubDate>Mon, 01 Jun 2026 17:12:20 GMT</pubDate>
            <atom:updated>2026-06-01T17:12:20.079Z</atom:updated>
            <content:encoded><![CDATA[<blockquote>ASCP Review: My Journey with the <strong>ASCP API Security Certified Professional</strong> Exam</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/997/1*nB4Fm7lXmowv0LRQtxP0Ww.png" /></figure><p>If you are looking for an honest <strong>ASCP review</strong>, an <strong>ASCP APIsec</strong> experience, or a practical breakdown of the <strong>ASCP API Security Certified Professional</strong> exam by APIsec University, this is my firsthand account.</p><p>When I first heard about the <a href="https://www.credly.com/badges/34e98206-38b0-4196-8894-2583d115a0fc"><strong>ASCP</strong> </a>by APIsec University, I honestly thought it would just be another certification exam. Maybe some questions, maybe some theory, maybe a few tricky concepts around APIs.</p><p>I was completely wrong.</p><blockquote>This exam was pure practical core.</blockquote><p>You are basically thrown into an environment and told to figure things out yourself. No step by step guidance. No MCQs. No hints holding your hand.</p><p>Just APIs, endpoints, authentication flows, weird behaviors, and flags hidden behind vulnerabilities.</p><p>To pass the exam, you need to capture <strong>6 out of 8 flags</strong> within <strong>12 hours</strong>.</p><p>And that is where the real story starts.</p><h4><strong>The Start</strong></h4><p>I started the exam at around <strong>6 PM</strong> in the evening.</p><p>The first thing I did was reconnaissance and enumeration. Looking around the application, understanding the API structure, checking endpoints, playing with requests, and trying to understand how everything worked together.</p><p>The first hour actually went pretty well.</p><p>I got <strong>2 flags</strong> quickly and that gave me a huge confidence boost.</p><p>Maybe <strong>too much confidence.</strong></p><p>I have played a lot of CTFs in the past, so somewhere in my mind I assumed this would be another normal CTF style challenge.</p><p>That overconfidence became my biggest mistake during the exam.</p><h4><strong>The Mid Game</strong></h4><p>By around <strong>9 PM</strong> I had found <strong>3 more flags.</strong></p><p>That made it <strong>5 flags total</strong>.<br>Just <strong>one more flag</strong> needed to pass.<br>At that point I thought:</p><blockquote>“Yeah, this is done. I’ll get the next one soon.”</blockquote><p>But that “soon” never came.</p><p>I kept trying different things.</p><p>Different attack paths. Different requests. Different parameters. Looking at responses again and again. Replaying requests. Modifying tokens. Testing authorization issues. Trying random ideas that made sense in my head.</p><p>Nothing worked.</p><p>Hours passed.</p><p>I think exhaustion slowly started taking over without me even realizing it. I was so focused on getting that final flag that I completely ignored the fact that my brain was basically shutting down.</p><h4><strong>The Unexpected Part</strong></h4><p>And then something funny happened.</p><p>I accidentally fell asleep.</p><p>Literally with my laptop open.</p><p>I don’t even remember when exactly I slept. I think it was around <strong>midnight</strong>.</p><p>The next thing I remember is waking up at around <strong>4:30 in the morning</strong> with my laptop still in front of me.</p><ul><li>5 flags submitted</li><li>1 flag left</li><li>1 hour remaining</li></ul><p>And the weirdest part is that while sleeping, I actually dreamt of a method I could try.</p><p>Sounds fake, but it genuinely happened.</p><p>I woke up, tried that exact approach immediately, and somehow it actually worked.</p><h4><strong>Boom.</strong></h4><p><strong>6th flag captured.</strong></p><p>I passed the exam with less than an hour remaining.</p><p>The relief at that moment was insane.</p><p><strong>What This Exam Taught Me</strong></p><p>I was really happy that I passed, but at the same time I also had this regret in my mind.</p><p>Maybe if I had taken proper breaks earlier instead of forcing myself continuously, I could have stayed fresh enough to get the remaining 2 flags as well.</p><p>That exam genuinely taught me something important.</p><blockquote>Breaks are necessary.</blockquote><p>Your brain needs rest, especially during long practical exams. Sometimes stepping away for a bit helps more than staring at the same endpoint for 3 straight hours.</p><h4><strong>About the Certification</strong></h4><p>The ASCP exam itself costs around <strong>**$450**</strong>, but I actually got the voucher through a CTF event, so I didn’t personally buy it.</p><p>I had also completed the <strong>**CASA**</strong> and <strong>**ACP**</strong> certifications before this, which were mostly MCQ based.</p><p>Honestly, I was a little disappointed by those because they felt more theoretical than practical.</p><p>But ASCP was completely different.</p><p>This one felt like:</p><ul><li>Actual hacking</li><li>Actual enumeration</li><li>Actual exploitation</li><li>Actual problem solving</li><li>Not question answering.</li><li>Not memorization.</li><li>Not theory dumping.</li></ul><p>You actually have to think, explore, break things, and chain ideas together.</p><p>That made the experience genuinely enjoyable.</p><h4><strong>Tools That Helped Me</strong></h4><p>At first I thought <strong>Burp Suite</strong> alone would be enough.</p><p>But no.</p><p><strong>Postman</strong> became surprisingly useful too.</p><p>Using both together actually helped a lot.</p><ul><li>Burp for interception and manipulation</li><li>Postman for cleaner API testing workflows</li></ul><h4><strong>Resources I Recommend</strong></h4><p><strong>PortSwigger Academy</strong></p><p>Probably one of the best places to learn web and API security concepts practically.<br><a href="https://portswigger.net/web-security">https://portswigger.net/web-security</a></p><p><strong>APIsec University API Penetration Testing Course</strong></p><p>This course is free and genuinely useful for understanding API testing methodologies.<br><a href="https://www.apisecuniversity.com/courses/api-penetration-testing">https://www.apisecuniversity.com/courses/api-penetration-testing</a></p><p><strong>crAPI</strong></p><p>A vulnerable API lab where you can practice real world API vulnerabilities.<br><a href="https://crapi.apisec.ai/">https://crapi.apisec.ai/</a></p><p><strong>One Request to Guide Them All</strong></p><p>Another really fun resource for API learning and practice.<br><a href="https://one-request.apisecuniversity.com/">https://one-request.apisecuniversity.com/</a></p><h4><strong>Final Thoughts</strong></h4><p>Honestly, no single resource is ever enough.</p><p>The more you practice, the better you get.</p><p>That’s really it.</p><p>I did the ASCP mostly out of curiosity rather than just for a certification badge. And I’m glad I did, because it ended up being one of the most enjoyable practical certification experiences I’ve had so far.</p><p>you can find the same on my folio @ <a href="https://swarnimbandekar.in/blog/ascp/">https://swarnimbandekar.in/blog/ascp/</a></p><h4>Feel Free To Reach Out</h4><p><a href="https://www.linkedin.com/in/swarnimbandekar/">https://www.linkedin.com/in/swarnimbandekar/</a><br><a href="https://x.com/swarnimsb">https://x.com/swarnimsb</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=51ed4fea2cf8" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[easy $100 | bypass 403 to 200 ok]]></title>
            <link>https://infosecwriteups.com/easy-100-bypass-403-to-200-ok-b6bc126e2f4b?source=rss-242059e90f66------2</link>
            <guid isPermaLink="false">https://medium.com/p/b6bc126e2f4b</guid>
            <category><![CDATA[bug-bounty-tips]]></category>
            <category><![CDATA[bug-bounty]]></category>
            <category><![CDATA[hacking]]></category>
            <category><![CDATA[infosec]]></category>
            <dc:creator><![CDATA[Swarnim Bandekar]]></dc:creator>
            <pubDate>Sun, 25 Jan 2026 14:24:48 GMT</pubDate>
            <atom:updated>2026-01-25T14:24:48.833Z</atom:updated>
            <content:encoded><![CDATA[<p>can you even imagine what most people do?<br>they do recon, burst out some payloads and think that’s bbh?<br>naahh man, ill show you how a simple recon got me $100</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*puZjvPWD2T3rz23FfeJBgQ.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*LOpDSqVhsDOJFMjWR5vreQ.png" /></figure><p>I used shodan for the recon. I put the target in the query and I got various results where one was updated on the same day when I was checking.<br><a href="https://www.shodan.io/search?query=tatamotors.com">https://www.shodan.io/search?query=redacted.com</a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*SD3zuN_feOEe4L8NHdCKAg.png" /></figure><p>I than went to <a href="https://sub.sub.redacted.com/"><em>https://sub.sub.redacted.com</em></a> and found a page which had literally nothing in it.</p><p>then i thought of fuzzing the website, i used dirsearch with the common wordlist.</p><blockquote>dirsearch -u <a href="https://sub.sub.redacted.com/">https://sub.sub.redacted.com/</a></blockquote><p>i got to see a 403 on /.env which says the file is available but not accessible and when i tried to visit <a href="https://sub.sub.redacted.com/.env"><em>https://sub.sub.redacted.com/.env</em></a> i got a cloudflare error saying “<strong>Sorry, you have been blocked You are unable to access redacted.com</strong>”</p><h4>One Question That Matters</h4><p>If the WAF blocks me<br>what is it protecting?</p><p>A WAF only protects what it sits in front of.<br>If the origin server is exposed<br>the WAF means nothing.</p><p>So I went looking for the real server.</p><h4>Shodan Changed Everything</h4><h4>WAF Bypass in One Step</h4><p>Accessing the application through the origin IP completely bypassed the WAF.<br> No filters<br> No blocks<br> No warnings</p><p>Requesting the .env file returned a clean 200 OK.</p><p>The production environment file was exposed.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fgiphy.com%2Fembed%2FQNFhOolVeCzPQ2Mx85%2Ftwitter%2Fiframe&amp;display_name=Giphy&amp;url=https%3A%2F%2Fmedia.giphy.com%2Fmedia%2Fv1.Y2lkPTc5MGI3NjExNzAycG5kM2twbm1waHFuZzVoaGo5YzI1bHh1MTcxcjh4cmt3YnB5YyZlcD12MV9naWZzX3NlYXJjaCZjdD1n%2FQNFhOolVeCzPQ2Mx85%2Fgiphy.gif&amp;image=https%3A%2F%2Fmedia0.giphy.com%2Fmedia%2Fv1.Y2lkPTc5MGI3NjExcDk4dHVuZWhqZmZ4bWEwNWJ3anQ2dWVxbHRvMW9qc3JsdDZ4YnJiYSZlcD12MV9pbnRlcm5hbF9naWZfYnlfaWQmY3Q9Zw%2FQNFhOolVeCzPQ2Mx85%2Fgiphy_s.gif&amp;type=text%2Fhtml&amp;schema=giphy" width="435" height="244" frameborder="0" scrolling="no"><a href="https://medium.com/media/195f27419d2f37f9121fc293c579e5ef/href">https://medium.com/media/195f27419d2f37f9121fc293c579e5ef/href</a></iframe><h4>What Was Leaked</h4><p>The file contained critical production secrets.</p><p>Database credentials<br>Session signing keys<br>Internal API routes</p><p>This was more than a file leak.<br>It was a full security control bypass.</p><h4>Why This Is Serious</h4><p>An attacker could avoid every WAF rule.<br>No rate limiting<br>No injection filters<br>No detection<br>With valid credentials, backend systems were within reach.<br>This is how small misconfigs turn into big breaches.</p><h4>reported it and got it fixed quickly with a P2 with $100, not much but not bad i guess.</h4><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fgiphy.com%2Fembed%2FPOENQvQ2O29UcNzMgM%2Ftwitter%2Fiframe&amp;display_name=Giphy&amp;url=https%3A%2F%2Fmedia.giphy.com%2Fmedia%2Fv1.Y2lkPWVjZjA1ZTQ3dWppZTJ6cXp2c3R5bWs3dmVmMDlwNW9yeWVibGw2aXNnMG1tbzdteCZlcD12MV9naWZzX3NlYXJjaCZjdD1n%2FPOENQvQ2O29UcNzMgM%2Fgiphy.gif&amp;image=https%3A%2F%2Fmedia0.giphy.com%2Fmedia%2Fv1.Y2lkPTc5MGI3NjExYjg4a2hxcjlxaXVpcXR6bjUyNDZ0aDZ0YTRidDg4ZmpkMXppMGtrdyZlcD12MV9pbnRlcm5hbF9naWZfYnlfaWQmY3Q9Zw%2FPOENQvQ2O29UcNzMgM%2Fgiphy_s.gif&amp;type=text%2Fhtml&amp;schema=giphy" width="435" height="244" frameborder="0" scrolling="no"><a href="https://medium.com/media/aeb05a037973387cd8ae5aed6d6a15f3/href">https://medium.com/media/aeb05a037973387cd8ae5aed6d6a15f3/href</a></iframe><h4>50 claps if you like it ;) thanks for reading</h4><p>Watch scan data.<br>Test quickly.<br>Think beyond the front door.</p><h4>Connect here:</h4><p>folio: <a href="https://swarnimbandekar.github.io/">https://swarnimbandekar.github.io/</a><br>LinkedIn: <a href="https://www.linkedin.com/in/swarnimbandekar/?originalSubdomain=in">https://www.linkedin.com/in/swarnimbandekar/</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b6bc126e2f4b" width="1" height="1" alt=""><hr><p><a href="https://infosecwriteups.com/easy-100-bypass-403-to-200-ok-b6bc126e2f4b">easy $100 | bypass 403 to 200 ok</a> was originally published in <a href="https://infosecwriteups.com/">InfoSec Write-ups</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[️ 100 Web App Bugs You Should Be Hunting ]]></title>
            <link>https://infosecwriteups.com/100-web-app-bugs-you-should-be-hunting-6295f78d6880?source=rss-242059e90f66------2</link>
            <guid isPermaLink="false">https://medium.com/p/6295f78d6880</guid>
            <category><![CDATA[penetration-testing]]></category>
            <category><![CDATA[bug-bounty-writeup]]></category>
            <category><![CDATA[hacking]]></category>
            <category><![CDATA[bug-bounty]]></category>
            <category><![CDATA[infosec]]></category>
            <dc:creator><![CDATA[Swarnim Bandekar]]></dc:creator>
            <pubDate>Thu, 19 Jun 2025 06:19:36 GMT</pubDate>
            <atom:updated>2025-06-19T06:19:36.179Z</atom:updated>
            <content:encoded><![CDATA[<p>From IDORs to SSRFs — A Mega List to Supercharge Your Hunting</p><p>In this post, I’m sharing <strong>100 web app exploit ideas</strong> that you can explore during your bug bounty hunts. These are not theoretical — many of these are based on real-world bugs reported in public bug bounty programs.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fgiphy.com%2Fembed%2FTOWeGr70V2R1K%2Ftwitter%2Fiframe&amp;display_name=Giphy&amp;url=https%3A%2F%2Fmedia.giphy.com%2Fmedia%2Fv1.Y2lkPWVjZjA1ZTQ3ZzZydjBmbHV3MjF1MG94dzNlaTNudXJxY2J2ZDVjOHc4dHY4NXQ2OCZlcD12MV9naWZzX3NlYXJjaCZjdD1n%2FTOWeGr70V2R1K%2Fgiphy.gif&amp;image=https%3A%2F%2Fmedia3.giphy.com%2Fmedia%2Fv1.Y2lkPTc5MGI3NjExOHFuYTAxMDh3dTFyam5pZ3M4ejl2NTdjNjFuYXo0amUyMnVlNTBxYyZlcD12MV9pbnRlcm5hbF9naWZfYnlfaWQmY3Q9Zw%2FTOWeGr70V2R1K%2Fgiphy_s.gif&amp;type=text%2Fhtml&amp;schema=giphy" width="435" height="244" frameborder="0" scrolling="no"><a href="https://medium.com/media/784dec8ec596618859252ffc08220ac9/href">https://medium.com/media/784dec8ec596618859252ffc08220ac9/href</a></iframe><h3>🔓 Insecure Direct Object References (IDOR)</h3><ul><li>IDOR on user profile update</li><li>IDOR via email enumeration</li><li>IDOR on subscription APIs</li><li>Broken object-level authorization in API</li></ul><h3>💉 Cross-Site Scripting (XSS)</h3><ul><li>Reflected XSS in search bar</li><li>Stored XSS in comments</li><li>DOM-based XSS in JS-heavy pages</li><li>XSS via SVG upload</li><li>XSS via malformed JSON</li><li>HTML injection in emails</li></ul><h3>🎯 Open Redirects</h3><ul><li>Open redirect via query param</li><li>Open redirect with base64 trick</li><li>Unsafe redirect in logout flow</li><li>Unsafe redirect after login</li></ul><h3>🧠 Logic and Business Flaws</h3><ul><li>Logic flaw in shopping cart</li><li>Price manipulation via hidden input</li><li>Coupon abuse</li><li>Duplicate purchase via race condition</li><li>Bypassing paywall via caching</li><li>Business logic flaw in refunds</li><li>Flawed invite/token logic</li></ul><h3>🐍 SSRF (Server-Side Request Forgery)</h3><ul><li>SSRF in PDF generator</li><li>SSRF via webhook feature</li><li>Blind SSRF via image fetcher</li><li>SSRF using DNS rebinding</li><li>SSRF via Cloud metadata endpoint</li></ul><h3>🔐 Authentication &amp; Session</h3><ul><li>Broken authentication bypass</li><li>Insecure password reset token</li><li>Missing rate limit on login</li><li>No lockout after failed login attempts</li><li>JWT token none algorithm</li><li>JWT with weak secret</li><li>JWT with overly long expiration</li><li>Broken session invalidation on logout</li><li>Session fixation</li><li>Default credentials active</li><li>Bypassing email verification</li><li>No MFA enforced for admin</li></ul><h3>🧾 OAuth &amp; SAML Issues</h3><ul><li>OAuth misconfiguration (open redirect)</li><li>OAuth token leakage via Referer</li><li>OAuth scope escalation</li><li>SAML signature bypass</li></ul><h3>🎯 CSRF (Cross-Site Request Forgery)</h3><ul><li>CSRF on profile update</li><li>CSRF on account deletion</li></ul><h3>🌀 CORS &amp; Misconfigurations</h3><ul><li>CORS misconfiguration (wildcard with credentials)</li><li>Overly permissive CORS policy</li><li>Improper cookie flags (missing HttpOnly/Secure)</li><li>Content-Security-Policy misconfigured</li></ul><h3>🔨 Upload &amp; File Handling</h3><ul><li>Unsafe file upload (no content-type check)</li><li>MIME type confusion on uploads</li><li>Directory traversal in file viewer</li><li>Uploading polyglot files</li><li>File inclusion via upload &amp; access</li><li>Null byte injection in file path</li><li>Command injection via filename</li></ul><h3>⚙️ Deserialization &amp; Injection</h3><ul><li>Unsafe deserialization (PHP, Java)</li><li>SQL injection on rare parameter</li><li>GraphQL injection</li><li>HTTP parameter pollution</li><li>Using CRLF to inject headers</li><li>Using Unicode to bypass filters</li></ul><h3>⚡ GraphQL &amp; API Exploits</h3><ul><li>GraphQL introspection enabled</li><li>GraphQL injection</li><li>GraphQL rate limit missing</li><li>Mass assignment in REST API</li><li>API allows deleting arbitrary users</li><li>Missing access control on internal docs</li><li>API key reuse across environments</li></ul><h3>🧱 Rate Limits &amp; Brute Force</h3><ul><li>Missing rate limit on login</li><li>Credential stuffing on forgotten endpoints</li><li>No lockout after failed login attempts</li><li>Rate-limit bypass using X-Forwarded-For</li><li>GraphQL rate limit missing</li></ul><h3>🧪 Miscellaneous &amp; Creative Angles</h3><ul><li>Authentication bypass with null bytes</li><li>Host header injection</li><li>Abuse of debug endpoints</li><li>Replay attack on payment endpoint</li><li>Leaked credentials in JavaScript</li><li>Leaked API keys in mobile app</li><li>Token leakage via JavaScript var</li><li>Fuzzing params to find debug info</li><li>Using alternative HTTP methods (PUT, DELETE)</li><li>Cache poisoning via Host header</li><li>Cache deception via file extension</li><li>Hidden admin functionality in frontend</li><li>Mobile app with hardcoded secrets</li></ul><h3>📂 Sensitive Info Disclosure</h3><ul><li>Debugging info in error messages</li><li>Server reveals stack traces</li><li>Leak of internal IP in error message</li><li>Leaking sensitive info in analytics scripts</li><li>Misconfigured .git exposed</li><li>Accessible .env file</li><li>Backup file accessible (.bak)</li><li>Open database exposed (MongoDB, Redis)</li></ul><h3>🔍 Clickjacking &amp; UI Issues</h3><ul><li>Clickjacking vulnerability</li><li>Lack of brute-force protection</li><li>Open WebSocket with no auth</li><li>Insecure image proxy</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Jf2txSzU6dtFwcN-bswO5Q.jpeg" /></figure><blockquote>Ready to hit the hunting grounds again.<br>If you found this helpful, drop a 👏 and share it with your fellow hackers.<br>Stay curious. Stay ethical.<br> — Swarnim Bandekar</blockquote><p>Credits: <a href="https://www.linkedin.com/in/wesley-thijs-8b384828a?miniProfileUrn=urn%3Ali%3Afsd_profile%3AACoAAEY_fwcBVfLJI1Ig_-A5EBJvfQJ-PNYwHCc">Wesley Thijs</a></p><h4>Connect with me:</h4><p><a href="https://www.swarnim.live/">Swarnim Bandekar</a></p><p>Linkedin:<br><a href="https://www.linkedin.com/in/swarnimbandekar/">https://www.linkedin.com/in/swarnimbandekar</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6295f78d6880" width="1" height="1" alt=""><hr><p><a href="https://infosecwriteups.com/100-web-app-bugs-you-should-be-hunting-6295f78d6880">🕷️ 100 Web App Bugs You Should Be Hunting 💥</a> was originally published in <a href="https://infosecwriteups.com/">InfoSec Write-ups</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[ How a Simple RECON Earned Me ₹XX,000]]></title>
            <link>https://infosecwriteups.com/how-a-simple-recon-earned-me-xx-000-4282805d2eac?source=rss-242059e90f66------2</link>
            <guid isPermaLink="false">https://medium.com/p/4282805d2eac</guid>
            <category><![CDATA[infosec]]></category>
            <category><![CDATA[bug-bounty-writeup]]></category>
            <category><![CDATA[hacking]]></category>
            <category><![CDATA[penetration-testing]]></category>
            <category><![CDATA[bug-bounty]]></category>
            <dc:creator><![CDATA[Swarnim Bandekar]]></dc:creator>
            <pubDate>Wed, 11 Jun 2025 16:42:05 GMT</pubDate>
            <atom:updated>2025-06-12T06:11:23.462Z</atom:updated>
            <content:encoded><![CDATA[<blockquote>Security bugs aren’t always flashy. Sometimes, you don’t need to pop a shell or find an RCE to make an impact.<br> Sometimes… all you need is a little curiosity and a lot of recon.</blockquote><blockquote>This is the story of how I stumbled upon an <strong>exposed origin IP</strong> at <strong>XYZ</strong>, India’s largest stock brokerage, and how that led to an unexpected <strong>₹XX,000 bounty</strong> — all without writing a single exploit.</blockquote><h4>☕ It started with a late-night recon session…</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/500/0*zqz4vkrVjE57oFYN.png" /></figure><p>Like most bug bounty hunters, I was doing my usual late-night stroll across a domain — XYZ’s public-facing assets.<br>WAF? Cloudflare.<br>Endpoints? Mostly locked.<br>But I had a hunch.</p><p>Out came Shodan, my favorite search engine for all the things you <em>shouldn’t</em> see.</p><p>One quick dork later:</p><pre>Ssl.cert.subject.CN:&quot;domain.com&quot; 200</pre><p>And boom — I landed on an IP:<br>11.1.111.11</p><p>An Amazon EC2 instance quietly serving traffic… and not a trace of Cloudflare in sight.</p><h4>🧠 “Wait… is this really accessible?”</h4><p>I typed in:<br>https://11.1.111.11/login</p><p><strong>It loaded.</strong><br>No 403. No timeout. Just a clean login page staring right back at me.</p><p>I double-checked with tools: no WAF, no CDN headers, and the cert? Signed for domain.com.</p><p>Bingo.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fgiphy.com%2Fembed%2FMM0Jrc8BHKx3y%2Ftwitter%2Fiframe&amp;display_name=Giphy&amp;url=https%3A%2F%2Fmedia.giphy.com%2Fmedia%2Fv1.Y2lkPTc5MGI3NjExZXV5Ym90d21jMWpweGkwenNycDNid2hsYmxsY3ppMmEwZGV4NmpyaSZlcD12MV9naWZzX3NlYXJjaCZjdD1n%2FMM0Jrc8BHKx3y%2Fgiphy.gif&amp;image=https%3A%2F%2Fmedia0.giphy.com%2Fmedia%2Fv1.Y2lkPTc5MGI3NjExZjFlN2pkMDc0ZW53OHludTFqc3IyM2k1MmwweTRnNjZmaWd1bmxodCZlcD12MV9pbnRlcm5hbF9naWZfYnlfaWQmY3Q9Zw%2FMM0Jrc8BHKx3y%2Fgiphy_s.gif&amp;type=text%2Fhtml&amp;schema=giphy" width="435" height="244" frameborder="0" scrolling="no"><a href="https://medium.com/media/87df765490ce9e17249ba194985938b1/href">https://medium.com/media/87df765490ce9e17249ba194985938b1/href</a></iframe><h4>🤔 But is it a <em>bypass</em>?</h4><p>Here’s where it got interesting. XYZ uses Cloudflare for protection — rate limiting, WAF, DDoS, the works.<br>But this subdomain — sub.domain.com— wasn’t behind it.</p><p>At first glance, that might seem like a non-issue. Maybe internal, maybe forgotten.</p><p>But to an attacker?<br>It’s an open door.<br>Direct origin access means you can:</p><ul><li>Bypass rate limits</li><li>Fuzz without detection</li><li>Brute force at full throttle</li><li>Even launch DDoS attacks — because there’s no shield in place</li></ul><p>And it all stems from one thing: <strong>security misconfiguration</strong>.</p><h4>📬 The response that made me smile</h4><p>I reported it privately through ComOlho, their bug bounty platform.<br>Soon after, XYZ got back:</p><blockquote><em>“Hey Swarnim, we discussed this internally… it’s not behind Cloudflare for some internal reasons. But because of your report, we’re now discussing whether to fix it. Please repost publicly — we’ll process your bounty.”</em></blockquote><p>I wasn’t expecting a big payout — just happy they took it seriously.</p><p>But then…</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/593/1*q83SQ1RErbm8Zc1oFP3iwA.png" /></figure><p><strong>₹XX,000 dropped into my account.</strong></p><p>No exploit. No shell. Just impact.</p><h4>💡 What I learned</h4><ul><li><strong>Bug bounties aren’t about breaking things</strong> — they’re about finding things that are broken.</li><li><strong>Even “boring” bugs matter</strong> — origin IP exposure can change the threat model completely.</li><li><strong>If it feels too quiet… dig deeper</strong> — sometimes the loudest vulnerabilities whisper.</li></ul><h4>🚀 To all bug hunters out there…</h4><p>Don’t chase just the CVEs.<br>Don’t underestimate the power of <strong>recon</strong>, <strong>curiosity</strong>, and <strong>context</strong>.</p><p>This was one IP. One misconfiguration.<br>And it paid off — literally and figuratively.</p><p>Thanks, XYZ. And shoutout to platforms like ComOlho for making security collaborative and rewarding.</p><p>Time to go hunting again. 🔍💻</p><p>If you liked this story, give it a 👏 and share it with fellow hackers.</p><p>Stay safe. Stay curious.<br> — <em>Swarnim Bandekar</em></p><h4>Connect with me:</h4><p><a href="https://swarnim.live/">Swarnim Bandekar</a></p><p>Linkedin:<br><a href="https://www.linkedin.com/in/swarnimbandekar/">https://www.linkedin.com/in/swarnimbandekar/</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4282805d2eac" width="1" height="1" alt=""><hr><p><a href="https://infosecwriteups.com/how-a-simple-recon-earned-me-xx-000-4282805d2eac">💰 How a Simple RECON Earned Me ₹XX,000</a> was originally published in <a href="https://infosecwriteups.com/">InfoSec Write-ups</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[ The “Unlimited Leave” Hack I Found at My College]]></title>
            <link>https://infosecwriteups.com/the-unlimited-leave-hack-i-found-at-my-college-4c772df5f8e4?source=rss-242059e90f66------2</link>
            <guid isPermaLink="false">https://medium.com/p/4c772df5f8e4</guid>
            <category><![CDATA[bug-bounty]]></category>
            <category><![CDATA[bug-bounty-tips]]></category>
            <category><![CDATA[hacking]]></category>
            <category><![CDATA[penetration-testing]]></category>
            <category><![CDATA[idor]]></category>
            <dc:creator><![CDATA[Swarnim Bandekar]]></dc:creator>
            <pubDate>Thu, 15 May 2025 17:52:17 GMT</pubDate>
            <atom:updated>2025-06-06T05:08:07.366Z</atom:updated>
            <content:encoded><![CDATA[<blockquote><em>“With great power comes great responsibility.”</em><br>Uncle Ben (and every ethical hacker ever)</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*3Wz0lK2K-BF-atBoNU2Sxw.jpeg" /></figure><h3>🏫 The Setup: Life Inside the Hostel</h3><p>Being a college student living in a hostel means every outing feels like a <strong>covert military mission</strong>.</p><p>You don’t just leave.<br> You apply for a pass.<br> Then wait for mentor approval.<br> Then warden approval.<br> Then — <em>maybe</em> — you get to step outside for a couple of hours.</p><p>At VIT-AP, all of this happens on a student portal called <strong>VTOP</strong>.</p><p>One day, while casually navigating through old outing passes (okay, maybe with Burp Suite open 😅), I noticed something that made me freeze.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fgiphy.com%2Fembed%2FYQitE4YNQNahy%2Ftwitter%2Fiframe&amp;display_name=Giphy&amp;url=https%3A%2F%2Fmedia.giphy.com%2Fmedia%2Fv1.Y2lkPTc5MGI3NjExZGhmNWtkZjhjbnA5enNlaDd4MjNiM2R4ajRvaXlhemtudXllNjR4byZlcD12MV9naWZzX3NlYXJjaCZjdD1n%2FYQitE4YNQNahy%2Fgiphy.gif&amp;image=https%3A%2F%2Fmedia4.giphy.com%2Fmedia%2Fv1.Y2lkPTc5MGI3NjExd3owOWxscXFyZTZlbWFpZWtqYmVkcTdzNHN5dzNkYWp2dWF2aHc3byZlcD12MV9pbnRlcm5hbF9naWZfYnlfaWQmY3Q9Zw%2FYQitE4YNQNahy%2Fgiphy_s.gif&amp;type=text%2Fhtml&amp;schema=giphy" width="435" height="244" frameborder="0" scrolling="no"><a href="https://medium.com/media/3d66b01b983af206b84e8e7828d5fd29/href">https://medium.com/media/3d66b01b983af206b84e8e7828d5fd29/href</a></iframe><h3>🕵️‍♂️ The Discovery:</h3><p>After applying for a new leave, I looked at the request that generated the outing form. It looked something like this:</p><pre>GET /sensored/sensored/sensored/WXXXXXXX?authorizedID=XYZ&amp;_csrf=ABC...</pre><p>That WXXXXXXX?</p><p>That’s the <strong>leave ID</strong>.</p><p>So I had a thought:<br>What if I changed that ID?<br>What if I put in an <strong>older leave ID</strong> that had already been approved?<br>Or what if I… <strong>guessed someone else’s leave ID</strong>?</p><p>So I tried. I intercepted the request, modified the leave ID, and…</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*cNp0sd16BVDwVrazw24yhQ.png" /></figure><h3>🚨 The Vulnerability: IDOR Strikes Again</h3><p>The server didn’t ask questions.<br>No validation. No permission check.</p><p>I was able to:</p><p>✅ <strong>Download my own outing pass even if it wasn’t approved yet</strong><br>✅ <strong>Access outing passes of other students — just by guessing theirs</strong><br>✅ <strong>Bypass the entire mentor and warden approval workflow</strong></p><p>This, my friends, is a <strong>textbook IDOR</strong> — Insecure Direct Object Reference.</p><p>The kind of bug that’s simple, but devastating.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*l7kwE5X4VXv2FwxLA4BVGA.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*uqEF05Hm8_czFk-QQrotMQ.png" /></figure><h3>🤯 The Temptation</h3><p>I won’t lie. For a second, I sat there like:</p><blockquote>“So… I can leave the hostel anytime now?”<em><br> </em>“No more waiting on approvals?”<em><br> </em>“I could generate outing passes for anyone?”</blockquote><p>Unlimited outings. Unlimited freedom. Zero oversight.</p><p>But here’s the thing: <strong>that’s not why I do this</strong>.</p><p>I don’t hack to escape. I hack to secure.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fgiphy.com%2Fembed%2FRbDKaczqWovIugyJmW%2Ftwitter%2Fiframe&amp;display_name=Giphy&amp;url=https%3A%2F%2Fmedia.giphy.com%2Fmedia%2Fv1.Y2lkPTc5MGI3NjExZ2Y3Z3YwdWJ4MHAyaHdoM2h4YjZzbjY1ajN3YWRhbHo5NWlhY3dzaiZlcD12MV9naWZzX3NlYXJjaCZjdD1n%2FRbDKaczqWovIugyJmW%2Fgiphy.gif&amp;image=https%3A%2F%2Fmedia4.giphy.com%2Fmedia%2Fv1.Y2lkPTc5MGI3NjExYzZhaHQzNzRtOGI3em1pcml0NThpMmtpejVqOGY0dXUxZDIzNTduYSZlcD12MV9pbnRlcm5hbF9naWZfYnlfaWQmY3Q9Zw%2FRbDKaczqWovIugyJmW%2Fgiphy_s.gif&amp;type=text%2Fhtml&amp;schema=giphy" width="435" height="244" frameborder="0" scrolling="no"><a href="https://medium.com/media/64d77b0c57c936c1ad486fede697ea84/href">https://medium.com/media/64d77b0c57c936c1ad486fede697ea84/href</a></iframe><h3>📬 The Responsible Disclosure</h3><p>Instead of exploiting it, I did the right thing. I wrote a detailed vulnerability report and sent it to the college IT team. (SDC)</p><p>What I included:</p><ul><li>📌 A step-by-step breakdown of the bug</li><li>📌 The exact affected URL and how to replicate the issue</li><li>📌 A video PoC showing the vulnerability in action</li><li>📌 Recommendations on how to fix it</li></ul><h3>⏱️ The Response: Fast. Respectful. Responsible.</h3><p>To my surprise — and respect — the VIT-AP team took action <strong>immediately</strong>.<br>The issue was <strong>patched in just 4 days.</strong> ✅</p><p>No debates, no denials — just good security hygiene. That’s rare. And awesome.</p><h3>💡 Lessons Learned</h3><p>🛡️ <strong>Always validate access on the server-side.</strong><br>🧠 <strong>Security isn’t about complex hacks. It’s about overlooked logic.</strong><br>🤝 <strong>Ethical hacking builds bridges — not walls.</strong></p><p>This experience was more than just a bug find. It was a crash course in access control, ethics, and responsible disclosure.</p><h3>🧠 Final Thoughts</h3><p>You don’t need zero-days to make an impact.<br> Sometimes, all it takes is <strong>a changed ID in a URL</strong> — and the right mindset.</p><p>So if you’re a budding hacker reading this:<br>Stay curious. Stay ethical.<br>Hack not to break things, but to fix them.</p><p>— <em>Swarnim Bandekar</em></p><p><strong>Tags:</strong><br> #CyberSecurity #EthicalHacking #WebSecurity #IDOR #VulnerabilityDisclosure #VITAP #StudentHacks #BugBounty #HackWithPurpose #Infosec</p><h3><strong>Reach Out:</strong></h3><p><a href="https://www.linkedin.com/in/swarnimbandekar/">https://www.linkedin.com/in/swarnimbandekar/</a></p><p><a href="https://www.swarnim.live/">Swarnim Bandekar</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4c772df5f8e4" width="1" height="1" alt=""><hr><p><a href="https://infosecwriteups.com/the-unlimited-leave-hack-i-found-at-my-college-4c772df5f8e4">🎭 The “Unlimited Leave” Hack I Found at My College</a> was originally published in <a href="https://infosecwriteups.com/">InfoSec Write-ups</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>