<?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 H4cker-Nafeed on Medium]]></title>
        <description><![CDATA[Stories by H4cker-Nafeed on Medium]]></description>
        <link>https://medium.com/@mdnafeed3?source=rss-725a08e6bc90------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*RTREDUDLGhYdLnJJnWqKXA.jpeg</url>
            <title>Stories by H4cker-Nafeed on Medium</title>
            <link>https://medium.com/@mdnafeed3?source=rss-725a08e6bc90------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 18:15:27 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@mdnafeed3/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[From ZIP to Zoho Hall of Fame: How I Found Exposed API Keys !]]></title>
            <link>https://medium.com/@mdnafeed3/from-zip-to-zoho-hall-of-fame-how-i-found-exposed-api-keys-17eeca415474?source=rss-725a08e6bc90------2</link>
            <guid isPermaLink="false">https://medium.com/p/17eeca415474</guid>
            <category><![CDATA[bug-hunting]]></category>
            <category><![CDATA[zoho]]></category>
            <category><![CDATA[cybersecurity]]></category>
            <category><![CDATA[hacking]]></category>
            <category><![CDATA[bug-bounty]]></category>
            <dc:creator><![CDATA[H4cker-Nafeed]]></dc:creator>
            <pubDate>Sat, 28 Jun 2025 13:44:36 GMT</pubDate>
            <atom:updated>2025-06-28T13:59:22.542Z</atom:updated>
            <content:encoded><![CDATA[<h3>From ZIP to Zoho Hall of Fame: How I Found Exposed API Keys !</h3><p><em>I’m Mohammed Nafeed, also known as </em><strong><em>H4cker Nafeed</em></strong><em>. It’s been quite a while since I’ve written any security articles, and I’ve finally decided to publish one. In this article, I’ll be sharing how I discovered two API keys from popular services and how this led to my inclusion in </em><strong><em>Zoho Corporation’s Security Researcher Hall of Fame</em></strong><em>.</em></p><p><em>What is Zoho Corporation, and what does it provide?</em></p><p><em>Zoho Corporation is a tech company that offers a wide range of </em><strong><em>cloud-based business software</em></strong><em>. Its products include tools for </em><strong><em>CRM, email, accounting, project management, and app development</em></strong><em>. Zoho is known for its </em><strong><em>privacy-focused</em></strong><em>, ad-free services and its all-in-one suite, </em><strong><em>Zoho One</em></strong><em>, used by businesses worldwide.</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/736/1*CjwHQF0yf2vqXt-iRzk9cw.jpeg" /><figcaption>Zoho Logo</figcaption></figure><p><em>Before we start hunting on a target company we need to know what does the company provide to its customers, so that we get better idea and understanding.</em></p><p><em>At Zoho, finding security flaws was quite challenging for me since Zoho’s bug bounty program has huge crowd.</em></p><p><strong><em>During my reconnaissance</em></strong><em>, I came across two ZIP files hosted on one of Zoho’s assets. These files were </em><strong><em>publicly accessible</em></strong><em>, so I downloaded them for further analysis.</em></p><p><em>What is a </em><strong><em>ZIP file</em></strong><em>, and why is sensitive information like </em><strong><em>API keys</em></strong><em> &amp; Other Credentials are often stored in it?</em></p><blockquote><em>A ZIP file is a compressed archive that bundles multiple files into one. Sensitive data like API keys &amp; Credentials is stored in ZIP files for convenience, portability, and sometimes to add basic protection (e.g., password or encryption). However, ZIP files alone are not secure and should be used with proper encryption or secure storage methods.</em></blockquote><p><em>I found two ZIP file links, such as:</em></p><ul><li><a href="https://example.zoho.com/download/map.zip">https://*.example.zoho.com/download/YaXydhsi/Gmap.zip</a></li><li><a href="https://example.zoho.com/download/map.zip">https://*.example.zoho.com/download/Oazqxylm/Amap.zip</a></li></ul><p><em>To easily view the contents without extracting them to my local storage, I used an online tool called </em><strong><em>EzyZip</em></strong><em>. This tool allows you to </em><strong><em>unzip or view files — including executables like </em></strong><strong><em>.exe—directly in the browser</em></strong><em>, without downloading or extracting them on your personal computer.</em></p><p><em>Link for EzyZip tool: </em><a href="https://www.ezyzip.com/open-extract-exe-file.html"><em>https://www.ezyzip.com/open-extract-exe-file.html</em></a></p><p><em>When I unzipped the files (</em><em>map.zip and </em><em>amap.zip) using the </em><strong><em>EzyZip</em></strong><em> online tool, I found HTML files named </em><em>Gmap_128801.html and </em><em>Amap_128801.html. After viewing the HTML content, I noticed that both files contained </em><strong><em>API keys</em></strong><em> for the </em><strong><em>Google Maps API</em></strong><em> and </em><strong><em>Amap API</em></strong><em>.</em></p><p><em>Gmap_128801.html:</em></p><blockquote>&lt;script type=”text/javascript” async src=”//maps.googleapis.com/maps/api/js?sensor=false&amp;language=en&amp;key=xxxxxxxxxxxxxxx&amp;callback=initGMaps&amp;key=xxxxxxxxxxxx&amp;callback=initGMaps”&gt;&lt;/script&gt;</blockquote><p><em>Amap_128801.html:</em></p><blockquote>&lt;script type=”text/javascript” id=”mapAPI” src=”<a href="https://webapi.amap.com/maps?v=2.0&amp;key=xxxxxxxxxxxx">https://webapi.amap.com/maps?v=2.0&amp;key=xxxxxxxxxxxx</a>xx&quot;&gt;&lt;/script&gt;<br>&lt;script src=”<a href="https://webapi.amap.com/ui/1.1/main.js">https://webapi.amap.com/ui/1.1/main.js</a>&quot;&gt;&lt;/script&gt;</blockquote><h4><em>Testing the Keys Before Reporting:</em></h4><p><em>Since these keys were exposed publicly, and direct reporting without confirming impact is not ideal, I decided to test their potential for misuse. One key was for the </em><strong><em>Google Maps API</em></strong><em>, and the other belonged to </em><strong><em>Amap</em></strong><em>, a map service based in China.</em></p><p><em>To assess the </em><strong><em>Google Maps API key</em></strong><em>, I used a tool called </em><strong><em>Gmaps API Scanner</em></strong><em>, which can test API keys for vulnerabilities such as unrestricted access to paid services (like geolocation, geocoding, or billing-related endpoints).</em></p><p><em>The tool is available here: </em><a href="https://github.com/ozguralp/gmapsapiscanner"><em>https://github.com/ozguralp/gmapsapiscanner</em></a></p><p><em>After scanning the </em><strong><em>Google Maps API key</em></strong><em> with the </em><a href="https://github.com/ozguralp/gmapsapiscanner"><em>Gmaps API Scanner</em></a><em>, the tool reported that the key is </em><strong><em>not vulnerable</em></strong><em>. This means it likely has </em><strong><em>usage restrictions</em></strong><em> in place and cannot be exploited for unauthorized access to paid Google Maps services.</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/612/1*dGryzjPRwyyjGH7TGF7xfQ.png" /><figcaption>Not Vulnerable</figcaption></figure><p><em>It says the provided API key is expired but its not, sometimes we need to do manual check.</em></p><p><em>To confirm the result manually, I created a </em><strong><em>simple HTML file</em></strong><em> using the exposed API key to test if the map renders or allows access to any services in a browser.</em></p><pre>&lt;!DOCTYPE html&gt;<br>&lt;html&gt;<br>  &lt;head&gt;<br>    &lt;title&gt;Google Maps API Test&lt;/title&gt;<br>    &lt;script async defer<br>      src=&quot;https://maps.googleapis.com/maps/api/js?key=XXXXXXXXXXXX&amp;callback=initMap&quot;&gt;<br>    &lt;/script&gt;<br>    &lt;script&gt;<br>      function initMap() {<br>        var location = { lat: 37.7749, lng: -122.4194 };<br>        var map = new google.maps.Map(document.getElementById(&#39;map&#39;), {<br>          zoom: 12,<br>          center: location<br>        });<br>        new google.maps.Marker({ position: location, map: map });<br>      }<br>    &lt;/script&gt;<br>  &lt;/head&gt;<br>  &lt;body&gt;<br>    &lt;h3&gt;Google Map Test&lt;/h3&gt;<br>    &lt;div id=&quot;map&quot; style=&quot;height:500px;width:100%;&quot;&gt;&lt;/div&gt;<br>  &lt;/body&gt;<br>&lt;/html&gt;</pre><p><em>Replace the API Key and save it in (</em><strong><em>.html</em></strong><em>) format and open it using browser.</em></p><p><em>The map </em><strong><em>did render successfully</em></strong><em>, indicating that the API key is valid. However, it did </em><strong><em>not allow access to any premium features or restricted endpoints</em></strong><em>, which confirms that the key is </em><strong><em>not exploitable</em></strong><em> for abuse or unauthorized billing and its only for developing purpose.</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*2nwvRUCcLDplD6rFkH1nsg.png" /><figcaption>Google Map</figcaption></figure><p><em>Just like I did with the Google Maps API key, I decided to verify the </em><strong><em>Amap API key</em></strong><em> by writing a simple HTML script to test if the map loads and whether the key has any usage restrictions.</em></p><pre>&lt;!DOCTYPE html&gt;<br>&lt;html&gt;<br>  &lt;head&gt;<br>    &lt;meta charset=&quot;utf-8&quot;&gt;<br>    &lt;title&gt;Amap API Test&lt;/title&gt;<br>    &lt;script src=&quot;https://webapi.amap.com/maps?v=2.0&amp;key=XXXXXXXXXXXXX&quot;&gt;&lt;/script&gt;<br>    &lt;script&gt;<br>      function initMap() {<br>        var map = new AMap.Map(&quot;container&quot;, {<br>          zoom: 10,<br>          center: [116.397428, 39.90923] // Beijing coordinates<br>        });<br>      }<br>      window.onload = initMap;<br>    &lt;/script&gt;<br>    &lt;style&gt;<br>      #container { width: 100%; height: 500px; }<br>    &lt;/style&gt;<br>  &lt;/head&gt;<br>  &lt;body&gt;<br>    &lt;h3&gt;Amap API Key Test&lt;/h3&gt;<br>    &lt;div id=&quot;container&quot;&gt;&lt;/div&gt;<br>  &lt;/body&gt;<br>&lt;/html&gt;</pre><p><em>The Amap key also </em><strong><em>rendered the map successfully</em></strong><em>, showing that the key is </em><strong><em>valid </em></strong><em>and its not for development use.</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*iWGtPFkvkUWLd54msfKbpA.png" /><figcaption>China Map Service</figcaption></figure><p><em>After validating the exposure of the API keys through my own testing, I responsibly reported the issue to </em><strong><em>Zoho Corporation</em></strong><em> via their </em><strong><em>bug bounty program</em></strong><em>.</em></p><p><em>Initially, they acknowledged the report and began investigating. A day later, I received an official response (see image below) explaining the cause and their action:</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/907/1*LVdZJJBDwW7N3xrro_pMfA.png" /></figure><p><em>The exposed API keys were intended solely for internal development use. Billing was not enabled, and the Google Maps key was restricted to development-only access.</em></p><p><em>The inclusion of these keys in a ZIP file was unintentional, occurring during the packaging process. Following the report, the team promptly removed the ZIP files, revoked the exposed keys, and confirmed that no sensitive data or production systems were affected.</em></p><p><em>Since the issue posed minimal risk and had no financial impact, it was classified as low severity. Although no monetary bounty was awarded, the report was acknowledged, and recognition was offered in their </em><strong><em>Hall of Fame</em></strong><em>.</em></p><p><strong><em>Thank you for taking the time to read my article.</em></strong><em><br>I appreciate your interest, and I hope it provided some useful insights into responsible disclosure and API key security.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=17eeca415474" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[This Is How I Bypassed The Most Critical Security Check!]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://medium.com/@mdnafeed3/this-is-how-i-bypassed-the-most-critical-security-check-00e9ba525ebc?source=rss-725a08e6bc90------2"><img src="https://cdn-images-1.medium.com/max/735/1*zBZGaHR-lTxTqeRJtmfuhw.jpeg" width="735"></a></p><p class="medium-feed-snippet">Look at How a Hacker Can Think Outside the Box!</p><p class="medium-feed-link"><a href="https://medium.com/@mdnafeed3/this-is-how-i-bypassed-the-most-critical-security-check-00e9ba525ebc?source=rss-725a08e6bc90------2">Continue reading on Medium »</a></p></div>]]></description>
            <link>https://medium.com/@mdnafeed3/this-is-how-i-bypassed-the-most-critical-security-check-00e9ba525ebc?source=rss-725a08e6bc90------2</link>
            <guid isPermaLink="false">https://medium.com/p/00e9ba525ebc</guid>
            <category><![CDATA[bug-bounty]]></category>
            <category><![CDATA[bug-bounty-tips]]></category>
            <category><![CDATA[cybersecurity]]></category>
            <category><![CDATA[hacking]]></category>
            <category><![CDATA[technology]]></category>
            <dc:creator><![CDATA[H4cker-Nafeed]]></dc:creator>
            <pubDate>Mon, 23 Dec 2024 15:28:15 GMT</pubDate>
            <atom:updated>2024-12-23T15:28:15.902Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[Find Open Redirect in Just 2 min - $1000]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://medium.com/@mdnafeed3/find-open-redirect-in-just-2-min-1000-c527bb3e65fb?source=rss-725a08e6bc90------2"><img src="https://cdn-images-1.medium.com/max/850/1*f5hHDpnDE-hHG-7J1DbrHA.png" width="850"></a></p><p class="medium-feed-snippet">The Secrets of Web Application Security Vulnerabilities!</p><p class="medium-feed-link"><a href="https://medium.com/@mdnafeed3/find-open-redirect-in-just-2-min-1000-c527bb3e65fb?source=rss-725a08e6bc90------2">Continue reading on Medium »</a></p></div>]]></description>
            <link>https://medium.com/@mdnafeed3/find-open-redirect-in-just-2-min-1000-c527bb3e65fb?source=rss-725a08e6bc90------2</link>
            <guid isPermaLink="false">https://medium.com/p/c527bb3e65fb</guid>
            <category><![CDATA[cybersecurity]]></category>
            <category><![CDATA[bug-bounty]]></category>
            <category><![CDATA[bug-bounty-tips]]></category>
            <dc:creator><![CDATA[H4cker-Nafeed]]></dc:creator>
            <pubDate>Tue, 29 Oct 2024 13:32:32 GMT</pubDate>
            <atom:updated>2024-10-29T13:33:46.852Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[Exploiting Open Redirection $1000]]></title>
            <link>https://medium.com/@mdnafeed3/how-about-exploiting-open-redirection-how-base64-encoding-can-uncover-hidden-vulnerabilities-cb5beb11b763?source=rss-725a08e6bc90------2</link>
            <guid isPermaLink="false">https://medium.com/p/cb5beb11b763</guid>
            <category><![CDATA[cybersecurity]]></category>
            <category><![CDATA[web3]]></category>
            <category><![CDATA[infosec]]></category>
            <category><![CDATA[hacking]]></category>
            <category><![CDATA[bug-bounty]]></category>
            <dc:creator><![CDATA[H4cker-Nafeed]]></dc:creator>
            <pubDate>Mon, 29 Jul 2024 14:25:14 GMT</pubDate>
            <atom:updated>2024-07-29T14:48:57.194Z</atom:updated>
            <content:encoded><![CDATA[<p><em>Hello guys, I am Md Nafeed. Welcome back to my new article. I hope your are doing fine !</em></p><p><em>Just have a smile and start reading this amazing article.</em></p><p><em>In this article, we are going to see an interesting vulnerability known as Open Redirection.</em></p><p><em>Question: What is Open Redirection?</em></p><p><em>Answer: Open Redirection is a web application vulnerability that occurs when a web application or server improperly processes URLs, allowing attackers to redirect users to a different, potentially malicious website. This can lead to phishing attacks, where users are tricked into entering sensitive information on a fraudulent site, or other types of attacks that exploit the user&#39;s trust in the original website.</em></p><p><em>So let&#39;s see how I found an Open Redirection vulnerability in a big organization.</em></p><p><em>So I used to keep an alarm every day at 3 AM, and most of the time, I hunt bugs at that time as the entire town will be silent and my brain will start braining ! Just kidding LOL.</em></p><p><em>I started to hunt, and the first part I always do is to check the website&#39;s functionality, but there was nothing interesting.</em></p><p><em>Basically, I don&#39;t like webpages that don&#39;t have enough functions like login and signup. So, I started to go deep inside the website and began subdomain enumeration.</em></p><p><em>Happy to see that there were a total of 30+ subdomains, and I was opening and checking every page, but nothing found interesting; there was no login or signup to go deep.</em></p><p><em>And at last, I found a subdomain that had a login function and a signup function.</em></p><p><em>So, I did signup and logged into the website.</em></p><p><em>I started checking the functions, but the website&#39;s function was not like I expected. So, I checked the signout option, and when I clicked the signout option, I saw the URL was different from normal, showing like this:</em></p><p><strong><em>https://sub.example.com/auth/realms/example/protocol/openid-connect/logout?post_logout_redirect_uri=aHR0cHM6Ly9tYWluLmV4YW1wbGUuY29tL2xvZ291dA==</em></strong></p><p><em>When I saw this URL, I realized it was encoded in Base64 to confuse users. The developer encoded the URL to make it less understandable to anyone. But I know how developers use this type of encoding to appear more professional. However, they don&#39;t realize that we are more professional than them.</em></p><p><em>So I decoded the URL and found the secret:</em></p><p><em>After Decoding the URL looked like this</em></p><p>```</p><p><strong><em>https://sub.example.com/auth/realms/example/protocol/openid-connect/logout?post_logout_redirect_uri=https://main.example.com/logout</em></strong></p><p>```</p><p><em>We can clearly see that how developer hided the redirecting domain with base64 encoding.</em></p><p><em>Here the affected parameter was `post_logout_redirect_uri`.</em></p><p><em>So now I changed the redirecting URL to:</em></p><p><strong><em>https://sub.example.com/auth/realms/example/protocol/openid-connect/logout?post_logout_redirect_uri=https://evil.com/logout</em></strong></p><p><em>Here, `evil.com` is a malicious site which I am instructing the website to redirect.</em></p><p><em>And again I encoded the redirecting URL to Base64 which looks like this.</em></p><p><strong><em>https://sub.example.com/auth/realms/example/protocol/openid-connect/logout?post_logout_redirect_uri=aHR0cHM6Ly9ldmlsLmNvbS9sb2dvdXQ=</em></strong></p><p><em>So basically, developers use this type of redirection to take users to the main domain after every successful logout.</em></p><p><em>Then when I logged out, To my surprise, it logged out and redirected to `evil.com`.</em></p><p><em>So, an attacker can send these URLs to any user to lead them to a malicious website, which, being a subdomain of the main domain, looks legitimate.</em></p><p><em>Question: Why did this happen?</em></p><p><em>Answer: This happened because the application improperly validates the `post_logout_redirect_uri` parameter. Instead of restricting redirects to trusted domains, the application allows any URL to be specified, including malicious sites. As a result, attackers can manipulate the redirect URL to point to a site they control, potentially leading users to a malicious destination after logging out.</em></p><p><em>What is the impact of this vulnerability?</em></p><p><em>The impact of this vulnerability can be significant:</em></p><p><em>1. Phishing Attacks: Attackers can use the open redirection to trick users into visiting a malicious site that appears to be legitimate, potentially leading to phishing attacks and the theft of sensitive information.</em></p><p><em>2. Credential Theft: Users might be redirected to fake login pages that mimic the legitimate site&#39;s interface, increasing the risk of credential theft.</em></p><p><em>3. Trust Erosion: Such vulnerabilities can erode trust in the affected website, as users may question the security and integrity of the platform.</em></p><p><em>4. Session Hijacking: Attackers can exploit this vulnerability to steal session cookies or tokens by redirecting users to a site controlled by the attacker, where they might capture session data.</em></p><p><em>Thank you for your time.</em></p><p>Please give me your feedback in comments.</p><p><em>Also follow me on social media to learn and grow together.</em></p><p><em>Instagram: </em><a href="https://www.instagram.com/h4cker_nafeed"><em>https://www.instagram.com/h4cker_nafeed</em></a></p><p><em>LinkedIn: </em><a href="https://www.linkedin.com/in/mohammed-nafeed-62a716250"><em>https://www.linkedin.com/in/mohammed-nafeed-62a716250</em></a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=cb5beb11b763" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Bypassing Input Validation  $0 - $1000]]></title>
            <link>https://medium.com/@mdnafeed3/bypassing-input-validation-0-1000-799682d547ba?source=rss-725a08e6bc90------2</link>
            <guid isPermaLink="false">https://medium.com/p/799682d547ba</guid>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[infosec]]></category>
            <category><![CDATA[cybersecurity]]></category>
            <category><![CDATA[bug-bounty]]></category>
            <dc:creator><![CDATA[H4cker-Nafeed]]></dc:creator>
            <pubDate>Tue, 02 Jul 2024 03:46:08 GMT</pubDate>
            <atom:updated>2024-07-02T03:46:08.623Z</atom:updated>
            <content:encoded><![CDATA[<h3>Bypassing Input Validation $0 - $1000</h3><p><em>Welcome back to my new article! I’m Mohammed Nafeed, a bug bounty hunter.</em></p><p><em>So today, we’re going to explore an intriguing vulnerability that many bug hunters tend to overlook &amp; It is nothing but an input validation bypass.</em></p><p><em>What is Input Validation ?</em></p><p><em>Input validation is the process of checking user-provided data to ensure it meets required formats and constraints. It’s essential for security, preventing issues like SQL injection, cross-site scripting (XSS), buffer overflow, command injection, and directory traversal.</em></p><p><em>Many bug hunters, when they usually test websites and come to the registration or sign-up page, if the website doesn’t allow special characters in the first name or elsewhere, they usually log in using normal words for further testing. But wait, why the hurry there? It’s like you are leaving a vulnerability and going to test another vulnerability which might become a duplicate after reporting…LoL…just for fun But take it serious!</em></p><p><em>As a bug hunter, it’s essential to test every endpoint and functionality, especially during manual testing. When using XSS payloads or other exploits, they often contain special characters like `&lt;`, `&gt;`, `/`, `\`, `*`, `{`, `}`, and `#`. If you try to use these in input fields like first name, last name, or any other, and the validation fails with an error stating that special characters are not allowed, it’s an indication that the input validation process is in place.</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*pq7tEAFZOAalVgwL6NB3LQ.png" /><figcaption>Input Validation Check Point</figcaption></figure><p><em>Now let’s go deep into how to bypass this restriction.</em></p><p><em>What is Input Validation Bypass ?</em></p><p><em>Input validation bypass is a technique used to circumvent the security measures that check user input for proper formatting and content. This can lead to serious vulnerabilities such as SQL injection, XSS, remote code execution, and command injection. It is crucial to ensure that input validation is robust to prevent data corruption, system crashes, and security breaches.</em></p><p><em>When a normal input validation bypass occurs without any impact, it’s typically considered low or informational. However, if it can be chained with other vulnerabilities such as SQL injection, XSS, or RCE (remote code execution), the severity escalates from high to critical levels.</em></p><p><em>Some Normal Technique To Bypass Include :</em></p><ul><li><strong><em>Encoding and Decoding</em></strong><em>: Using different encoding techniques (URL encoding, Base64 encoding) to bypass filters that are designed to block special characters.</em></li><li><strong><em>Whitespace Injection</em></strong><em>: Inserting spaces, tabs, or newlines to bypass validation checks that don’t account for whitespace.</em></li><li><strong><em>Null Byte Injection</em></strong><em>: Using null bytes (</em><em>%00) to terminate strings early and bypass validation checks.</em></li><li><strong><em>Character Encoding Manipulation</em></strong><em>: Employing different character encodings or Unicode characters that may not be properly validated or filtered.</em></li><li><strong><em>HTML Entity Encoding</em></strong><em>: Using HTML entities (</em><em>&amp;lt;, </em><em>&amp;gt;, </em><em>&amp;amp;) to bypass filters that block specific characters.</em></li><li><strong><em>Unicode Encoding</em></strong><em>: Using Unicode representations of characters to bypass filters that are not Unicode-aware.</em></li><li><strong><em>Double Encoding</em></strong><em>: Encoding characters twice to bypass filters that only decode once.</em></li><li><strong><em>Using Escape Sequences</em></strong><em>: Employing escape sequences like </em><em>\x or </em><em>\u to bypass input validation.</em></li></ul><p><em>Now here comes the secret part: bypassing the input validation where many bug hunters aren’t familiar.</em></p><p><em>So, when you enter the payload or links in the input field, the system typically rejects them due to special character restrictions. However, using Burp Suite, you can intercept and submit the signup or registration form. Once the request is successfully captured, send it to Burp Repeater for testing. Turn off interception, navigate to the captured request in Burp Repeater, and then manipulate the request as needed for further testing.</em></p><pre>POST /signup HTTP/1.1<br>Host: example.com<br>User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:99.0) Gecko/20100101 Firefox/99.0<br>Accept: text/html,application/xhtml+xml,application/xml;q=0.9,image/webp,*/*;q=0.8<br>Accept-Language: en-US,en;q=0.5<br>Accept-Encoding: gzip, deflate<br>Content-Type: application/x-www-form-urlencoded<br>Content-Length: [length]<br><br>first_name= md<br>last_name= nafeed<br>address= 403 area-51 USA <br>email=test@example.com</pre><p><em>your request normally looks like this.</em></p><p><em>Now manipulate the request like</em></p><pre>POST /signup HTTP/1.1<br>Host: example.com<br>User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:99.0) Gecko/20100101 Firefox/99.0<br>Accept: text/html,application/xhtml+xml,application/xml;q=0.9,image/webp,*/*;q=0.8<br>Accept-Language: en-US,en;q=0.5<br>Accept-Encoding: gzip, deflate<br>Content-Type: application/x-www-form-urlencoded<br>Content-Length: [length]<br><br>first_name= https://evil.com<br>last_name= &lt;script&gt;alert(&#39;XSS&#39;)&lt;/script&gt;<br>address= /etc/passwd<br>email=test@example.com</pre><p><em>Now send the request to the server and see thew result. if the website is vulnerable to this manipulation then you did a input validation bypass using this technique.</em></p><p><em>If the server response is 400 bad request or anything try to change POST TO GET or GET to POST method.</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*MP1B11fPDkuw4NHfHae0rA.jpeg" /><figcaption>Input Validation Bypass To Open Redirection</figcaption></figure><p><em>Why this happens?</em></p><p><em>This happens mainly because the developer has implemented front-side input validation checks but not server-side checks. So, when you send the modified data to the server, you have already bypassed the front check .</em></p><p><em>By doing this, we are breaking the developer’s logic. The developer assumes that front-side checks are sufficient, thinking that no one can add payloads to exploit other vulnerabilities.</em></p><p><em>But some developers don’t realize that they should also implement server-side checks.</em></p><p><em>Note: When you enter special characters in the signup page, client-side validation (like JavaScript) blocks them, saying “no special characters.” However, when you capture the request with Burp Suite, add special characters to fields like `first_name`, and resend it, you get a 200 OK response. This happens because the server lacks proper server-side validation to block these characters, making it a security vulnerability.</em></p><p><em>So from next time, try using this technique; you never know what vulnerability you might discover, like SQL injection, XSS, LFI, SSTI, etc.</em></p><p><em>Thus you can successfully bypass this type of restriction</em>.</p><p><em>Thank You !</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=799682d547ba" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Bypassing CloudFlare Error 1015: You Are Being Rate Limited]]></title>
            <link>https://medium.com/@mdnafeed3/bypassing-cloudflare-error-1015-you-are-being-rate-limited-f25f4e8f7bb2?source=rss-725a08e6bc90------2</link>
            <guid isPermaLink="false">https://medium.com/p/f25f4e8f7bb2</guid>
            <category><![CDATA[bug-bounty]]></category>
            <category><![CDATA[vulnerability]]></category>
            <category><![CDATA[cybersecurity]]></category>
            <category><![CDATA[hacking]]></category>
            <dc:creator><![CDATA[H4cker-Nafeed]]></dc:creator>
            <pubDate>Tue, 23 Apr 2024 14:16:04 GMT</pubDate>
            <atom:updated>2024-04-25T02:55:52.256Z</atom:updated>
            <content:encoded><![CDATA[<h3>Bypassing CloudFlare Security In Just 2 Clicks $100</h3><p><em>Welcome back to my new article! I’m Mohammed Nafeed, a bug bounty hunter.</em></p><p><em>Bug hunting is an exciting and challenging field that involves finding and reporting vulnerabilities in software, websites, and applications.</em></p><p><em>What is Rate Limit Attack?</em></p><p><em>Answer: A rate limit attack is when an attacker floods a system with a high volume of requests to exhaust its resources or cause it to slow down, making it unavailable for legitimate users.</em></p><p><em>For example sending of unlimited verification code to any user globally leads to spam their inbox.</em></p><p><em>Let’s dive into my recent experience with website testing. I was conducting tests on a particular website and decided to try a rate limit attack. To my surprise, the attack was successful, allowing me to send over 1000+ Gmail verification codes to any user. However, as soon as I exceeded 100 requests, Cloudflare’s security measures kicked in, displaying an “Error 1015: You Are Being Rate Limited.”</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*X55ZLLyV63XItZQ7sDanNg.png" /><figcaption>Cloudflare Blockage Error 1015</figcaption></figure><p><em>This Cloudflare blockage prevented me from taking any further actions on the website. At this point, I was faced with a challenge. Being blocked by Cloudflare’s firewall security was a roadblock, but with my bug hunting experience, I decided to think outside the box. I started to experiment with the URL, testing for case sensitivity vulnerabilities.</em></p><p><em>I tried manipulating the URL by changing the case of certain letters, such as converting uppercase (A) to lowercase (a). This approach was based on the idea that some web servers and firewalls might treat URLs differently based on case sensitivity. To my surprise, this tactic worked, and I was able to bypass the rate limit restriction.</em></p><p><em>Normal URL:</em></p><p><a href="https://www.example.com/web/Participant/profile/ChangePassword.aspx"><em>https://www.example.com/web/Participant/profile/ChangePassword.aspx</em></a></p><p><em>Bypassed URL:</em></p><p><a href="https://www.example.com/web/Participant/profile/changePassword.aspx"><em>https://www.example.com/web/Participant/profile/changepassword.aspx</em></a></p><p><em>What is Case Sensitive Vulnerability?</em></p><p><em>A case-sensitive vulnerability occurs when an application or system does not treat uppercase and lowercase characters as distinct. This can lead to security issues because an attacker can manipulate the input case to bypass authentication, access unauthorized data, or perform other malicious activities. For example, if a system checks passwords in a case-insensitive manner, an attacker could enter a password with different cases to gain unauthorized access. Proper handling of case sensitivity is essential to ensure the security and integrity of applications and systems.</em></p><p><em>This experience highlighted the importance of thorough testing and thinking creatively when it comes to bug hunting. It’s not always about finding a direct vulnerability; sometimes, it’s about understanding how different components interact and finding unconventional ways to exploit or bypass security measures.</em></p><p><em>In the world of bug bounty hunting, every challenge presents an opportunity to learn and improve. This incident served as a reminder of the importance of persistence, creativity, and continuous lear</em>ning <em>in the field of cybersecurity.</em></p><p><em>So, the next time when you see an error or a rate limit message on a website, try switching things up a bit. You never know what you might find!</em></p><p><em>Proof of Concept:</em></p><p><a href="https://drive.google.com/file/d/1Q4uERdBPd8vW6_FQPM9SnRBortmufRFt/view?usp=drivesdk"><em>https://drive.google.com/file/d/1Q4uERdBPd8vW6_FQPM9SnRBortmufRFt/view?usp=drivesdk</em></a></p><p><em>If the above video link doesn’t work kindly message me on Instagram.</em></p><p><em>Thank You….</em></p><p><em>Follow me on -</em></p><p><em>Instagram: </em><a href="https://www.instagram.com/h4cker_nafeed/"><em>https://www.instagram.com/h4cker_nafeed/</em></a></p><p><em>LinkedIn: </em><a href="https://www.linkedin.com/in/mohammed-nafeed-62a716250/"><em>https://www.linkedin.com/in/mohammed-nafeed-62a716250/</em></a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f25f4e8f7bb2" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA["From Legit to Lure: Transforming a Website into an Amazon Phishing Site"]]></title>
            <link>https://medium.com/@mdnafeed3/unveiling-a-stored-xss-vulnerability-example-com-under-the-spotlight-37d0895cebca?source=rss-725a08e6bc90------2</link>
            <guid isPermaLink="false">https://medium.com/p/37d0895cebca</guid>
            <category><![CDATA[bug-bounty]]></category>
            <category><![CDATA[cybersecurity]]></category>
            <dc:creator><![CDATA[H4cker-Nafeed]]></dc:creator>
            <pubDate>Sun, 31 Mar 2024 17:50:07 GMT</pubDate>
            <atom:updated>2024-04-03T08:30:45.406Z</atom:updated>
            <content:encoded><![CDATA[<h3>&quot;From Legit to Lure: Transforming a Website into an Amazon Phishing Site&quot; (example.com)</h3><p><strong>“Hello friend”,</strong>I’m Mohammed Nafeed, a web application hacker (bug hunter) and a tech enthusiast. I’m passionate about exploring the digital realm, uncovering vulnerabilities, and improving web security. Being a tech guy allows me to dive deep into the intricacies of technology, constantly learning and adapting to the ever-evolving technology. If you have any questions or need assistance with anything related to web security or technology, feel free to reach out!</p><p>In this blog, I’m concealing the website’s identity due to its Vulnerability Disclosure Policy (VDP). That’s why I’ve used “example.com” as a reference.</p><p><strong>QUOTES:</strong></p><p><strong>“A bug is never just a mistake. It represents something bigger. An error of thinking. That makes you who you are.” — Elliot Alderson, Mr. Robot</strong></p><p><strong>“A bug is a feature waiting to happen.” — Md Nafeed</strong></p><p><strong>Question: What is a stored XSS vulnerability?</strong></p><p>Answer: A stored XSS (Cross-Site Scripting) vulnerability is a type of security flaw in web applications where malicious scripts are injected into the application’s database or storage. These scripts are then retrieved and executed by unsuspecting users when they visit the affected page or interact with the compromised content. Unlike reflected XSS, where the malicious script is immediately executed upon visiting a crafted URL, in stored XSS, the payload persists on the server, posing a persistent threat to all users who access the compromised page or data. This type of vulnerability can be exploited to steal sensitive information, hijack user sessions, deface websites, or perform other malicious actions, making it a significant risk to web application security.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ghZCV7kPlfS2RgQ9opw70A.png" /><figcaption>STORED CROSS-SITE-SCRIPTING</figcaption></figure><p><strong>Your wait is over Lets get started,</strong></p><p>“So, before we get started, I want to share that I’ve also discovered an IDOR (Insecure Direct Object Reference) vulnerability in NASA. This flaw allows me to access sensitive PDF files revealing their upcoming future projects and more. However, due to NASA’s VDP (Vulnerability Disclosure Policy), I’m unable to disclose it publicly.”</p><p>I received a token of appreciation from NASA for uncovering this vulnerability.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*n7VxHf7MkzWCLdPETJA36w.jpeg" /><figcaption>Token of appreciation from NASA</figcaption></figure><p><strong>My Journey: Discovering a Stored XSS Vulnerability,</strong></p><p>During my bug hunting assessment, I came across an intriguing website whose primary function is to optimize image resolution, making a significant impact worldwide. As I peaked into the website’s functionality, I noticed an option to upload files. As a bug hunter, this likely sparks an idea in your mind. But what’s the idea? Well, here’s the kicker: uploading an XSS payload disguised as an SVG file. Upon uploading the SVG file and opening the image in a new tab, the unexpected happens — a popup appears, proclaiming “hacked by mdnafeed.”</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*5vIe4hfDt1UcQLd_KYVRAA.jpeg" /><figcaption>WEBSITE’S FUNCTIONALITY</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*4bD55XD8XbzvWF5jkzv05Q.png" /><figcaption>XSS POP UP</figcaption></figure><p>Below is a basic example of an SVG file containing an XSS payload:</p><pre>&lt;?xml version=&quot;1.0&quot; standalone=&quot;no&quot;?&gt;<br>&lt;!DOCTYPE svg PUBLIC &quot;-//W3C//DTD SVG 20010904//EN&quot;<br> &quot;http://www.w3.org/TR/2001/REC-SVG-20010904/DTD/svg10.dtd&quot;&gt;<br>&lt;svg version=&quot;1.0&quot; xmlns=&quot;http://www.w3.org/2000/svg&quot;<br> width=&quot;2560.000000pt&quot; height=&quot;1600.000000pt&quot; viewBox=&quot;0 0 2560.000000 1600.000000&quot;<br> preserveAspectRatio=&quot;xMidYMid meet&quot; onload=&quot;alert(&#39;hacked by mdnafeed&#39;)&quot;&gt;<br>&lt;metadata&gt;</pre><p><strong>Question: What is an SVG file?</strong></p><p>Answer: An SVG (Scalable Vector Graphics) file is a type of XML-based vector image format used to define graphics for the web. Unlike raster image formats such as JPEG or PNG, which store images as a grid of pixels, SVG files use mathematical equations to describe shapes and lines, allowing them to be scaled without loss of quality. SVG files are commonly used for icons, logos, illustrations, and other graphics on websites and can be manipulated using CSS and JavaScript. They offer advantages such as smaller file sizes, scalability, and accessibility for screen readers and search engines.</p><p>This SVG file, when uploaded to a vulnerable website, could execute the JavaScript code within the &lt;script&gt; tags, resulting in a popup displaying &quot;hacked by mdnafeed&quot;.</p><p>Do we stop here? No, let’s take this XSS to the next level. I utilized another SVG file capable of leaking user cookies from the server side. Finally here we go !!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Tvdg2RS2HPbohqgwaTq1-A.png" /><figcaption>GOT DOCUMENT.COOKIES</figcaption></figure><p>Below is a basic example of an SVG file containing an (Document.Cookies) payload:</p><pre>&lt;?xml version=&quot;1.0&quot; standalone=&quot;no&quot;?&gt;<br>&lt;!DOCTYPE svg PUBLIC &quot;-//W3C//DTD SVG 20010904//EN&quot;<br> &quot;http://www.w3.org/TR/2001/REC-SVG-20010904/DTD/svg10.dtd&quot;&gt;<br>&lt;svg version=&quot;1.0&quot; xmlns=&quot;http://www.w3.org/2000/svg&quot;<br> width=&quot;2560.000000pt&quot; height=&quot;1600.000000pt&quot; viewBox=&quot;0 0 2560.000000 1600.000000&quot;<br> preserveAspectRatio=&quot;xMidYMid meet&quot; onload=&quot;alert(document.cookie)&quot;&gt;<br>&lt;metadata&gt;</pre><p>This SVG file, when uploaded to a vulnerable website, could execute the JavaScript code within the &lt;script&gt; tags, resulting in a popup displaying &quot;Document.cookies”.</p><p>Is everything over? Not quite. Since we’re dealing with a stored XSS, we need to log into the website to upload the files. This rules out the possibility of it being a self-XSS which is less impact. To confirm, I copied the URL of the uploaded image and pasted it into another browser like Chrome. Lo and behold, the popup reappeared with cookies again,confirming that it is indeed a valid stored XSS vulnerability.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*QD0V19M05iUhYTCc9ZVOWw.jpeg" /><figcaption>PASTED URL IN CHROME CONFIRMING THAT ITS A VALID STORED XSS</figcaption></figure><p>Now, whoever clicks on the link, an attacker can steal their cookies and login credentials.</p><p>After reporting my valid stored XSS, considered out of scope, did Nafeed lose the battle? No, Nafeed won’t lose the battle. Taking my hacking skills in a more advanced way, I changed my mind to play a black hat hacker role, and being a black hat for a good reason is not a wrong thing. So, I planned to take down the website with a Amazon phishing scam website.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*3OXz2hAAfEG4F5bSIPbdqw.jpeg" /><figcaption>They considered as out of scope</figcaption></figure><p>&quot;They think they know politics, but they don’t realize I belong to India.&quot;</p><p>Now it’s time to show who I am !!</p><p>Go beyond the alert! — with XSScope</p><p>Go to <a href="https://github.com/kleiton0x00/XSScope">https://github.com/kleiton0x00/XSScope</a> and clone the project.</p><pre>git clone https://github.com/kleiton0x00/XSScope<br>python3 xsscope.py<br></pre><p>A GUI software will open, so go to Main -&gt; Add HTML code<br>A new tab will popup, like in the image below.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*VAOtKZ_c69pWeL5o7FUH3g.jpeg" /><figcaption>XSS Scope</figcaption></figure><p>Now click on “Choose Pre-generated HTML code” and click on which website you like to generate a Phishing Clone. In this case, I will choose “Amazon Login Form”. The whole code will be added into the text box automatically, so click Apply Code.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*EU4HRiLSsDkPs87sOPYZ4Q.jpeg" /><figcaption>Apply code</figcaption></figure><p>Now click on Main -&gt; XSS Payloads and a new window will popup</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ge9ZxwVAQ6y7jO4HKrBWIg.jpeg" /><figcaption>Custom.js</figcaption></figure><p>There will be 10 payloads ready to be deployed, but I’m copying the first payload since onload=&quot;alert(document.cookie)&quot;&gt; worked before.</p><p>Paste the payload into the website and the Phishing Website will be displayed</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*m7pA9lizRDQdLnUV2Yga5g.jpeg" /><figcaption>Created Amazon phishing site</figcaption></figure><p>Now the victim will simply add his credentials into the phishing website.</p><p>The credentials will be stored in /XSScope/login_phishing/credentials/</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*zgcW2UrvAjdrJ3i3K7D1VQ.jpeg" /><figcaption>Credentials captured</figcaption></figure><p>So, finally, I submitted a report, and it was validated. Here’s my conclusion for fellow hackers: always scrutinize website functionalities like file uploads. That’s how I unearthed this vulnerability. Happy hunting!</p><p>&quot;Remember, never give up on yourself. You possess a unique ability that others won’t ever have.&quot;</p><p>Always remember, even the largest companies harbor vulnerabilities; it’s your ingenuity and creativity that uncover them.</p><p><strong>“Make sure to follow me on social media for support and more insights!”</strong></p><p>Instagram: <a href="https://www.instagram.com/h4cker_nafeed/">https://www.instagram.com/h4cker_nafeed/</a></p><p>LinkedIn: <a href="https://www.linkedin.com/in/mohammed-nafeed-62a716250?utm_source=share&amp;utm_campaign=share_via&amp;utm_content=profile&amp;utm_medium=android_app">https://www.linkedin.com/in/mohammed-nafeed-62a716250?utm_source=share&amp;utm_campaign=share_via&amp;utm_content=profile&amp;utm_medium=android_app</a></p><p>Medium: <a href="https://medium.com/@mdnafeed3">https://medium.com/@mdnafeed3</a></p><p>Thank You,</p><p>Regards,</p><p>Md Nafeed (Bug Hunter)</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=37d0895cebca" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>