<?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 Salma Ashraf on Medium]]></title>
        <description><![CDATA[Stories by Salma Ashraf on Medium]]></description>
        <link>https://medium.com/@0xL0m4?source=rss-b00b246abc3a------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*5P3Vo4-xG6T71BTMMOhBcQ.jpeg</url>
            <title>Stories by Salma Ashraf on Medium</title>
            <link>https://medium.com/@0xL0m4?source=rss-b00b246abc3a------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 22:34:11 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@0xL0m4/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[Broken OTP Authentication Flow Leads to Email Abuse]]></title>
            <link>https://medium.com/@0xL0m4/broken-otp-authentication-flow-leads-to-email-abuse-52c9ee23ba57?source=rss-b00b246abc3a------2</link>
            <guid isPermaLink="false">https://medium.com/p/52c9ee23ba57</guid>
            <dc:creator><![CDATA[Salma Ashraf]]></dc:creator>
            <pubDate>Mon, 25 May 2026 09:46:20 GMT</pubDate>
            <atom:updated>2026-05-25T17:35:12.968Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Hf2jIrUk7jw6o6YndItywQ.jpeg" /></figure><p>بِسْمِ اللَّـهِ الرَّحْمَـٰنِ الرَّحِيمِ</p><p>In this writeup, I’ll walk through how a simple observation during OTP flow analysis led to uncovering an authentication-related issue. By carefully inspecting request behavior and testing different parameter values, I noticed an inconsistency that opened the door for deeper investigation.</p><p>Let’s dive in step by step…</p><h3>Overview</h3><p>While analyzing the application requests, I was specifically observing how the OTP generation process behaves under different request conditions.</p><p>The endpoint appeared to adjust its behavior based on the requirePassword query parameter……..hmm, which immediately raised questions about whether this logic was fully enforced server-side or partially controlled by client input.</p><p>During testing, I noticed that OTP enforcement differed depending on the value of this parameter, which led me to investigate further.</p><p><strong>Notes</strong></p><p>the testing was performed using a fully authenticated user session, obtained through a normal login flow.</p><p>A valid X-Session-Token was used throughout the testing process, meaning the requests were not executed as a guest or unauthenticated user.</p><h3>Steps</h3><p><strong>1. Authenticate normally</strong></p><p>Complete the standard login process and obtain a valid session token:</p><pre>X-Session-Token: &lt;valid_user_session_token&gt;</pre><p>2. Send OTP request with password requirement enabled</p><pre>POST /v3/customers/email/authenticate?requirePassword=true</pre><p>Body</p><pre>{<br>  &quot;username&quot;: &quot;test@email.com&quot;<br>}</pre><p>Result</p><p>403 Forbidden</p><p>The request fails as the endpoint enforces password validation.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*evjb9bv8XXJzOyZ1oMPjZQ.png" /><figcaption>without changing the parameter value</figcaption></figure><p>3. Modify authentication flow parameter</p><p>Change requirePassword from true to false:</p><pre>POST /v3/customers/email/authenticate?requirePassword=false</pre><p>Body</p><pre>{<br>  &quot;username&quot;: &quot;test@email.com&quot;<br>}</pre><p>Result</p><pre>200 OK<br>{<br>  &quot;result&quot;: {<br>    &quot;otpDigits&quot;: 4,<br>    &quot;isCaptchaRequired&quot;: false,<br>    &quot;reSendOtpTimer&quot;: 45,<br>    &quot;isRetryLimitExhausted&quot;: false<br>  }<br>}</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ieMzZUmeT2fglwjiXIlrPQ.png" /><figcaption>with changing requirePassword value from true to false</figcaption></figure><p>Voila, I can bypass its password value need with modify the parameter value . and OTP was successfully sent to that email.</p><p>4. Cross-email validation</p><p>Using the same authenticated session token, the OTP request can be repeated for different email addresses not associated with the logged-in user.</p><p>The system still returns a successful response as long as the requirePassword parameter is set to false.</p><p>This indicates that OTP generation is not strictly bound to:</p><p>session ownership , authenticated user identity , or server-side authorization checks</p><h3>Impact Analysis</h3><ul><li>Ability to trigger OTP for arbitrary email addresses</li><li>Potential abuse of OTP system (spam)</li></ul><h3>Conclusion</h3><p>This vulnerability demonstrates how small inconsistencies in authentication logic can lead to meaningful security gaps, especially when client-controlled parameters influence sensitive backend behavior.</p><p>Alhamdulillah, the issue was confirmed and accepted as a Low Severity finding by the security team.</p><blockquote>Don’t forget to keep Palestine in your prayers. See you in the next bug bounty writeup! 👋</blockquote><p>Questions or feedback? Feel free to connect with me on LinkedIn: <a href="http://www.linkedin.com/in/0xl0m4">www.linkedin.com/in/0xl0m4</a></p><p>سبحانك اللهم وبحمدك، أشهد أن لا إله إلا أنت، أستغفرك وأتوب إليك</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=52c9ee23ba57" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[From Subdomain Enumeration to an Exposed Internal Configuration Panel]]></title>
            <link>https://medium.com/@0xL0m4/from-subdomain-enumeration-to-an-exposed-internal-configuration-panel-3708df761dbc?source=rss-b00b246abc3a------2</link>
            <guid isPermaLink="false">https://medium.com/p/3708df761dbc</guid>
            <category><![CDATA[cybersecurity]]></category>
            <category><![CDATA[subdomains-enumeration]]></category>
            <category><![CDATA[penetration-testing]]></category>
            <category><![CDATA[web-security]]></category>
            <category><![CDATA[bug-bounty-writeup]]></category>
            <dc:creator><![CDATA[Salma Ashraf]]></dc:creator>
            <pubDate>Sun, 24 May 2026 18:35:58 GMT</pubDate>
            <atom:updated>2026-05-25T14:42:36.707Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*NXTqHjjwsSbjzWKVwlSa0Q.jpeg" /></figure><p>بِسْمِ اللَّـهِ الرَّحْمَـٰنِ الرَّحِيمِ</p><p>In bug bounty hunting, some of the most impactful findings don’t always come from complex scripts or heavy automation. Often, they come from careful observation, patience, and knowing where to look.</p><p>In this writeup, I’ll walk through how I was able to discover a critical security issue using a focused approach to reconnaissance. Let’s dive in.</p><h3><strong>Initial Discovery</strong></h3><p>My initial objective was to understand the application’s behavior. I started by interacting with the platform, observing how requests flow between the frontend and backend, and reviewing responses using browser DevTools and Burp Suite.</p><p>After a while, I decided to take a step back and expand the scope of my reconnaissance.</p><p>I ran a subdomain enumeration process using FFUF against the target infrastructure to get a clearer picture of the overall attack surface.</p><p>the tool returned more than 600 subdomains.</p><p>At that point, I began reviewing them one by one, trying to understand what services were exposed and whether any of them were unintentionally accessible.</p><p>During this process, I discovered a subdomain that immediately stood out, as it appeared to be an internal system that was not intended for public access.</p><p>Unlike the main production application, this environment looked like an internal dashboard that had been unintentionally exposed.</p><p>More importantly, it was accessible directly without any authentication or authorization checks in place.</p><h3><strong>Steps</strong></h3><p>Let’s assume that the vulnerable domain is: redacted.com</p><p>1- Perform subdomain enumeration on the target domain using ffuf:</p><pre>ffuf -u https://FUZZ.redacted.com \<br>-w /usr/share/wordlists/SecLists/Discovery/DNS/subdomains-top1million-5000.txt</pre><p>2- Manually review the discovered subdomains one by one to identify any interesting or potentially internal/staging environments.</p><p>3- During this process, I found a subdomain that appeared to expose an internal dashboard.</p><p>4- While exploring it, I discovered that one endpoint directly led me to the configuration panel: /dashboard/config</p><p>5- Accessing this endpoint revealed that it was fully reachable without any authentication or authorization checks.</p><p>6- The interface allowed direct interaction with configuration values through the UI.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*KQ36a1s80ClH4cLQ2POw-A.jpeg" /><figcaption>subdomain directly led to the configuration panel</figcaption></figure><p>7- After modifying a value, I opened that endpoint in another browser</p><p>8- Voila, The changes were successfully reflected.</p><h3>Conclusion</h3><p>This finding highlights how powerful recon step and even simple misconfigurations in staging or internal environments can lead to meaningful security exposure if not properly isolated.</p><p>Alhamdulillah, the vulnerability was reviewed and accepted as a High Severity finding.</p><blockquote><em>Don’t forget to keep Palestine in your prayers. See you in the next bug bounty writeup! 👋</em></blockquote><p>Questions or feedback? Feel free to connect with me on LinkedIn: <a href="http://www.linkedin.com/in/0xl0m4">www.linkedin.com/in/0xl0m4</a></p><p>سبحانك اللهم وبحمدك، أشهد أن لا إله إلا أنت، أستغفرك وأتوب إليك</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=3708df761dbc" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Help Ann — Forensics Challenge]]></title>
            <link>https://medium.com/@0xL0m4/help-ann-forensics-challenge-ad6277af55d5?source=rss-b00b246abc3a------2</link>
            <guid isPermaLink="false">https://medium.com/p/ad6277af55d5</guid>
            <dc:creator><![CDATA[Salma Ashraf]]></dc:creator>
            <pubDate>Tue, 13 Jan 2026 12:56:47 GMT</pubDate>
            <atom:updated>2026-01-13T13:10:34.885Z</atom:updated>
            <content:encoded><![CDATA[<h3>Help Ann writeup — Forensics Challenge</h3><p><strong>Platform:</strong> Cyber Talents<br> <strong>Category:</strong> Forensics<br> <strong>Difficulty:</strong> Medium (100 points)</p><h3>Challenge Description</h3><p>A scanned QR code was provided, but it was corrupted.<br> The goal was to fix the QR code image and retrieve the hidden information.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*K5emPNA8t4_M---4Lu1CjA.png" /></figure><h3>Tools Used</h3><ul><li>hexedit</li><li>file</li></ul><h3>Analysis Steps</h3><h3>1. Download the attached file named help_ann_please.</h3><h3>2. Check its type using the file command.</h3><pre>──(root㉿kali)-[/home/kali/Downloads]<br>└─# file help_ann_please<br>help_ann_please: data</pre><p>The output data indicates that the file type could not be recognized, suggesting that the header was corrupted.</p><h3>3. Open the file using hexedit to inspect its hex header.</h3><p>While inspecting the first bytes, it was clear that the file structure resembled a PNG image, but the header was incorrect.</p><h3>4. Identify the correct PNG header</h3><p>After searching for the PNG file signature, the correct hex header was found to be:</p><pre>89 50 4E 47 0D 0A 1A 0A</pre><h3>5. Fix the corrupted header</h3><p>It was observed that the first two bytes of the header were incorrect (00 instead of 89).<br> Edit them from 00 to 89 and save the changes.</p><h3>6. Verify the fix</h3><pre>┌──(root㉿kali)-[/home/kali/Downloads]<br>└─# file help_ann_please    <br>help_ann_please: PNG image data, 300 x 300, 8-bit/color RGBA, non-interlaced</pre><p>This confirmed that the file was successfully restored as a valid PNG image.</p><h3>7. Open the image</h3><p>Use the xdg-open tool:</p><pre>xdg-open help_ann_please</pre><p>The image was now clearly visible as a QR code.</p><h3>8. Scan the QR code</h3><p>After scanning the QR code, the flag was successfully retrieved.</p><h3>Flag</h3><pre>Flag{Aw3s0m3-Y0u-G0t-th1s}</pre><blockquote><em>Until next challenge! 👋</em></blockquote><p><a href="https://cybertalents.com/challenges/forensics/help-ann">The challenge link</a></p><p><a href="https://www.linkedin.com/in/salma-ashraf11">LinkedIn</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ad6277af55d5" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>