<?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 Mohamed Shibil on Medium]]></title>
        <description><![CDATA[Stories by Mohamed Shibil on Medium]]></description>
        <link>https://medium.com/@mshibilmp?source=rss-150e035ad072------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*-Ao4DTMey5Djif-pd7QOuQ.jpeg</url>
            <title>Stories by Mohamed Shibil on Medium</title>
            <link>https://medium.com/@mshibilmp?source=rss-150e035ad072------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 14:51:03 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@mshibilmp/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[How I Earned My Place Among  Ferrari’s Elite-16 in the Hall of Fame]]></title>
            <link>https://mshibilmp.medium.com/how-i-earned-my-place-among-ferraris-elite-16-in-the-hall-of-fame-951e95ae3dc8?source=rss-150e035ad072------2</link>
            <guid isPermaLink="false">https://medium.com/p/951e95ae3dc8</guid>
            <category><![CDATA[hall-of-fame]]></category>
            <category><![CDATA[ethical-hacking]]></category>
            <category><![CDATA[bug-bounty]]></category>
            <category><![CDATA[penetration-testing]]></category>
            <category><![CDATA[cybersecurity]]></category>
            <dc:creator><![CDATA[Mohamed Shibil]]></dc:creator>
            <pubDate>Fri, 22 Sep 2023 16:09:24 GMT</pubDate>
            <atom:updated>2023-09-22T16:09:24.047Z</atom:updated>
            <content:encoded><![CDATA[<p>Hi Leets 👨‍💻 !</p><p>In this blog✍ , I am delighted to recount my journey of achieving a place in the Iconic Brand <strong>Ferrari’s Hall of Fame</strong> by securing their products and services.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*FB7Ag8LNE49UtRR6.jpg" /></figure><p><em>Lets Start. . .🐞</em></p><blockquote>Vulnerability: Sensitive Information Disclosure</blockquote><p>Sensitive Information Disclosure is a security 🛠 vulnerability that occurs when sensitive or confidential 👀 data is unintentionally exposed to unauthorized individuals or entities. This vulnerability can arise from various sources, such as insecure configurations, coding errors,<br>inadequate access controls, or weaknesses in network communication protocols. Attackers can exploit this vulnerability to gain access to sensitive data, leading to potential privacy breaches, identity theft, financial loss, or reputation damage for individuals or organizations.</p><blockquote>Steps to Reproduce:</blockquote><ol><li>Enumerated the subdomains using tools such as <strong>amass</strong>, <strong>subfinder</strong>, <strong>findomain</strong>, <strong>assetfinder</strong> etc.</li><li>Remove the duplicate domains from above results.</li><li>Find the live subdomains by using <strong>httpx </strong>or <strong>httprobe</strong> and selected one subdomain ( <a href="https://test.redact.com/">https://test.redact.com</a><strong> </strong>)</li><li>Identified couple of <strong>endpoints</strong>; used <strong>dirsearch</strong> for this part</li><li>Checked each endpoints individually and noted one of them are not accessible via <strong>GET</strong> request.(https://test.redact.com/api/consumer/systemsettings)</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/proxy/1*jpSmq-M5n9szWVkujrBVDw.png" /></figure><p>6. So I intercepted the request using Burp-suite and changed the request method from <strong>GET</strong> to <strong>POST</strong> and added the <strong>content-length</strong> as well and send the request.</p><p>7. After thoroughly reviewing the response, and really surprised 😲 that I was able to fetch ♨ sensitive information such as <em>AzureAuthuserId</em>, <em>AzureAuth Password, Client IDs, Consumer IDs, Internal path endpoints and many more. . .</em></p><p>I made an attempt to escalate the vulnerability, but encountered some challenges. Subsequently, I prepared a comprehensive report 📖 and shared it with the appropriate team as a contribution to their <strong>Responsible Disclosure Program</strong>.</p><p>A few days later, the team successfully resolved the issue &amp; acknowledged my contribution by including my name in their <strong>Hall of Fame</strong> 🌟</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/581/1*T1LeQ1z1omzzKT38xnMKGg.png" /><figcaption>Ferrari Hall of Fame</figcaption></figure><p>Thank you for <em>passing by</em> ! :🖐</p><p>Happy Hunting :🐞</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=951e95ae3dc8" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How I Earned $$$ for Excessive Data Exposure Through Directory Traversal Leads to Product Price…]]></title>
            <link>https://mshibilmp.medium.com/how-i-earned-for-excessive-data-exposure-through-directory-traversal-leads-to-product-price-4582e5371774?source=rss-150e035ad072------2</link>
            <guid isPermaLink="false">https://medium.com/p/4582e5371774</guid>
            <category><![CDATA[infosec]]></category>
            <category><![CDATA[owasp]]></category>
            <category><![CDATA[bug-bounty]]></category>
            <category><![CDATA[ethical-hacking]]></category>
            <category><![CDATA[api]]></category>
            <dc:creator><![CDATA[Mohamed Shibil]]></dc:creator>
            <pubDate>Fri, 03 Mar 2023 02:36:10 GMT</pubDate>
            <atom:updated>2025-08-10T15:22:59.645Z</atom:updated>
            <content:encoded><![CDATA[<h3>How I Earned $$$ for Excessive Data Exposure Through Directory Traversal Leads to Product Price Manipulation</h3><p>Hi Folks 👋,</p><p>This is my second <em>small</em> write-up✍️. This time I am writing about the first bounty I received from a private program. Let’s say our domain name called <strong>Redact.com</strong></p><blockquote><strong><em>API3:Excessive Data Exposure</em></strong></blockquote><blockquote>Excessive data exposure is a vulnerability that occurs when sensitive data is exposed to an unauthorized user or application. This can include data such as passwords, credit card numbers, social security numbers, and other personal information. This type of vulnerability can occur when an application is not properly configured to limit access to sensitive data, or when an application does not properly encrypt the data before it is stored or transmitted. This can allow malicious actors to gain access to data that should be kept private.</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*PfQigkYUQtwfEhidhDYc5Q.png" /></figure><p>Since <strong>Redact.com </strong>having Medium scope, I started with subdomain enumeration and among them only a few was in scope and rest belongs to third party domains.</p><p>Coming to the main application, I went through the each functionality to get an idea how the application works.</p><h3><strong>Attack Scenario: </strong>🛠</h3><p>They have couple of products in the application which is used to organize the documents. So I thought of checking their <strong>Product Purchasing Flow.</strong></p><p>First I fire up Burp suite then select a product and added to cart by intercepting the cart requests. I checked each request’s responses but didn’t find anything interesting. After going through all the requests I am done for that day 🌃 !</p><p>Very next day with a fresh mind again I focused on the same scenario carefully. Then I noticed one of the requests among adding to cart has a parameter <strong>base</strong></p><pre>base=https://www.redact.com</pre><p>and another parameter <strong>next </strong>in the <strong>URL</strong> !</p><pre>next=https://www.redact.com/cart?sku=0000000</pre><p>Then I was started to playing with these parameters one after another to find something special. Interestingly the <strong>base </strong>parameter was <em>unlocked</em> by throwing at “ <strong>/../../../../../../</strong> ” payload via simple <strong>Directory Traversal</strong> !!</p><p>This landed us to another subdomain which exposed the Sensitive Information in JSON format 🔎</p><pre>https://api.redact.com/numericalvalue/cart/list.ext?id=</pre><blockquote>Here goes the <strong>Magic Spell</strong> ! !</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/498/0*kQYi2MlYraa3nBZS.gif" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*FY_xcysP0EPtyWdbg-7o_Q.png" /><figcaption>Excessive Data Exposed</figcaption></figure><blockquote>I checked its response and found 👾 <strong>Excessive data </strong>including the <strong>product’s distinct coupon codes</strong>, <strong>id, Clients who received personalized discount</strong> was exposed.</blockquote><p>Then what I did was, just copied one of the Coupon code and entered the same code during check out and I got the discount to purchase the product. I tried each and every coupon code and finally got a Coupon code which 👾 “<strong><em>offers 100% discount” </em></strong>and I applied that code in the coupon code. Instantly the price changed to 000.00 for their Pro Product. So I can able to purchase it <strong>Free of cost</strong>!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/772/1*v9yvqUAGE6df4iRsANNw5g.png" /><figcaption>After Applying the 100% Coupon code for purchasing pro edition</figcaption></figure><p>For reporting this vulnerability, I’ve been 🎯 awarded with <strong>$500 </strong>💰 and got the appreciation from the client as well !</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/511/1*ywBIxC3F4OVxMJMhyQyDeQ.png" /><figcaption>Bounty Received !</figcaption></figure><p>Happy to secure !</p><p>Thank you 🙏🏻</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4582e5371774" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How I got my first Appreciation ?!]]></title>
            <link>https://mshibilmp.medium.com/how-i-got-my-first-appreciation-f3f6c15cf87?source=rss-150e035ad072------2</link>
            <guid isPermaLink="false">https://medium.com/p/f3f6c15cf87</guid>
            <category><![CDATA[ethical-hacking]]></category>
            <category><![CDATA[responsible-disclosure]]></category>
            <category><![CDATA[cybersecurity]]></category>
            <category><![CDATA[bug-hunting]]></category>
            <category><![CDATA[bug-bounty]]></category>
            <dc:creator><![CDATA[Mohamed Shibil]]></dc:creator>
            <pubDate>Sat, 10 Jul 2021 21:30:33 GMT</pubDate>
            <atom:updated>2021-08-09T04:34:55.181Z</atom:updated>
            <content:encoded><![CDATA[<h3>How I got my first Acknowledgement ?!</h3><p>In a Responsible Disclosure Program.</p><p>Like every noob , I am also stuck in between where to start in bug bounty and how to select a target ? , even though I am doing pen testing for months !</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/638/0*7B8E-MBxgNwd2Otj" /></figure><p>Finally, after roaming weeks by weeks I catch up something and started to hunt . Then I realized that I am wasting time , because I opted the bad approach . Every-time when someone posts their bug bounties $$ my inner-self was hurting . But I didn’t give up , I started learning again by reading blogs , write-ups , watching POC and all .</p><p>This time I choose <em>less traveled road ! </em>Nothing but the google dorks .</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/384/0*OWAEtUFLuHWQD6i2" /></figure><p>One after one I checked the sites and their In-scope and Out of scope stuffs. Later ,I choose one target called <em>redact.com</em> and stick to it . Yaaaaeeeaay !!</p><blockquote>Focus on the journey, not the destination. Joy is found not in finishing an activity but in doing it.-Greg Anderson</blockquote><p>Started to Recon and enumerated subdomains . Then got an interesting subdomain called <em>dashboard.redact.com . </em>Opened the subdomain in browser and checked its content . Its redirected to a login page !</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/430/0*Nyz6adEuhUYFSiAy.jpg" /></figure><p>I tried to login with default credentials , but <strong>F.A.I.L.E.D</strong> miserably. Then did the brute-forcing , nothing happened . Now I change my mind and go for the directory brute-forcing . . . . . . . . . . T A — D A ! got something . . . . . . . . . . . .</p><p>I got an interesting endpoint called /metrices . Once hit the enter , it exposes the dashboard metrices to the instance. I got some information exposed including OS Information , Response time , Admin and Users counts etc . . .</p><blockquote>Feeling Happy finally , didn’t waste a time and started to make the report and send send them on the same day . After couple of weeks, got a response from the security team stating that they acknowledged the issue and it is valid .</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/620/0*7CZaLHp7aRGz8E0s.jpg" /><figcaption>This is the exact feeling once I got the response from the asset owner</figcaption></figure><blockquote>Thank you for Passing by 🙏</blockquote><p><em>NB : This is my very first write-up in this platform . Kindly pardon me for the typos,grammar and made u sleep for reading this ! .</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f3f6c15cf87" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>