<?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 Sonu Chaudhary 🧑‍💻 on Medium]]></title>
        <description><![CDATA[Stories by Sonu Chaudhary 🧑‍💻 on Medium]]></description>
        <link>https://medium.com/@sonuoffsec?source=rss-d3741153ce50------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*Nvvj5rBRQajvNQFv</url>
            <title>Stories by Sonu Chaudhary 🧑‍💻 on Medium</title>
            <link>https://medium.com/@sonuoffsec?source=rss-d3741153ce50------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 16:47:50 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@sonuoffsec/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[How I Find the Real IP Behind Cloudflare (When It’s Not Supposed to Be Visible)]]></title>
            <link>https://medium.com/@sonuoffsec/how-i-find-the-real-ip-behind-cloudflare-when-its-not-supposed-to-be-visible-cd48e2ce5e62?source=rss-d3741153ce50------2</link>
            <guid isPermaLink="false">https://medium.com/p/cd48e2ce5e62</guid>
            <category><![CDATA[cybersecurity]]></category>
            <category><![CDATA[hacking]]></category>
            <category><![CDATA[bug-bounty-tips]]></category>
            <category><![CDATA[bug-bounty-writeup]]></category>
            <category><![CDATA[bug-bounty]]></category>
            <dc:creator><![CDATA[Sonu Chaudhary ‍]]></dc:creator>
            <pubDate>Sat, 21 Mar 2026 19:18:58 GMT</pubDate>
            <atom:updated>2026-03-21T19:18:58.764Z</atom:updated>
            <content:encoded><![CDATA[<p>A lot of people think putting a site behind Cloudflare = done, secure.’</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*U-yLarep3ueN4HBxPEM-oA.png" /><figcaption>No need to break Cloudflare, just find what it’s not protecting.</figcaption></figure><p>That’s not how it works.</p><p>Cloudflare is strong, no doubt. It hides the real IP, filters traffic, blocks obvious attacks… but it only protects traffic that actually goes through it.</p><p>If I can find the real server IP somewhere else, I don’t need to “bypass” Cloudflare.</p><p>I just go around it.</p><h3>Quick idea of what’s happening</h3><p>When a site uses Cloudflare, you’re not talking to the server directly.</p><p>It’s more like:</p><ul><li>You → Cloudflare</li><li>Cloudflare → Server</li></ul><p>That server still has a real IP (origin IP).<br>And if that leaks… game changes.</p><h3>Why this matters (from an attacker mindset)</h3><p>Once the real IP is known:</p><ul><li>You can hit the server directly</li><li>No Cloudflare filtering</li><li>Sometimes no WAF at all</li><li>Rate limits? Depends… but often weaker</li></ul><p>Basically, all that protection… gone.</p><h3>How I usually approach this</h3><p>Not gonna lie — this is rarely about some “crazy exploit”.</p><p>Most of the time it’s just looking for mistakes.</p><h3>1. Subdomains (easy wins sometimes)</h3><p>First thing I usually check.</p><p>Main domain is protected, but dev or API might not be.</p><p>Something like:</p><pre>api.target.com<br>dev.target.com<br>old.target.com</pre><p>If one of these points directly to an IP instead of Cloudflare, that’s a big hint.</p><p>Sometimes it literally gives you the origin.</p><h3>2. Old configs people forgot about</h3><p>A lot of sites didn’t start with Cloudflare.</p><p>They moved to it later.</p><p>Problem is old DNS data doesn’t just disappear.<br>It’s still floating around in public datasets.</p><p>So even if everything looks clean now, the past can expose the real IP.</p><h3>3. Staging / testing stuff (very common)</h3><p>This is honestly one of the most common leaks I see.</p><p>Developers spin up:</p><pre>staging.target.com<br>test.target.com<br>beta.target.com</pre><p>And forget to lock it down properly.</p><p>These often point straight to the origin server.</p><p>No Cloudflare, nothing.</p><h3>4. Email side leaks</h3><p>This one is a bit situational, but still worth checking.</p><p>If the app sends emails (reset password, notifications, etc.), headers can sometimes reveal internal routing or IP-related info.</p><p>Not always a direct hit, but sometimes it gives useful clues.</p><h3>5. Third-party integrations</h3><p>Sometimes services connect directly to the backend:</p><ul><li>APIs</li><li>Monitoring tools</li><li>External services</li></ul><p>If any of those endpoints are exposed or misconfigured, they can leak info about the infrastructure.</p><h3>The important part</h3><p>I’m not “breaking Cloudflare”.</p><p>I’m just finding a path that doesn’t go through it.</p><p>That’s it.</p><h3>If you’re defending this</h3><p>This is where most setups fail.</p><p>Basic things that should be done (but often aren’t):</p><ul><li>Only allow Cloudflare IPs to access your server</li><li>Don’t leave subdomains unprotected</li><li>Lock staging environments properly</li><li>Regularly check what’s exposed publicly</li></ul><p>Nothing advanced. Just no shortcuts.</p><h3>Final thought</h3><p>People think this is some advanced bypass technique.</p><p>In reality?</p><p>It’s usually just:</p><blockquote><em>misconfiguration + a bit of patience</em></blockquote><p>Cloudflare works fine.</p><p>The problem is everything around it.</p><p><em>For educational purposes only. Don’t test this on systems you don’t have permission for.</em></p><p>Let’s connect 👇</p><p><a href="https://www.linkedin.com/in/sonuoffsec">Linkedin</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=cd48e2ce5e62" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Breaking the Wall: A Deep Dive Into WAF Detection and Bypass Techniques]]></title>
            <link>https://medium.com/@sonuoffsec/breaking-the-wall-a-deep-dive-into-waf-detection-and-bypass-techniques-e880be92d0c0?source=rss-d3741153ce50------2</link>
            <guid isPermaLink="false">https://medium.com/p/e880be92d0c0</guid>
            <category><![CDATA[bug-bounty-tips]]></category>
            <category><![CDATA[bug-bounty-writeup]]></category>
            <category><![CDATA[bug-bounty]]></category>
            <category><![CDATA[waf-bypass]]></category>
            <category><![CDATA[aws-waf]]></category>
            <dc:creator><![CDATA[Sonu Chaudhary ‍]]></dc:creator>
            <pubDate>Sat, 21 Mar 2026 11:33:41 GMT</pubDate>
            <atom:updated>2026-03-21T11:42:47.661Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*E2vFOrdZfsBiJhss_-VXPw.png" /></figure><h3>“We Have a WAF, So We’re Secure.”</h3><p>That’s what the client told me.</p><p>It was a large financial company. Mature security team. Enterprise-grade tooling.<br> They were confident.</p><p>Very confident.</p><p>Two hours later… I was inside their application.</p><p>No zero-day.<br>No advanced exploit.<br>No magic.</p><blockquote>Their WAF didn’t fail. Their assumption did.</blockquote><h3>The Truth About WAFs</h3><p>Web Application Firewalls are everywhere.</p><p>Cloudflare. Akamai. Imperva. AWS.</p><p>They promise protection against:</p><ul><li>SQL Injection</li><li>XSS</li><li>RCE</li><li>Bots</li></ul><p>And they <em>do work……………………………….</em></p><blockquote><strong><em>But only against noise “not against intent”</em></strong></blockquote><blockquote><strong><em>A WAF filters attackers. It doesn’t stop them.</em></strong></blockquote><h3>Why Most Testers Fail</h3><p>Most people approach WAFs like this:</p><ul><li>Send payload</li><li>Get blocked</li><li>Try harder payload</li><li>Get blocked again</li></ul><p>And then they conclude:</p><blockquote><em>“This WAF is too strong.”</em></blockquote><p>No.</p><blockquote><strong><em>You’re just attacking it blindly.</em></strong></blockquote><h3>The Shift That Changes Everything</h3><p>Stop treating a WAF like a wall.<br> Start treating it like a <strong>system</strong>.</p><p>Because systems have:</p><ul><li>Logic</li><li>Behaviour</li><li>Weaknesses</li></ul><p>And most importantly:</p><blockquote><strong><em>Blind spots.</em></strong></blockquote><h3>Step 1: Make the WAF Reveal Itself</h3><p>Before bypassing anything, ask:</p><blockquote><strong><em>What exactly is protecting the target?</em></strong></blockquote><h3>A Simple Request Can Expose It</h3><pre>curl -I https://target.com</pre><p>Look closely:</p><ul><li>CF-RAY → Cloudflare</li><li>X-CDN: Imperva → Imperva</li><li>X-Cache: filtered → Akamai</li></ul><p>Sometimes… the WAF tells you what it is.</p><h3>Trigger It on Purpose</h3><pre>curl &quot;https://target.com/?id=1&#39;+OR+1=1--&quot;</pre><p>Now observe:</p><ul><li>Cloudflare → branded block page</li><li>Imperva → CAPTCHA</li><li>Akamai → reference ID</li><li>ModSecurity → silent 403</li></ul><blockquote><strong><em>Every block is a fingerprint. Not a failure.</em></strong></blockquote><h3>Use Tools - But Don’t Rely on Them</h3><pre>wafw00f https://target.com</pre><p>Automation is fast.</p><p>But:</p><blockquote><strong><em>Manual observation is what actually wins.</em></strong></blockquote><h3>Step 2: Understand How It Thinks</h3><p>Most people skip this step.</p><p>That’s why most people fail.</p><h3>The 4 Detection Models</h3><h3>1. Signature-Based</h3><p>Looks for patterns like:</p><pre>UNION SELECT<br>&lt;script&gt;<br>../</pre><p><strong>Weakness:</strong> Change the structure…bypass.</p><h3>2. Anomaly Scoring</h3><p>Each suspicious input adds points.</p><p><strong>Weakness:</strong> Stay below threshold.</p><h3>3. Behaviour Analysis</h3><p>Too fast = suspicious.</p><p><strong>Weakness:</strong> Act like a normal user.</p><h3>4. Machine Learning</h3><p>Modern WAFs use ML.</p><p>But:</p><blockquote><strong><em>ML fails at the edges…..attackers live at the edges.</em></strong></blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Q4ohgTi_58SJwWI29TkBpA.png" /></figure><h3>Step 3: Breaking the Wall</h3><p>Now the practical part.</p><p>These are real techniques, not theory.</p><h3>1. Case Manipulation</h3><pre>UNION SELECT → uNiOn SeLeCt</pre><blockquote><strong><em>Same payload. Different appearance.</em></strong></blockquote><h3>2. Encoding Tricks</h3><pre>&lt;script&gt;alert(1)&lt;/script&gt;<br>↓<br>%253Cscript%253Ealert(1)%253C%252Fscript%253E</pre><blockquote><strong><em>WAF decodes once. Backend decodes twice.</em></strong></blockquote><h3>3. Comment Injection</h3><pre>UNION/**/SELECT/**/password/**/FROM/**/users</pre><blockquote><strong><em>SQL ignores comments. Regex often doesn’t.</em></strong></blockquote><h3>4. HTTP Parameter Pollution</h3><pre>?q=hello&amp;q=&lt;payload&gt;</pre><ul><li>PHP → last value</li><li>Flask → first value</li></ul><blockquote><strong><em>Exploit the mismatch between systems.</em></strong></blockquote><h3>5. Content-Type Confusion</h3><p>Send:</p><ul><li>JSON to form endpoints</li><li>XML to APIs</li></ul><blockquote><strong><em>Many WAFs don’t inspect unexpected formats properly.</em></strong></blockquote><h3>6. Chunked Transfer Encoding</h3><p>Split payload into parts.</p><blockquote><strong><em>WAF sees fragments. Backend sees full payload.</em></strong></blockquote><h3>7. Path Traversal Obfuscation</h3><pre>../../etc/passwd<br>↓<br>..%252F..%252Fetc%252Fpasswd</pre><blockquote><strong><em>Same intent. Different encoding.</em></strong></blockquote><h3>8. Header Trust Abuse</h3><pre>X-Forwarded-For: 127.0.0.1</pre><blockquote><strong><em>If the backend trusts headers “you become internal”</em></strong></blockquote><h3>The Technique Most People Ignore</h3><p>And the one that matters the most.</p><h3>“ Find the Origin Server”</h3><blockquote><strong><em>If you reach the origin… the WAF becomes irrelevant.</em></strong></blockquote><p>You’re not bypassing it.</p><p>You’re skipping it entirely.</p><h3>How It Happens</h3><ul><li>DNS history leaks</li><li>SSL certificate reuse</li><li>Email headers</li><li>SSRF</li></ul><pre>curl https://ORIGIN_IP -H &quot;Host: target.com&quot;</pre><p>And just like that:</p><blockquote><strong><em>No WAF. No filtering. Just the application.</em></strong></blockquote><h3>The Real Methodology</h3><p>Here’s what actually works:</p><ol><li>Fingerprint the WAF</li><li>Observe normal responses</li><li>Trigger controlled blocks</li><li>Identify filters</li><li>Modify payloads gradually</li><li>Combine techniques</li><li>Always hunt origin IP</li></ol><blockquote><strong><em>WAF bypass is not payload-based. It’s observation-based.</em></strong></blockquote><h3>Reality Check</h3><p>WAFs:</p><p>✅ Stop automated scanners<br> ✅ Reduce noise<br> ✅ Add friction</p><p>But they do NOT:</p><blockquote>Fix vulnerabilities<br>Stop skilled attackers<br>Replace secure coding</blockquote><h3>Final Thought</h3><blockquote><strong><em>A WAF is not a wall. It’s a filter.</em></strong></blockquote><p>And filters can always be bypassed.</p><p>Final Words</p><p>For defenders:</p><ul><li>Fix root causes</li><li>Don’t rely on WAF alone</li></ul><p>For testers:</p><ul><li>Stop spamming payloads</li><li>Start studying behaviour</li></ul><p>Because the difference between:</p><blockquote><em>Getting blocked<br> vs<br> Getting in</em></blockquote><p>…is not tools.</p><blockquote><strong><em>It’s understanding.</em></strong></blockquote><p>#cybersecurity #penetrationtesting #waf #bugbounty #appsec #infosec #ethicalhacking</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e880be92d0c0" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[403 Forbidden Bypass technique.]]></title>
            <link>https://medium.com/@sonuoffsec/403-forbidden-bypass-technique-eda321012baa?source=rss-d3741153ce50------2</link>
            <guid isPermaLink="false">https://medium.com/p/eda321012baa</guid>
            <category><![CDATA[403-crack]]></category>
            <category><![CDATA[bug-bounty]]></category>
            <category><![CDATA[bug-bounty-403]]></category>
            <category><![CDATA[403]]></category>
            <category><![CDATA[403-bypass]]></category>
            <dc:creator><![CDATA[Sonu Chaudhary ‍]]></dc:creator>
            <pubDate>Sun, 03 Oct 2021 14:07:21 GMT</pubDate>
            <atom:updated>2021-10-03T14:07:21.830Z</atom:updated>
            <content:encoded><![CDATA[<h3>403 Forbidden Bypass Technique.</h3><p>Hi, everyone!</p><p>My name is Sonu Chaudhary, I’m a security researcher from India. Here, I am sharing how we can bypass 403 Forbidden pages. There are various techniques that we can use during testing !!</p><p>What is 403</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*MQUZM2M51e4a_RwX.jpg" /></figure><p>The HTTP 403 is an HTTP status code meaning access to the requested resource is forbidden. The server understood the request, but will not fulfill it.</p><blockquote>Whenever we found 403 Page its means something is inside we just need to bypass it.</blockquote><blockquote>There are various techniques to bypass 403 Forbidden but here I discuss the top 4 ways that we can use.</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/616/0*XaUXjKPQ0s0ZGQRt.gif" /></figure><p>Try Appending {%2e} or {%2f} { <strong>/*, /./}</strong>after the first slash!</p><blockquote><a href="https://www.domain/DB">https://www.domain/DB</a> = 403<br><a href="https://www.domain/DB">https://www.domain/%2e/DB</a> =200<br><a href="https://www.domain/DB">https://www.domain/./DB</a> =200</blockquote><p>Adding headers to requests module.</p><blockquote>Content-Length: 0<br>X-rewrite-url<br>X-Original-URL<br>X-Custom-IP-Authorization<br>X-Forwarded-For</blockquote><p>Change requested method</p><blockquote>GET → POST, GET → TRACE, GET → PUT, GET <strong>→ </strong>OPTIONS</blockquote><p>USing CURL</p><blockquote>curl -i -s -k -X $’GET’ -H $’Host: account.domain.com’ -H $’X-rewrite-url: admin/login’ $’<a href="https://account.domain.com/&#39;">https://account.domain.com/&#39;</a></blockquote><p><strong>Takeaway</strong></p><p>I’m sure that a lot of security researchers had already seen their process but this is how I approach for bypassing 403 Forbidden in the vulnerable application.</p><p>That’s all for today if you have any suggestions please let me know so that we can coordinate and add something new to the given method.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/0*e3IkX1m8FLpsvZKJ.png" /></figure><p><strong>You can contact me on</strong></p><blockquote><a href="https://www.linkedin.com/in/dufferhackers/">Linkedin </a>|<a href="https://twitter.com/dufferhackers">Twitter</a></blockquote><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=eda321012baa" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>