<?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 NadSec on Medium]]></title>
        <description><![CDATA[Stories by NadSec on Medium]]></description>
        <link>https://medium.com/@somnadh0000?source=rss-80780c4794f4------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*5KnalaM7I2I0g-mFs4wTyw.png</url>
            <title>Stories by NadSec on Medium</title>
            <link>https://medium.com/@somnadh0000?source=rss-80780c4794f4------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Fri, 20 Nov 2026 07:00:18 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@somnadh0000/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[Road to OSCP/CPTS: The Ultimate SMB Enumeration Cheat Sheet ]]></title>
            <link>https://medium.com/@somnadh0000/road-to-oscp-cpts-the-ultimate-smb-enumeration-cheat-sheet-d80410e0a462?source=rss-80780c4794f4------2</link>
            <guid isPermaLink="false">https://medium.com/p/d80410e0a462</guid>
            <category><![CDATA[oscp-preparation]]></category>
            <category><![CDATA[oscp]]></category>
            <category><![CDATA[penetration-testing]]></category>
            <category><![CDATA[cybersecurity]]></category>
            <category><![CDATA[enumeration]]></category>
            <dc:creator><![CDATA[NadSec]]></dc:creator>
            <pubDate>Thu, 27 Nov 2025 06:57:44 GMT</pubDate>
            <atom:updated>2025-11-27T06:57:44.303Z</atom:updated>
            <content:encoded><![CDATA[<h3>Road to CPTS/OSCP: The Ultimate SMB Enumeration Cheat Sheet 🚀</h3><h3>👋 Introduction</h3><p>Welcome to a brand-new series I’m starting called <strong>“Road to CPTS / OSCP”</strong> — a place where I’ll be sharing crisp, exam-ready cheat sheets, recon notes, and practical offensive security material.</p><p>If you’re preparing for <strong>Hack the Box CPTS</strong>, <strong>OffSec OSCP</strong>, or any certification where SMB enumeration is a core topic…<br>then today’s blog is your new <strong>best friend</strong>. 😄</p><p>This cheat sheet includes <strong>every important SMB command</strong>, exactly as you provided — <strong>nothing changed, nothing removed</strong> — just structured in a clean, readable format.</p><p>Let’s dive in. 🔍</p><h3>Why SMB?</h3><p>let’s understand <strong>why SMB enumeration is one of the most important skills for CPTS/OSCP exams.</strong></p><p>SMB is like a treasure chest.<br> If it’s misconfigured, you can find:</p><ul><li>Hidden files</li><li>Passwords</li><li>Usernames</li><li>Misconfigured shares</li><li>And sometimes… even remote code execution 😮</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*g6BNahbuaRw6eigyhmxOFg.png" /></figure><p>Tools like <strong>smbclient, rpcclient, smbmap, CrackMapExec, and Impacket</strong> are your weapons.</p><p>Most exam machines heavily rely on SMB clues to open the door to the next step.<br> If you master this cheat sheet, you can:<br> ✔ Enumerate better<br> ✔ Find misconfigurations faster<br> ✔ Pivot into shells sooner</p><p>And that is exactly what OSCP/CPTS exams need:<br> <strong>method + speed + accuracy</strong>.</p><h3>🚀 SMB Enumeration Cheat Sheet (Everything in One Place)</h3><p>This section contains <strong>ALL commands </strong>ready for study or exam use.</p><h3>1. Port Scan</h3><pre>nmap -sV -sC -p139,445 &lt;IP&gt;</pre><pre>nmap --script smb-vuln* -p445 &lt;IP&gt;</pre><p>→ Detects SMB version, shares, and vulnerabilities (MS17–010, MS08–067).</p><h3>2. Anonymous / Null Session</h3><pre>smbclient -N -L //&lt;IP&gt;</pre><pre>rpcclient -U &quot;&quot; &lt;IP&gt;</pre><p>→ Find shares, users, and domain info without credentials.</p><h3>3. Share Enumeration</h3><pre>smbclient //&lt;IP&gt;/&lt;share&gt;</pre><pre>smbmap -H &lt;IP&gt;<br>smbmap -R &lt;share&gt; -H &lt;IP&gt;</pre><p>→ Discover readable/writable folders, sensitive files, config leaks, credentials.</p><h3>4. User Enumeration (SAMR/RPC)</h3><pre>rpcclient -U &quot;&quot; &lt;IP&gt;</pre><p>Once connected, use:</p><pre>enumdomusers<br><br>queryuser &lt;RID&gt;<br><br>enumdomains<br><br>netshareenumall</pre><p>→ Extract usernames, RIDs, group info.</p><p><strong>Impacket Faster SID Bruteforce:</strong></p><pre>lookupsid.py &lt;user&gt;:&lt;pass&gt;@&lt;IP&gt;</pre><p><strong>RID Brute Force Loop:</strong></p><pre>for i in $(seq 500 1100); do rpcclient -U &quot;&quot; &lt;IP&gt; -c &quot;queryuser 0x$(printf &#39;%x\n&#39; $i)&quot;; done</pre><h3>5. Service/Share Vulnerabilities</h3><pre>smbmap -x &quot;ipconfig /all&quot; -H &lt;IP&gt; -u user -p pass</pre><p>→ Check for remote code execution through SMB pipes.</p><pre>smbmap -R &lt;share&gt;</pre><p>→ Look for writable shares → upload .bat/.vbs/ASPX webshells.</p><h3>6. CrackMapExec (Red-Team Tool)</h3><pre>cme smb &lt;IP&gt; --shares</pre><pre>cme smb &lt;IP&gt; --pass-pol</pre><pre>cme smb &lt;IP&gt; -u user -p pass --sam</pre><pre>cme smb &lt;IP&gt; -u user -p pass --lsa</pre><pre>cme smb &lt;IP&gt; --gen-relay-list</pre><p>→ Password policy, SAM dumps, LSA secrets, relay-attack targets.</p><h3>7. Enum4linux-ng</h3><pre>./enum4linux-ng.py &lt;IP&gt; -A</pre><p>→ All-in-one user, share, RID, password policy enum.</p><h3>8. Impacket SAMR Enumeration</h3><pre>samrdump.py &lt;IP&gt;</pre><p>→ Dumps users, groups, RIDs.</p><h3>9. Server-Side Enumeration</h3><pre>smbstatus</pre><p>→ View active SMB sessions and versions (useful on compromised Samba hosts).</p><h3>10. SMB Vulnerabilities You MUST Check (Exam-Ready List)</h3><p><strong>1. SMBv1 Enabled</strong><br> → Exploits: EternalBlue, EternalRomance, DoublePulsar</p><p><strong>2. Anonymous SMB / Null Sessions</strong><br> → Enumerate users, shares, domain, SID.</p><p><strong>3. Weak or Misconfigured Shares</strong><br> → Writable shares → upload payloads.</p><p><strong>4. Weak NTFS or Share ACLs</strong><br> → Sensitive file exposure.</p><p><strong>5. SMB Signing Disabled</strong><br> → Vulnerable to NTLM relay.</p><p><strong>6. NTLMv1 / LM Hashing Enabled</strong><br> → Cracked instantly with hashcat.</p><p><strong>7. Stored Credentials in Shares</strong><br> → .ini, .txt, .config, .vbs files with passwords.</p><p><strong>8. Pipe Exploits / Lack of Hardening</strong><br> → Remote command execution via named pipes.</p><p><strong>9. Print Spooler Exposure (PrintNightmare)</strong><br> → If accessible via SMB pipes.</p><h3>11. Exploitation Paths (After Enumeration)</h3><p><strong>If SMBv1 →</strong> Exploit MS17–010 (EternalBlue)<br><strong>If writable share →</strong> Upload webshell, scheduled task, or reverse-shell script<br><strong>If SMB Signing Off →</strong> Run: responder + ntlmrelayx.py<br><strong>If credentials found →</strong> Dump SAM/LSA with CME or psexec.py</p><h3>🎯 Final Thoughts</h3><p>This blog is the first entry in my new series:<br> 📘 <strong>Road to CPTS / OSCP — Exam Prep Notes &amp; Cheat Sheets</strong></p><p>Today we covered SMB enumeration, one of the <strong>most repeated, most important, and most scoring topics</strong> in penetration testing exams.</p><p>💬 If you want cheat sheets for NFS, FTP, AD Enumeration, PrivEsc, Bufferoverflows, or Linux/Windows tricks — just tell me, I’ll write them.</p><p>Stay tuned. More deep, clean, exam-ready notes coming. 🚀</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d80410e0a462" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[ IDOR: The Bug That Opens Doors Without Knocking]]></title>
            <link>https://medium.com/@somnadh0000/idor-the-bug-that-opens-doors-without-knocking-6abbb9f9600f?source=rss-80780c4794f4------2</link>
            <guid isPermaLink="false">https://medium.com/p/6abbb9f9600f</guid>
            <category><![CDATA[bug-bounty]]></category>
            <category><![CDATA[bug-bounty-writeup]]></category>
            <category><![CDATA[cybersecurity]]></category>
            <category><![CDATA[bug-bounty-tips]]></category>
            <dc:creator><![CDATA[NadSec]]></dc:creator>
            <pubDate>Tue, 04 Nov 2025 16:34:47 GMT</pubDate>
            <atom:updated>2025-11-04T16:34:47.076Z</atom:updated>
            <content:encoded><![CDATA[<h3>👋 Introduction</h3><p>Imagine walking into a house just because the door wasn’t locked. No keys, no hacks — just open the door and step in.<br>That’s <strong>Insecure Direct Object Reference (IDOR)</strong> in the world of web security.<br>It’s simple, often overlooked, but can lead to <strong>massive impact with very little effort</strong>.</p><p>This blog is part of my series where I share <strong>“Less Effort, More Impact” bugs</strong> 🐞 — so you can learn to spot them too.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*C8xMJNU54-SUAa0bmtXRKA.png" /></figure><h3>🐞 What is IDOR?</h3><p>IDOR happens when an application exposes object references (like user_id, invoice_id, or document_id) directly in the URL or request — <strong>without proper access checks</strong>.</p><p>👉 Example:</p><pre>https://bank.com/user/profile?user_id=123</pre><p>If you change 123 ➝ 124, and the system shows you someone else’s data — <strong>boom, you’ve got an IDOR</strong>.</p><h3>📖 Story Time — How IDOR Works</h3><p>Let’s walk through a real-world-like scenario 👇</p><p><strong>1.You log in</strong> to your account and see your profile at:</p><pre>https://shop.com/orders?order_id=101</pre><p>2.Out of curiosity, you replace 101 with 102:</p><pre>https://shop.com/orders?order_id=102</pre><p>3.Suddenly, you see <strong>someone else’s order details</strong> (address, payment info, etc.).</p><p>The app didn’t check if that order actually belongs to you.<br> ✅ Less effort,<br> 💥 Huge impact.</p><h3>🛠️ Why Does This Happen?</h3><p>Because developers often assume:</p><p>“If a user is logged in, they should only see their data.”<br> But unless they <strong>validate ownership on the backend</strong>, users can freely manipulate IDs in requests.</p><h3>⚡ Impact of IDOR</h3><ul><li>📂 Data leakage (personal info, orders, invoices)</li><li>💳 Sensitive financial details exposure</li><li>🔐 Account takeovers (in some cases)</li><li>🌍 Wide-scale privacy issues</li></ul><p>That’s why <strong>big companies pay huge bounties</strong> for IDOR bugs.</p><h3>📝 Steps to Test for IDOR</h3><p>Here’s a simple approach you can follow:</p><p>1.🔍 <strong>Look for IDs in URLs or requests</strong> (user_id, order_id, profile_id).</p><p>2.🔄 <strong>Change the value</strong> to another random number or ID.</p><p>3.👀 <strong>Check the response</strong> — do you get someone else’s data?</p><p>4.🛑 If yes, report it responsibly.</p><p>⚠️ Remember: <strong>Always test in authorized scopes</strong> (programs you have permission for).</p><h3>🛡️ How to Fix IDOR (For Devs)</h3><ul><li>✅ Always validate user access on the server side.</li><li>✅ Use indirect references (like tokens or hashed IDs).</li><li>✅ Enforce strict authorization checks for each request.</li></ul><h3>🚀 Final Thoughts</h3><p>IDOR is proof that <strong>not every hack requires fancy tools</strong>. Sometimes, just a curious eye and a few number changes can reveal huge vulnerabilities.</p><p>So next time you see an ID in a URL or API call, don’t just scroll past. It might be your ticket to finding a <strong>“Less Effort, More Impact” bug bounty</strong> 💰.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6abbb9f9600f" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[⏱️ Race Condition Vulnerability: When Speed Becomes the Enemy]]></title>
            <link>https://medium.com/@somnadh0000/%EF%B8%8F-race-condition-vulnerability-when-speed-becomes-the-enemy-69315f95b13c?source=rss-80780c4794f4------2</link>
            <guid isPermaLink="false">https://medium.com/p/69315f95b13c</guid>
            <category><![CDATA[bug-bounty]]></category>
            <category><![CDATA[race-condition]]></category>
            <category><![CDATA[cybersecurity]]></category>
            <category><![CDATA[penetration-testing]]></category>
            <dc:creator><![CDATA[NadSec]]></dc:creator>
            <pubDate>Thu, 09 Oct 2025 06:50:31 GMT</pubDate>
            <atom:updated>2025-10-09T08:01:20.246Z</atom:updated>
            <content:encoded><![CDATA[<h3>👋 Introduction</h3><p>Welcome back friends,<br>This blog is part of my <strong>“Less Effort, More Impact”</strong> series where I share bugs that attackers love because they don’t need rocket science hacking skills — but the results can be huge.</p><p>Today’s story is about <strong>Race Condition Vulnerability</strong>. Sounds fancy, right? But let me explain it in a simple way.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*e5VoCo1T0AOuGlRioeSD1A.png" /></figure><h3>🛒 Real World Example</h3><p>Imagine you’re shopping online on your favorite e-commerce site. You find a ₹500 coupon and apply it while checking out.</p><p>✅ Normally, the system should allow you to use the coupon <strong>only once</strong>.<br> ❌ But what if you find a way to apply the same coupon <strong>multiple times</strong> at lightning speed?</p><p>That’s exactly how a <strong>Race Condition</strong> attack works. The attacker takes advantage of the fact that the system is not handling multiple requests properly when they are processed at the same time.</p><h3>🪜 Steps an Attacker Follows</h3><p>Let’s break it down step by step:</p><ol><li>🔍 <strong>Find a vulnerable action</strong></li></ol><ul><li>For example: coupon redemption, wallet transfer, ticket booking, or password reset.</li></ul><p>2.🛠 <strong>Capture the request in Burp Suite</strong></p><ul><li>The attacker intercepts the request where the coupon is being applied.</li></ul><p>3.🧩 <strong>Duplicate the request multiple time</strong></p><ul><li>Burp Suite has a feature called <strong>Intruder → Pitchfork / Cluster Bomb</strong> or the newer <strong>Turbo Intruder extension</strong>.</li><li>These allow sending <strong>multiple requests in parallel</strong> almost at the same time.</li></ul><p>4.⚡ <strong>Send all requests simultaneously</strong></p><ul><li>If the system does not lock the process properly, multiple requests succeed.</li><li>Example: Coupon of ₹500 applied 10 times = ₹5000 discount 😱</li></ul><p>5.💸 <strong>Enjoy the reward</strong></p><ul><li>Attacker walks away with a huge discount, free items, or even money transfers.</li></ul><h3>🚦 Why This Happens</h3><p>Race conditions happen when:</p><ul><li>The application doesn’t handle <strong>concurrent requests</strong> properly.</li><li>There’s no proper <strong>locking mechanism</strong> in the backend.</li><li>Developers assume users will only click once and don’t expect attackers to send 100 clicks in one second.</li></ul><h3>🔑 Real-World Impact</h3><ul><li>Free coupons redeemed unlimited times.</li><li>Bank transfers made more than the actual balance.</li><li>Airline or event tickets booked multiple times with one payment.</li></ul><p>These bugs can lead to <strong>massive financial loss</strong> and are often rewarded heavily in bug bounty programs.</p><h3>🛡️ How Developers Can Prevent It</h3><ul><li>Use <strong>atomic transactions</strong> in the backend.</li><li>Implement <strong>unique coupon codes</strong> that expire instantly after use.</li><li>Add <strong>server-side locking</strong> so only one request is processed at a time.</li><li>Never rely only on the front-end button disabling.</li></ul><h3>✨ Conclusion</h3><p>Race Condition bugs prove that sometimes <strong>speed is the real enemy</strong>. For an attacker, it’s just about sending requests fast enough and tricking the system into processing them before it realises something’s wrong.</p><p>For us learners, this is a perfect example of how <strong>Less Effort can create More Impact</strong> in cybersecurity.</p><p>💡 <strong>Pro Tip for Learners:</strong><br> If you’re practising with labs (like PortSwigger Web Academy), always try <strong>sending multiple requests parallelly in Burp Suite</strong> — you’ll see how powerful this attack can be.</p><p>🔥 That’s it for today’s story. If you liked this blog, stay tuned — I’ll be sharing more bugs from my <strong>Less Effort, More Impact</strong> series.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=69315f95b13c" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[️ The Broken Link Jackpot: How a 404 Can Become a Security Goldmine!]]></title>
            <link>https://medium.com/@somnadh0000/%EF%B8%8F-the-broken-link-jackpot-how-a-404-can-become-a-security-goldmine-16ac517fccda?source=rss-80780c4794f4------2</link>
            <guid isPermaLink="false">https://medium.com/p/16ac517fccda</guid>
            <category><![CDATA[penetration-testing]]></category>
            <category><![CDATA[bug-bounty]]></category>
            <category><![CDATA[vapt]]></category>
            <category><![CDATA[cybersecurity]]></category>
            <category><![CDATA[web-application-security]]></category>
            <dc:creator><![CDATA[NadSec]]></dc:creator>
            <pubDate>Wed, 17 Sep 2025 06:46:29 GMT</pubDate>
            <atom:updated>2025-09-17T06:46:29.535Z</atom:updated>
            <content:encoded><![CDATA[<h3>👋 Introduction</h3><p>Welcome back, friends!<br> This is the <strong>Second</strong> <strong>post</strong> in my series <strong>“Less Effort, More Impact”</strong>, where I share vulnerabilities that look small but can cause <strong>huge consequences</strong>.</p><p>So far, we’ve explored:<br> 1️⃣ <strong>When a Header Turns Hostile: Host Header Injection</strong></p><p>Now, let’s dive into a bug that feels almost too simple to be dangerous — <strong>Broken Link Hijacking</strong>.</p><h3>🐞 The Bug</h3><p>We all know websites love to add links in their <strong>footer</strong> — social media, documentation, mobile app store links, and more.</p><p>But what happens when one of those links is no longer valid? 🤔</p><p>That’s where <strong>Broken Link Hijacking</strong> comes in.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*8PfNDuSWpmmuPRC289Iwhw.jpeg" /></figure><h3>🔗 Broken Link Hijacking Explained</h3><p>Here’s the idea:</p><p>👉 A website links to an external page (say, a Google Play app).<br>👉 Over time, that link becomes invalid — maybe the app is deleted, or the username changes.<br>👉 Attackers notice the <strong>abandoned link</strong>, claim it, and replace it with their <strong>own malicious content</strong>.<br>👉 Users who trust the official website unknowingly get redirected to malware, phishing pages, or fake apps.</p><p>Simple. Silent. Dangerous. ⚡</p><h3>🔍 Real-World Example</h3><p>Imagine scrolling to a website’s footer and finding:</p><ul><li>✅ <strong>Apple App Store link</strong> → Works fine.</li><li>❌ <strong>Google Play Store link</strong> → Returns a 404 error.</li></ul><p>That broken link could be hijacked by an attacker who publishes a <strong>malicious app</strong> under the same App ID.</p><p>So, the next time users click “Download from Google Play” on the company’s official site, they’re actually downloading malware. 🚨<br> Steps Attackers Use to Exploit It</p><h3>🪜 Steps Attack Use to Exploit It</h3><p>Here’s a simple breakdown of how this attack works:</p><p>1️⃣ <strong>Identify broken links</strong> — Look at the website footer, “Contact us” page, or Wappalyzer scans to spot unused/broken domains or social handles.<br>2️⃣ <strong>Check availability</strong> — See if the domain is expired or if the social handle is available.<br>3️⃣ <strong>Register / Claim it</strong> — The attacker purchases the domain or claims the username.<br>4️⃣ <strong>Hijack traffic</strong> — Now, whenever users click the link from the victim’s website, they land on the attacker-controlled page.<br>5️⃣ <strong>Exploit trust</strong> — The attacker can use this for phishing, malware, scams, or redirecting traffic.</p><h3>💥 Impact</h3><ul><li>🔐 <strong>Phishing &amp; Malware Distribution</strong> — Attackers trick users into installing harmful apps.</li><li>🕵️ <strong>Brand Damage</strong> — The official site indirectly promotes malicious links.</li><li>📉 <strong>Loss of Trust</strong> — Users lose confidence in the company’s digital presence.</li></ul><p>For attackers, this is <strong>low effort → high impact</strong>.</p><h3>🛡 Mitigation</h3><p>✔ <strong>Regularly audit all external links</strong> (social media, app stores, docs).<br>✔ <strong>Automate link monitoring</strong> so broken links get flagged instantly.<br>✔ <strong>Update or remove invalid links</strong> from footers and landing pages.<br>✔ <strong>Use permanent redirects</strong> where possible, instead of hardcoding links.</p><h3>🎯 Conclusion</h3><p>One broken link may look harmless.<br> But in the wrong hands, it can turn into a <strong>security goldmine for attackers</strong>.</p><p>This is why web security is not just about patching servers — it’s about <strong>attention to detail</strong>.</p><p>Stay tuned for the <strong>next post in “Less Effort, More Impact”</strong>, where I’ll share another bug that looks tiny but can cause huge damage.</p><p>💡 If you enjoyed this, share it with your friends and follow along for more <strong>real-world bug stories</strong>.</p><p>Let’s keep learning together. 💻✨</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=16ac517fccda" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[⚡ One Header. One Tweak. 
  And Boom — Can Lead To Account Takeover]]></title>
            <link>https://medium.com/@somnadh0000/one-header-one-tweak-and-boom-can-lead-to-account-takeover-643dcb9ab265?source=rss-80780c4794f4------2</link>
            <guid isPermaLink="false">https://medium.com/p/643dcb9ab265</guid>
            <dc:creator><![CDATA[NadSec]]></dc:creator>
            <pubDate>Tue, 02 Sep 2025 05:07:54 GMT</pubDate>
            <atom:updated>2025-09-02T05:07:54.656Z</atom:updated>
            <content:encoded><![CDATA[<h3>⚡ One Header. One Tweak. <br> 💥 And Boom — Can Lead To Account Takeover</h3><h3>👋 Introduction</h3><p>Hello friends,<br>Welcome to my brand-new series where I’ll share <strong>security bugs that require very little effort but have a massive impact</strong>. These are the kind of vulnerabilities that make you go:</p><blockquote>“Wait, that’s it? So simple?!”</blockquote><p>The goal is simple: <strong>Learn together. Grow together.</strong> 🚀<br>So, let’s kick things off with the <strong>first bug in the series</strong> 👇</p><h3>🐞 First Bug</h3><p>A single <strong>HTTP header</strong> that can flip the entire security model of an application.</p><p>Yes, I’m talking about…<br>🔥 <strong>Host Header Injection</strong> 🔥</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*9GIk-W4wGs-oCgICEyywwA.png" /></figure><h3>🕵️‍♂️ What’s the Host Header Anyway?</h3><p>You’ve probably seen it a thousand times:</p><pre>Host: example.com</pre><p>Looks boring, right?</p><p>But here’s the twist — this tiny header can help an attacker when an app blindly trusts it to build absolute URLs.</p><p>With the right conditions, an attacker could:<br> ✅ Steal <strong>password reset tokens</strong><br> ✅ Perform <strong>cache poisoning</strong><br> ✅ Even bypass <strong>access controls</strong></p><p><strong>One header. One exploit. Big damage.</strong></p><h3>🔍 Step-by-Step Exploit Guide</h3><p>Let’s break it down like a hacker would:</p><h3>✅ Step 1: Find a Password Reset Feature</h3><p>Most apps send an email with a reset link like this:</p><pre>https://example.com/reset?token=1234</pre><h3>✅ Step 2: Intercept the Request</h3><p>Open <strong>Burp Suite</strong> (or any proxy tool) and look for the Host header.<br> It usually looks like this:</p><pre>Host: example.com</pre><h3>✅ Step 3: Modify the Host Header</h3><p>Change it to your evil domain:</p><pre>Host: evil.com</pre><h3>✅ Why Does This Work?</h3><p>Because some apps use the <strong>incoming Host header</strong> directly when generating absolute URLs in emails.</p><p>So, instead of:</p><pre>https://example.com/reset?token=1234</pre><p>The victim receives:</p><pre>https://evil.com/reset?token=1234</pre><h3>✅ Step 4: Profit</h3><p>If the victim clicks that link, the reset token goes to the attacker’s server → attacker can reset the password.</p><p>🎯 <strong>Result? Full Account Takeover.</strong></p><h3>💥 Impact of Host Header Injection</h3><ul><li>🔐 <strong>Account Takeover</strong> — Password reset tokens get stolen.</li><li>🗂 <strong>Cache Poisoning</strong> — serve malicious content if caching depends on Host.</li><li>🔗 <strong>Open Redirect / SSRF</strong> — possible in misconfigured infrastructures.</li></ul><p><strong>Severity:</strong> High <strong>if</strong> password-reset flows, caching, or redirects depend on the Host header. Otherwise, risk is lower but still worth fixing.</p><h3>🛡 Mitigation Steps</h3><p>✔ Don’t trust the Host header for link generation.<br> ✔ Hardcode a canonical base URL (APP_URL) in configs for emails and redirects.<br> ✔ Enable strict allow-lists for Host on the server (reject unknown hosts).<br> ✔ Normalize headers at proxies/load balancers (strip X-Forwarded-Host if unused).<br> ✔ Make reset tokens single-use, short-lived, and context-bound</p><h3>🎯 Key Takeaway</h3><p>One header. One tweak.<br>And boom — <strong>your entire app is compromised</strong>.</p><p>This is why security isn’t just about big exploits. Even the smallest details matter.</p><p>🔥 Stay tuned for the next post in <strong>“Less Effort, More Impact”</strong>, where I’ll share another vulnerability that looks tiny but can break everything.</p><p>👉 Follow me for more <strong>web security tips, tricks, and real-world attack stories</strong>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=643dcb9ab265" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>