<?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 WE DO HACKS on Medium]]></title>
        <description><![CDATA[Stories by WE DO HACKS on Medium]]></description>
        <link>https://medium.com/@wedohacks?source=rss-731b888028ba------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*s0I7_YqeCwmrBdxMOS-Gxg.jpeg</url>
            <title>Stories by WE DO HACKS on Medium</title>
            <link>https://medium.com/@wedohacks?source=rss-731b888028ba------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Mon, 16 Nov 2026 20:49:39 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@wedohacks/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[Race Condition Vulnerability | wedohacks | Part 2]]></title>
            <link>https://wedohacks.medium.com/race-condition-vulnerability-wedohacks-part-2-140838fee1a4?source=rss-731b888028ba------2</link>
            <guid isPermaLink="false">https://medium.com/p/140838fee1a4</guid>
            <dc:creator><![CDATA[WE DO HACKS]]></dc:creator>
            <pubDate>Sun, 10 Nov 2024 17:42:20 GMT</pubDate>
            <atom:updated>2024-11-10T17:42:20.203Z</atom:updated>
            <content:encoded><![CDATA[<p>Part 1 : <a href="https://medium.com/@wedohacks/race-condition-vulnerability-wedohacks-ceae59b96e8a">https://medium.com/@wedohacks/race-condition-vulnerability-wedohacks-ceae59b96e8a</a></p><h3>Race conditions can leads to Register multiple accounts with same Mail/Phone Number.</h3><p><strong>Steps To Reproduce</strong></p><ol><li>Navigate to the Registration page</li><li>Intercept the registration request and send it to the Repeater multiple times</li><li>Pause the original request and go to the Repeater.</li><li>In the repeater, group all the requests and enable the <strong>“Send group in sequence (<em>single connection</em>)”</strong> option in the group send settings.</li><li>Send the requests and observe the responses.</li></ol><ul><li>If you receive a “<strong>200 OK</strong>” response, check the user ID or any other unique identifiers associated with the account. This indicates that multiple accounts can be created with the same email or phone number, revealing a business logic flaw.</li></ul><blockquote>Race conditions can allow attackers to bypass restrictions and exploit application flaws. Testing for race conditions, especially in critical features, and applying measures like rate-limiting and locking mechanisms are essential to prevent these vulnerabilities.</blockquote><p>© 𝘄𝗲𝗱𝗼𝗵𝗮𝗰𝗸𝘀</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=140838fee1a4" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Race Condition Vulnerability | wedohacks | Part 1]]></title>
            <link>https://wedohacks.medium.com/race-condition-vulnerability-wedohacks-ceae59b96e8a?source=rss-731b888028ba------2</link>
            <guid isPermaLink="false">https://medium.com/p/ceae59b96e8a</guid>
            <dc:creator><![CDATA[WE DO HACKS]]></dc:creator>
            <pubDate>Tue, 05 Nov 2024 17:41:57 GMT</pubDate>
            <atom:updated>2024-11-10T17:49:58.436Z</atom:updated>
            <content:encoded><![CDATA[<p><strong>What is Race Condition?</strong></p><p><em>A race condition vulnerability occurs when the behavior of a system depends on the sequence or timing of uncontrollable events. It arises in concurrent or parallel programming environments where multiple processes, threads, or asynchronous operations interact with shared resources. If these interactions are not properly synchronized, the system can enter an inconsistent or unpredictable state, leading to potential security vulnerabilities.</em></p><p><strong>Where can we find it?</strong></p><p>In functions like Limited Feature Access, Registration, Password Reset, Like and Follow, and so on…</p><p>(<em> comment down if you know more </em>)</p><h4>Here, I’ll share how to identify race conditions in various functions.</h4><h3>Race conditions can lead to bypassing limited feature restrictions.</h3><p><strong>Steps To Reproduce</strong></p><ol><li>Register an account and <strong>create a key </strong>or<strong> invite a user</strong> (<em>if in an organization</em>).</li><li>After this, you may find that no further actions are possible due to being a free/trial user (<em>purchasing is required to unlock full functionality</em>).</li><li>Delete the key or user invite and attempt to create/invite again. This time, intercept the request and send it to the repeater multiple times, while holding the original request.</li><li>In the repeater, group all the requests and enable the <strong>“Send group in sequence (<em>single connection</em>)”</strong> option in the group send settings.</li><li>Send the requests and observe the responses.</li></ol><ul><li>If you receive a “<strong>200 OK</strong>” response, manually verify to see if the limited feature restriction has been bypassed.</li></ul><blockquote>Race conditions can allow attackers to bypass restrictions and exploit application flaws. Testing for race conditions, especially in critical features, and applying measures like rate-limiting and locking mechanisms are essential to prevent these vulnerabilities.</blockquote><p>© 𝘄𝗲𝗱𝗼𝗵𝗮𝗰𝗸𝘀</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ceae59b96e8a" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Lack of Rate Limiting in OTP Function Leading to Account Takeover]]></title>
            <link>https://wedohacks.medium.com/lack-of-rate-limiting-in-otp-function-leading-to-account-takeover-9d1998f24bae?source=rss-731b888028ba------2</link>
            <guid isPermaLink="false">https://medium.com/p/9d1998f24bae</guid>
            <dc:creator><![CDATA[WE DO HACKS]]></dc:creator>
            <pubDate>Fri, 01 Nov 2024 17:41:56 GMT</pubDate>
            <atom:updated>2024-11-05T17:29:02.109Z</atom:updated>
            <content:encoded><![CDATA[<h3>Lack of Rate Limiting in OTP Function Leading to Account Takeover | wedohacks</h3><p><strong>Introduction</strong><br><em>One-Time Password (OTP) mechanisms are essential for securing user accounts in online applications. However, without proper rate limiting on OTP verification attempts, these systems become susceptible to automated attacks. This report details a critical vulnerability that allows an attacker to bypass OTP verification through repeated attempts, facilitating potential account takeover.</em></p><p><strong>The Role of Rate Limiting<br></strong><em>Rate limiting is a security control that restricts the number of attempts a user can make to access a service within a specific timeframe. Implementing rate limits on OTP requests is crucial to prevent brute-force attacks, where an attacker tries multiple combinations to gain unauthorized access.</em></p><h3>How to exploit the lack of rate limiting in the OTP function:</h3><p>1. <strong>Create an Account</strong><br>Register a new user account in the target site/application and ready for OTP verification.</p><p>2. <strong>Request OTP Verification and capture the request </strong><br>When the application prompts you for the OTP (One-Time Password), enter an incorrect OTP and capture this request in Burp.</p><p>3. <strong>Send the Request to Intruder</strong><br>Send this request to the Intruder and set the payload and Start Attack</p><p>4. <strong>Monitor Responses</strong><br>If you receive a 200 OK or 302 Found status code, it means you have bypassed the OTP verification.</p><blockquote><strong>200 OK</strong> indicates that the request was successful, and the OTP verification was bypassed.<br><strong>302 FOUND</strong> often indicates a redirect, which could also lead to successful authentication if the application processes the request without properly validating the OTP.</blockquote><p>If you’re seeing a 200 OKor 302 Found response for both incorrect and correct OTPs, then what will you do???</p><p><strong>you can use Content-Length to differentiate between successful and unsuccessful attempts</strong></p><ul><li>For each OTP attempt, observe the <strong>Content-Length</strong> in the response headers or body.</li><li>Usually, a successful OTP verification response will have a different Content-Length from a failed attempt, as the content of the page changes. <em>(e.g., a visible cookie or auth token, a redirect to the dashboard, or a welcome message).</em></li></ul><p><strong>These methods can potentially bypass OTP in registration and login functions.</strong></p><p>© 𝘄𝗲𝗱𝗼𝗵𝗮𝗰𝗸𝘀</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=9d1998f24bae" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Authentication Bypass via Response Manipulation | wedohacks]]></title>
            <link>https://wedohacks.medium.com/authentication-bypass-via-response-manipulation-wedohacks-a4ce887e0965?source=rss-731b888028ba------2</link>
            <guid isPermaLink="false">https://medium.com/p/a4ce887e0965</guid>
            <dc:creator><![CDATA[WE DO HACKS]]></dc:creator>
            <pubDate>Thu, 10 Oct 2024 17:42:06 GMT</pubDate>
            <atom:updated>2024-10-11T12:14:42.813Z</atom:updated>
            <content:encoded><![CDATA[<h3>Authentication Bypass in Register account via Response manipulation</h3><p><strong>Step 1: Register Account and Request OTP</strong></p><ul><li>Register a new account using an email or mobile number.</li><li>Request for an OTP (One-Time Password) to be sent to the registered email/mobile number.</li></ul><p><strong>Step 2: Capture Incorrect OTP Request in Burp Suite</strong></p><ul><li>Enter an incorrect OTP and capture the request in Burp Suite.</li></ul><p><strong>Step 3: Modify Response</strong></p><ul><li>Modify the response to change the Status from false to true.</li></ul><p><strong>Original Response:</strong></p><pre>{<br>  &quot;Status&quot;: false,<br>}</pre><p><strong>Modified Response:</strong></p><pre>{<br>  &quot;Status&quot;: true,<br>}</pre><ul><li><em>Also change Status code to</em><em>200 OK , [sometimes cases </em><em>302 Found ].</em></li><li><em>And also there is </em><em>Status is </em><em>Error then change it to </em><em>Success.</em></li></ul><p><strong>Step 4: Forward Modified Response</strong></p><ul><li>Forward the modified response.</li><li>If you successfully logged in to the account, You bypassed the OTP verification process.</li></ul><h3>More test cases for bypassing OTP</h3><ul><li>Check for default OTPs such as 111111, 222222, 123456, and 000000 (use both 4-digit and 6-digit combinations)</li><li>Check the response to see if the OTP has been leaked (capture the request in Burp Suite and send it to Repeater to analyze the response).</li><li>Try reusing the old OTP, as it may still be valid.</li></ul><h4>These methods can potentially bypass OTP in registration and login functions.</h4><p>© 𝘄𝗲𝗱𝗼𝗵𝗮𝗰𝗸𝘀</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a4ce887e0965" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Easy way to find Open Redirect Bug | wedohacks]]></title>
            <link>https://wedohacks.medium.com/easy-way-to-find-open-redirect-bug-wedohacks-a374e6740fd0?source=rss-731b888028ba------2</link>
            <guid isPermaLink="false">https://medium.com/p/a374e6740fd0</guid>
            <dc:creator><![CDATA[WE DO HACKS]]></dc:creator>
            <pubDate>Sat, 05 Oct 2024 17:42:02 GMT</pubDate>
            <atom:updated>2024-10-06T08:29:38.484Z</atom:updated>
            <content:encoded><![CDATA[<p><strong>Tools Used:</strong></p><ul><li><a href="https://github.com/projectdiscovery/subfinder">Subfinder</a>: A subdomain discovery tool that uses various techniques to find subdomains of a target domain.</li><li><a href="https://github.com/projectdiscovery/httpx">Httpx</a>: A fast and multi-purpose HTTP toolkit that can be used to check the status of a large number of URLs.</li><li><a href="https://github.com/projectdiscovery/katana">Katana</a>: A command-line tool that provides a simple way to use multiple web application security scanners and tools.</li><li><a href="https://github.com/lc/gau">Gau</a>: A tool that fetches known URLs from AlienVault’s Open Threat Exchange, the Wayback Machine, and Common Crawl.</li><li><a href="https://github.com/tomnomnom/waybackurls">Waybackurls</a>: A tool that fetches URLs from the Wayback Machine.</li></ul><p><strong>Step 1: Subdomain Discovery using Subfinder</strong></p><ul><li>Run the following command to discover subdomains of the target domain:</li></ul><p>subfinder -d wedohacks.com --silent -o subdomains.txt</p><ul><li>This will save the discovered subdomains to a file named subdomains.txt</li></ul><p><strong>Step 2: Filtering Live Domains using Httpx</strong></p><ul><li>Run the following command to filter out live domains from the subdomains discovered in Step 1:</li></ul><p>cat subdomains.txt | httpx &gt;&gt; live_domains.txt</p><ul><li>This will save the live domains to a file named live_domains.txt.</li></ul><p><strong>Step 3: Crawling URLs using Katana, Gau and waybackurls</strong></p><ul><li>Run the following command to crawl URLs from the live domains :</li></ul><p>katana -u live_domains.txt --output katana-urls.txt</p><ul><li>This will save the crawled URLs to a file named katana-urls.txt.</li></ul><p><em>Here i use Katana for crawl the Urls</em></p><p><em>You can also use tools such as gau, waybackurls, hakrawler, gospider or any other tools of your choice.</em></p><p><strong>Step 4: Filtering URLs with Parameters</strong></p><ul><li>Run the following command to filter out URLs with parameters from the crawled URLs :</li></ul><p>cat katana-urls.txt | grep &quot;=&quot; &gt;&gt; param.txt</p><p>The command above is also helpful for filtering out XSS parameters.</p><p>Additionally, we can filter out JavaScript Files using the command below.</p><p>cat katana-urls.txt | grep &quot;.js$&quot; &gt;&gt; js.txt</p><ul><li>Again use the grep tool to find redirect parameters and also perform a manual check.</li></ul><p>cat param.txt | grep redirect</p><p>Use the below keywords also.</p><p>&quot;next=&quot;, &quot;url=&quot;, &quot;target=&quot;, &quot;rurl=&quot;, &quot;dest=&quot;, &quot;destination=&quot;, &quot;view=&quot;, &quot;redir=&quot;, &quot;redirect_uri=&quot;, &quot;redirect_url=&quot;, &quot;redirect=&quot;, &quot;image_url=&quot;, &quot;go=&quot;, &quot;return=&quot;, &quot;returnTo=&quot;, &quot;return_to=&quot;, &quot;login=&quot;, &quot;login?to=&quot;, &quot;continue=&quot;, &quot;return_path=&quot;, &quot;/out/&quot;, &quot;/out?&quot;, &quot;cgi-bin/redirect.cgi&quot;</p><p><strong>Step 5: Identifying Open Redirect Bugs</strong></p><ul><li>Manually test open redirect payloads one by one or use any automation tool.</li></ul><h4>If you find any redirection, report it to the organization</h4><p>Open Redirect payloads : <a href="https://github.com/wedohacks/payloads/tree/main/openredirect">https://github.com/wedohacks/payloads/tree/main/openredirect</a></p><h3>Google Dorks to find Open Redirect Parameter</h3><p>site:target.com inurl:url= | inurl:return= | inurl:next= | inurl:redirect= | inurl:redir= | inurl:ret= | inurl:r2= | inurl:page= | inurl:&amp; | inurl:http</p><h3>Google Dorking Tool</h3><h3><a href="https://wedohacks.github.io/googledorks.html">https://wedohacks.github.io/googledorks.html</a></h3><p>© 𝘄𝗲𝗱𝗼𝗵𝗮𝗰𝗸𝘀</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a374e6740fd0" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Open Redirect Bug | wedohacks]]></title>
            <link>https://wedohacks.medium.com/open-redirect-bug-wedohacks-26012e51d50c?source=rss-731b888028ba------2</link>
            <guid isPermaLink="false">https://medium.com/p/26012e51d50c</guid>
            <category><![CDATA[open-redirect]]></category>
            <category><![CDATA[bug-bounty]]></category>
            <category><![CDATA[bugs]]></category>
            <category><![CDATA[bug-hunting]]></category>
            <category><![CDATA[hacking]]></category>
            <dc:creator><![CDATA[WE DO HACKS]]></dc:creator>
            <pubDate>Tue, 01 Oct 2024 17:41:32 GMT</pubDate>
            <atom:updated>2024-10-02T11:53:46.196Z</atom:updated>
            <content:encoded><![CDATA[<h3>Find Open Redirection Vulnerability in Login Page</h3><p><strong>1. Register and Login an Account then Access User Profile</strong>:</p><ul><li>Navigate to your user profile page (e.g., <a href="https://wedohacks.com/accounts/profile">https://wedohacks.com/accounts/profile</a>).</li><li>Copy the URL of the profile page for later use.</li></ul><p><strong>2. Logout and Clear Cookies</strong>:</p><ul><li>Log out of your account.</li><li>Clear all cookies in your browser to ensure a fresh session.</li><li>Go to the homepage of the site (e.g., <a href="https://wedohacks.com/">https://wedohacks.com</a><a href="https://samplesite.me)./">).</a></li></ul><p><strong>3. Attempt to Access Profile URL</strong>:</p><ul><li>Paste the copied profile URL into the address bar and press Enter.</li><li>If the site prompts for login, observe the URL in the address bar. You may find the login page with a redirect parameter, such as:</li><li><a href="https://wedohacks.com/login?next=/accounts/profile">https://wedohacks.com/login?next=/accounts/profile</a></li><li><a href="https://wedohacks.com/login?returnUrl=/accounts/profile">https://wedohacks.com/login?returnUrl=/accounts/profile</a></li></ul><p><strong>4. Try to Exploit the Redirect Parameter</strong>:</p><ul><li>Attempt to exploit the redirect parameter by appending an external domain. For example:</li><li><a href="https://wedohacks.com/login?next=https://hacker.com/">https://wedohacks.com/login?next=https://hacker.com/</a></li><li>Alternatively, try bypassing any regex filters by using a crafted URL:</li><li><a href="https://wedohacks.com/login?next=https://wedohacks.com@hacker.com/">https://wedohacks.com/login?next=https://wedohacks.com@hacker.com/</a></li></ul><p><strong>5. Verify Open Redirection</strong>:</p><ul><li>If the site redirects you to hacker.com, you have successfully identified an open redirection vulnerability.</li></ul><h3>Google Dorks to find Open Redirect Parameter</h3><p>site:target.com <a href="https://wedohacks.github.io/googledorks.html#">inurl:url= | inurl:return= | inurl:next= | inurl:redirect= | inurl:redir= | inurl:ret= | inurl:r2= | inurl:page= | inurl:&amp; | inurl:http</a></p><h3>Google Dorking Tool</h3><h4><a href="https://wedohacks.github.io/googledorks.html">https://wedohacks.github.io/googledorks.html</a></h4><p>© 𝘄𝗲𝗱𝗼𝗵𝗮𝗰𝗸𝘀</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=26012e51d50c" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[© ]]></title>
            <link>https://wedohacks.medium.com/-5d85a7a601cf?source=rss-731b888028ba------2</link>
            <guid isPermaLink="false">https://medium.com/p/5d85a7a601cf</guid>
            <dc:creator><![CDATA[WE DO HACKS]]></dc:creator>
            <pubDate>Tue, 01 Oct 2024 17:41:32 GMT</pubDate>
            <atom:updated>2024-10-01T17:41:32.002Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*4CK18uQPthZsgYSJpcH4WQ.jpeg" /><figcaption>© 𝘄𝗲𝗱𝗼𝗵𝗮𝗰𝗸𝘀</figcaption></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5d85a7a601cf" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>