<?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 Bashir Mohamed (BlackPanther87) on Medium]]></title>
        <description><![CDATA[Stories by Bashir Mohamed (BlackPanther87) on Medium]]></description>
        <link>https://medium.com/@bashir69emceeaka5?source=rss-576968c636dc------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*8JwozcXUX9qSMJUS.jpg</url>
            <title>Stories by Bashir Mohamed (BlackPanther87) on Medium</title>
            <link>https://medium.com/@bashir69emceeaka5?source=rss-576968c636dc------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 18 Nov 2026 20:03:58 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@bashir69emceeaka5/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[Cross-Tenant Access Exploit in Microsoft Entra ID: Breaking Governance with a simple trick]]></title>
            <link>https://medium.com/@bashir69emceeaka5/cross-tenant-access-exploit-in-microsoft-entra-id-breaking-governance-with-a-simple-trick-a06d88fe309e?source=rss-576968c636dc------2</link>
            <guid isPermaLink="false">https://medium.com/p/a06d88fe309e</guid>
            <dc:creator><![CDATA[Bashir Mohamed (BlackPanther87)]]></dc:creator>
            <pubDate>Tue, 16 Sep 2025 20:56:58 GMT</pubDate>
            <atom:updated>2025-09-16T20:56:58.086Z</atom:updated>
            <content:encoded><![CDATA[<p>Hello everyone,</p><p>I’m back with another security write‑up, and my goal this time is to share techniques that could sharpen your own assessment methodology. Let’s dive straight into the findings.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/220/1*rxDvreACkFSiskUzLaqPWg.gif" /></figure><h3>What Is Entitlement Management?</h3><p>Microsoft Entra ID’s <strong>Entitlement Management</strong> is a cornerstone of identity governance. It enables organizations to:</p><ul><li>Bundle resources into <strong>access packages</strong> (apps, groups, SharePoint sites).</li><li>Define <strong>policies</strong> for request, approval, and review.</li><li>Automate <strong>lifecycle management</strong> for on-boarding, expiration, and off-boarding.</li></ul><p>Users interact with these packages via the <strong>MyAccess portal </strong><a href="https://myaccess.microsoft.com,/"><strong>https://myaccess.microsoft.com</strong>,</a> which enforces governance policies.</p><figure><img alt="" src="https://cdn-images-1.medium.com/proxy/1*lIW9OfB5zcUqIZHEae8Fpw.png" /></figure><h3>Where is The Vulnerability here?</h3><p>Functionally, everything seemed to work “as designed” but there was a <strong>critical oversight</strong>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/560/1*XgB-Sjd4ZuwQgvxLijnnDw.gif" /></figure><p>A flaw in the MyAccess portal allowed attackers to initiate <strong>cross‑tenant access flows</strong> and <strong>bypass identity governance controls</strong> simply by crafting a URL in this format:</p><pre><a href="https://myaccess.microsoft.com/@ANYTARGET.onmicrosoft.com">https://myaccess.microsoft.com/@ANYTARGET.onmicrosoft.com</a></pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/220/1*UEXEK6-AaaB7HeCRZwC60w.gif" /></figure><p>Here is the Attack Flow:</p><ol><li>Visit the crafted URL targeting any Entra tenant.</li><li>Redirected to the OAuth 2.0 login flow.</li><li>Land inside the <strong>MyAccess portal</strong> scoped to that target tenant.</li><li>Request access to sensitive groups or resources.</li><li>If packages were misconfigured, governance controls could be sidestepped.</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*yQ2c9v7WszxJthwoGJ2wZA.jpeg" /></figure><p>So, I decided to see whether it’s possible to log into Microsoft’s tenant:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*7Xtb3JBpJ7b-WcTT_NKDcA.png" /></figure><p>and to my surprise it was possible indeed!</p><h3>Real-World Impact:</h3><ul><li>To validate the flaw, I targeted Microsoft’s own tenant:</li><li>Successfully accessed myaccess.microsoft.com/@microsoft.onmicrosoft.com.</li><li>Viewed <strong>over 35,500 access packages</strong> containing Azure AD Security Groups, Dynamics, Teams, and SharePoint groups by requesting access to a specific group from within the portal at <a href="https://myaccess.microsoft.com/@microsoft.onmicrosoft.com.">https://myaccess.microsoft.com/@microsoft.onmicrosoft.com.</a></li><li>Submitted 30+ requests across different packages — some were approved, others denied.</li></ul><p><strong>Scope:</strong> All Microsoft Entra ID tenants, including Microsoft’s own. <strong>Exposure:</strong> Accessible to <em>any</em> authenticated Azure user. <strong>Severity:</strong> High — potential for unauthorized access and privilege escalation.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*l9ivYT-VOZ2S9gOwXSGx_A.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*gZO7pCDUy6ZaJMEEwUE8iQ.jpeg" /></figure><h3>Mitigation Strategies</h3><p>To defend against this vulnerability, organizations must:</p><p>1 — Enforce strict governance on all access packages.</p><p>2 — Disable automatic approvals unless absolutely necessary.</p><p>3 — Require multi-stage approvals and periodic access reviews.</p><p>4 — Enable Just-in-Time (JIT) access with expiration and audit logging.</p><p>5 — Restrict packages to verified users or groups.</p><p>6 — Monitor external access requests and user activity.</p><h3>How Bad was it?</h3><p>this issue was so bad that Microsoft added myaccess.microsoft.com including other subdomains to the in-scope domains in the Identity bug bounty program.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*j5y5INn-zfCGxWqSHlK7fw.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/555/1*YclpHDGsbDA-Phe4chAaAg.png" /></figure><p>Not only that but Microsoft had to cancel planned changes to Access Package visibility in Entitlement management →</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/535/1*362XJ8YcTrqfVGe87yTGlg.png" /></figure><p>It’s rewarding to see impactful research recognized, and even more so to know that organizations can now better safeguard their identity layer.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*h7pEp6KyECY0Wq7vuTa0CA.jpeg" /></figure><p>by discovering and reporting this I was qualified to participate in the ZeroDayQuest live hacking event at Microsoft’s headquarter in Redmond Washington →</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*FsZR_pryFoe04JSafmxZEA.png" /></figure><h3>The bigger lesson:</h3><h4>Identity governance isn’t “set‑and‑forget”, it needs tight scoping, enforced approvals, and continuous monitoring to prevent clever pivots from turning into full‑blown breaches.</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/702/1*xAsOdFZhfjAO9UBc6zXxlg.jpeg" /></figure><p>Security isn’t just about patching flaws, it’s about anticipating the clever, unexpected ways systems can be bent. This exploit proved that even when tools behave “as designed,” misconfigurations can turn them into open doors.</p><p>Guard your identity layer with the same vigilance you’d reserve for your most prized asset. Review, test, and challenge your governance controls often, because the safest systems are those that are never taken for granted.</p><p>Stay curious, keep probing, and remember:</p><p>every vulnerability discovered and shared responsibly strengthens the shield we all rely on.</p><h3>Timeline</h3><ul><li><strong>23 Jun 2025</strong> Proof‑of‑concept video recorded showing exploit.</li><li><strong>25 Jun 2025, 19:49</strong> Issue reported to MSRC with details and POC.</li><li><strong>25 Jun 2025, 19:53</strong> Auto‑acknowledgment from MSRC.</li><li><strong>26 Jun 2025, 15:57</strong> MSRC requests additional technical data.</li><li><strong>26 Jun 2025, 15:59</strong> Case moved to “Review / Repro”, ID xxxxx assigned.</li><li><strong>27 Jun 2025, 17:11</strong> Researcher replies with alternative reproduction info.</li><li><strong>27 Jun 2025, 17:35</strong> Additional OAuth error details sent.</li><li><strong>30 Jun 2025, 21:20</strong> MSRC acknowledges added information.</li><li><strong>07 Jul 2025, 07:49</strong> MSRC confirms issue reproduced, fix in progress, disclosure deferral requested.</li><li><strong>07 Jul 2025, 23:01</strong> Researcher agrees to coordinated disclosure.</li><li><strong>08 Jul 2025, 07:50</strong> Researcher asks if vulnerability is zero‑day and CVE‑eligible.</li><li><strong>17 Jul 2025, 22:21</strong> Bounty review process begins.</li><li><strong>21 Jul 2025, 00:31</strong> Researcher reports account lockout from Microsoft tenant.</li><li><strong>24 Jul 2025, 19:31</strong> MSRC says CVE/acknowledgment decision after investigation.</li><li><strong>24 Jul 2025, 20:13</strong> Bounty award US $20,000 granted, rated Important, Elevation of Privilege.</li><li><strong>25 Jul 2025, 11:43</strong> Researcher thanks MSRC for award.</li><li><strong>31 Jul 2025, 01:05</strong> MSRC notes severity concerns are under review.</li><li><strong>07 Aug 2025, 00:07</strong> Case status changed to “Pre‑Release”, fix scheduled.</li><li><strong>08 Aug 2025, 23:26</strong> MSRC asks if disclosure blog is planned.</li><li><strong>10 Aug 2025, 17:40</strong> Researcher repeats CVE query,plans to share draft.</li><li><strong>11 Aug 2025, 21:35</strong> MSRC confirms not a zero‑day, no CVE, will acknowledge as online service vuln.</li><li>2 Sept MSRC confirms blog review underway.</li><li>5 Sept MSRC approves blog post and closes the case.</li><li>16 Sept blog post published.</li></ul><h3>Thank you for reading and may the bounties and bugs be with you 😎</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/780/1*6a2ieuFpxj1ACqyqGjGZww.jpeg" /></figure><p><strong>#MicrosoftEntraID</strong> #IdentityGovernance #AccessPackage #CloudSecurity <strong>#CrossTenantAccess</strong> #AzureAD #IdentityAndAccessManagement #Pentest <strong>#PrivilegeEscalation</strong> #BugBounty #EthicalHacking #Infosec <strong>#OAuthSecurity</strong> #SecurityResearch #MyAccessPortal #VulnerabilityReport</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a06d88fe309e" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How I got a 5000 $ Bounty from Microsoft]]></title>
            <link>https://medium.com/@bashir69emceeaka5/how-i-got-a-5000-bounty-from-microsoft-fb2e27fd40f7?source=rss-576968c636dc------2</link>
            <guid isPermaLink="false">https://medium.com/p/fb2e27fd40f7</guid>
            <category><![CDATA[red-team]]></category>
            <category><![CDATA[bug-bounty-tips]]></category>
            <category><![CDATA[security]]></category>
            <category><![CDATA[bug-bounty-writeup]]></category>
            <category><![CDATA[bug-bounty]]></category>
            <dc:creator><![CDATA[Bashir Mohamed (BlackPanther87)]]></dc:creator>
            <pubDate>Tue, 08 Oct 2024 19:09:21 GMT</pubDate>
            <atom:updated>2024-10-09T13:35:11.725Z</atom:updated>
            <content:encoded><![CDATA[<p>Hi there, my Name is Bashir aka BlackPanther87 and this is my second Writeup on Medium where I will share how I got a 5000 $ Bounty from Microsoft so without further wait let’s dive into the details.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/0*jx0bTumyac1C_B-9.jpg" /></figure><p>You might know from my previous Writeup <a href="https://medium.com/@bashir69emceeaka5/401-unauthorized-access-is-denied-due-to-invalid-credentials-53b086379a08">https://medium.com/@bashir69emceeaka5/401-unauthorized-access-is-denied-due-to-invalid-credentials-53b086379a08</a> that I mostly hunt on the public Microsoft bug bounty program →</p><p><a href="https://www.microsoft.com/en-us/msrc/bounty">https://www.microsoft.com/en-us/msrc/bounty</a></p><p>After reporting my previous Bug, I was excited and motivated to find more Bugs, so I repeated the same recon process… again</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/536/0*rzDuqOZUIkPSygae.png" /></figure><p>The results weren’t satisfying at all</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/888/0*A1aieoREx7h_1WET.jpg" /></figure><p>To be honest I use only findomain and subfinder sometimes so there’s no wonder why I didn’t find potentials subdomains to hunt on.</p><p>Tip: don’t skip Recon otherwise you’ll be out of the competition.</p><p>So what should I do now?</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/640/0*HWsH62GzduhFsuMV.jpg" /></figure><p>I pulled out my last but not least bullet →</p><p>Shodan.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/209/0*-4n2sKU5ejPMIiPI" /></figure><p>But what is Shodan?</p><p><strong>Shodan</strong> is a <a href="https://en.wikipedia.org/wiki/Search_engine">search engine</a> that lets users search for various types of servers (<a href="https://en.wikipedia.org/wiki/Webcam">webcams</a>, <a href="https://en.wikipedia.org/wiki/Router_(computing)">routers</a>, <a href="https://en.wikipedia.org/wiki/Server_(computing)">servers</a>, etc.) connected to the <a href="https://en.wikipedia.org/wiki/Internet">internet</a> using a variety of filters.<a href="https://en.wikipedia.org/wiki/Shodan_(website)#cite_note-1">[1]</a> Some have also described it as a search engine of <a href="https://en.wikipedia.org/wiki/Banner_grabbing">service banners</a>, which is <a href="https://en.wikipedia.org/wiki/Metadata">metadata</a> that the <a href="https://en.wikipedia.org/wiki/Server_(computing)">server</a> sends back to the client.<a href="https://en.wikipedia.org/wiki/Shodan_(website)#cite_note-shodanabout-2">[2]</a> This can be information about the server software, what options the service supports, a welcome message or anything else that the client can find out before interacting with the server.</p><p>Next step was to run some Shodan queries →<br>ssl:*.target.com 200</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*A5UjPG0Hf-8a4Jxrp0L1oA.png" /></figure><p>I was searching for any subdomains related to Bing.</p><p>But why Bing?</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*vVYOw5hAzPxabwZ5.gif" /></figure><p>I was inspired by the research done by one of the Wiz security researchers called <a href="https://www.wiz.io/authors/hillai-ben-sasson">Hillai Ben-Sasson</a>.</p><p>According to his research he found one of the craziest Bugs which he named the BingBang!</p><p>You can read more about this Story here →<br><a href="https://www.wiz.io/blog/bingbang">BingBang: How a simple developer mistake could have led to Bing.com takeover | Wiz Blog</a></p><p>So lets back to my story.</p><p>While searching for any subdomains related to Bing on Shodan, I found an insane subdomain!</p><figure><img alt="" src="https://cdn-images-1.medium.com/proxy/1*A5UjPG0Hf-8a4Jxrp0L1oA.png" /></figure><p>I couldn’t believe my eyes for seconds; I was like seriously! please not yet another interior panel.</p><p>Luckily for me it was!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/400/0*0I6v-3FGG1PySdbD" /></figure><p>I started navigating the platform and for my surprise it didn’t require any authentication!</p><p>I clicked the dropdown list under Dynamic Drawl and navigated to MC Dashboard.</p><p>Holy Grail!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/498/0*LGDHHewq8eZbugjr" /></figure><p>Apparently, Microsoft was using this feature to crawl its Domains/Subdomains to run some operational tasks.</p><p>To my surprise I found this unrestricted unauthenticated file upload bug under the Dynamic Drawler Cache Management which could allowed me to upload any payload such as XSS or a Reverse Shell or any malicious Malware!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/500/0*NNmLyY1fB6qqqTdu.jpg" /></figure><p>But hold on for a second! this was not everything, I went back to MC Dashboard and scrolled down until the end of the page.</p><p>Literally I was able to cause a massive XSS attacks against any Microsoft’s Subdomain stealing the credentials of any User logged in to that Service!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/620/0*qTgbLr2JWw9EKI0B.jpg" /></figure><p>I quickly summarized my findings and submitted the report to MSRC.</p><p>Shortly after I got notified that they are investigating the issue internally.</p><p>The impact of this Bug is beyond the scope of this Writeup so bear with me since this is my second Writeup and that I’m not allowed to share any sensitive details.</p><p>You can find more details here <a href="https://www.microsoft.com/en-us/msrc/cvd">https://www.microsoft.com/en-us/msrc/cvd</a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/479/0*9_2A4pYxCwS_b34t.jpg" /></figure><p>Well, next I had to wait for a while.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/736/0*MzCv7wOK-yjoPRCu.jpg" /></figure><p>Timeline:</p><p>31 Jul 2024 report submitted to MSRC and was followed by confirmation of receive.</p><p>1 Aug 2024 MSRC had accelerated response and disabled the site within 24 hours of receiving the case.</p><p>22 Aug 2024 got a notification from MSRC confirming the reported behaviour.</p><p>16 Sept 2024 A fix was reported for the reported issue and Microsoft would like to recognize my efforts on their public security researcher acknowledgement page.</p><p>18 Sept 2024 MSRC asked to review this Writeup before it goes public.</p><p>18 Sept 2024 I replied that the Writeup is not finish yet and it would take 2 days to be finished.</p><p>19 Sept 2024 MSRC engineering team has determined that my case is eligible for a $5000 US bounty award under the M365 Bounty Program.</p><p>25 Sept 2024 Writeup was sent to MSRC to be reviewed.</p><p>3 Oct 2024 Writeup was approved by MSRC.</p><p>That’s it Volks :)</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/498/0*jr77gq8xlwYR8TFO" /></figure><p>Tools used to discover this Bug:</p><p>1- Subfinder by project discovery <a href="https://github.com/projectdiscovery/subfinder">GitHub — projectdiscovery/subfinder: Fast passive subdomain enumeration tool.</a></p><p>2- Findomain <a href="https://github.com/Findomain/Findomain">GitHub — Findomain/Findomain: The fastest and complete solution for domain recognition. Supports screenshoting, port scan, HTTP check, data import from other tools, subdomain monitoring, alerts via Discord, Slack and Telegram, multiple API Keys for sources and much more.</a></p><p>3- Shodan <a href="https://www.shodan.io/">https://www.shodan.io/</a></p><p>Special thanks to the MSRC Team, Project Discovery, <a href="https://github.com/Edu4rdSHL">Eduard Tolosa</a> the author of findomain, the Shodan Team, <a href="https://www.wiz.io/authors/hillai-ben-sasson">Hillai Ben-Sasson</a> for the awesome BingBang research, and thanks to all BugBounty Hunters and the BugBounty hunting community.</p><p>You can find me here →</p><p>Twitter: <a href="https://x.com/panther86_black">BlackPanther86 (@panther86_black) / X</a><br>Linkedin: <a href="http://www.linkedin.com/in/mohamed-abdalah-bashir-322b941b2">www.linkedin.com/in/mohamed-abdalah-bashir-322b941b2</a></p><p>Thank you and Happy Hacking :)</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/498/0*AwgC9Na-ipsrSyeJ.gif" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=fb2e27fd40f7" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[From 401 — Unauthorized Access to 3000 $ Bounty from Microsoft.]]></title>
            <link>https://medium.com/@bashir69emceeaka5/from-401-unauthorized-access-to-3000-bounty-from-microsoft-53b086379a08?source=rss-576968c636dc------2</link>
            <guid isPermaLink="false">https://medium.com/p/53b086379a08</guid>
            <category><![CDATA[red-team]]></category>
            <category><![CDATA[microsoft]]></category>
            <category><![CDATA[bug-bounty]]></category>
            <category><![CDATA[bugbounty-writeup]]></category>
            <category><![CDATA[security]]></category>
            <dc:creator><![CDATA[Bashir Mohamed (BlackPanther87)]]></dc:creator>
            <pubDate>Tue, 08 Oct 2024 18:55:28 GMT</pubDate>
            <atom:updated>2024-10-10T06:24:43.031Z</atom:updated>
            <content:encoded><![CDATA[<h3>From 401 — Unauthorized Access to 3000 $ Bounty from Microsoft.</h3><h3>Hi everyone, this is my very first writeup on Medium.</h3><p>First, I will introduce myself and then I will jump directly into my latest findings.</p><p>Whoami?</p><p>Well, my name is Bashir, and I go by the name Blackpanther87, I’m a Sysadmin/DevOps by day and a Bug Bounty hunter by night.</p><p>Few months ago, I found a cool Bug at one of Microsoft’s subdomains, but why exactly Microsoft?</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*pEv2IT1OFJ3rrlIC" /><figcaption>Photo by <a href="https://unsplash.com/@impelling?utm_source=medium&amp;utm_medium=referral">Ed Hardie</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>The short answer is, because I work on a daily base as a Sysadmin with Microsoft products such as Office365, Exchange, Azure … etcetera.</p><p>The long answer is, I been hunting on Microsoft for almost three years now, and I like their Bug Bounty program.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/683/1*fQvsMdz1AbymdaX_nNMOwQ.png" /></figure><p>Most of you Hunters are familiar with the following error →</p><h3>401 — Unauthorized: Access is denied due to invalid credentials.</h3><p>This error is common in web applications and APIs that require user authentication.</p><p>After running some Recon-Tools such as Subfinder, Findomain, etcetera.</p><p>I found a subdomain which was interesting, I will call it <a href="https://targetbackend.binginternal.com,/">https://targetbackend.com,</a> next I opened the previous URL in my Browser →</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*pBd-tcshWMh-cklBJdb1CQ.png" /></figure><p>But nothing has been shown to me except the Server Error!!</p><p>So, I checked the Wappalyzer Browser-Extension to determine the Web server.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/495/1*dNjiFnkESk36ggfAFrCeog.png" /></figure><p>The Web server was IIS.</p><p>You can find more about the IIS server here <a href="https://www.google.com/url?sa=t&amp;source=web&amp;rct=j&amp;opi=89978449&amp;url=https://learn.microsoft.com/de-de/iis/get-started/introduction-to-iis/iis-web-server-overview&amp;ved=2ahUKEwipksKTu5eIAxUEB9sEHex0LWAQFnoECAkQAQ&amp;usg=AOvVaw3npkS882xDb_zPqlAemqlS">https://www.google.com/url?sa=t&amp;source=web&amp;rct=j&amp;opi=89978449&amp;url=https://learn.microsoft.com/de-de/iis/get-started/introduction-to-iis/iis-web-server-overview&amp;ved=2ahUKEwipksKTu5eIAxUEB9sEHex0LWAQFnoECAkQAQ&amp;usg=AOvVaw3npkS882xDb_zPqlAemqlS</a></p><p>Internet Information Services is according to Wikipedia an extensible <a href="https://en.wikipedia.org/wiki/Web_server">web server</a> created by <a href="https://en.wikipedia.org/wiki/Microsoft">Microsoft</a> for use with the <a href="https://en.wikipedia.org/wiki/Windows_NT">Windows NT</a> family.</p><p>Usually, other hunters will try to run dirsearch or ffuf, but I have different Methodology when I’m challenged by similar situations, instead of flooding the target with hundreds of requests, I choose to append “Admin” to the end of the target server → <a href="https://targetbackend.binginternal.com,/">https://targetbackend.com</a>/Admin</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ZaSVgE6p1GkiicYulG-Tyw.png" /></figure><p>Cool, now we are in the Admin Page lol</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/833/0*ki89Zq4dwIschLIn.png" /></figure><p>Based on previous experiences with the .Net Framework Applications specially and with other Applications generally, I’ve seen the /Admin path/directory very often and you might would like to add it to your favourite wordlist.</p><p>When I tried to click on any of the Admin Content, I get redirected to authenticate against the target server!!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/440/0*HX-VzkG987Xjorxn.gif" /></figure><p>That’s it, I ended with an unhappy end, what should I do next?</p><p>Should I give up after getting this far? I could’ve run dirsearch or ffuf flooding the target server with meaningless requests which will trigger the monitoring tools and get me banned.</p><p>After thinking a lot about how to overcome this obstacle, I remembered an Article about ASP.NET Tracing Overview!!</p><p>I googled the ASP.NET Tracing Overview and to my surprise here’s what I found →</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/972/1*45AXttuP9dW2mJ8gRlaOMg.png" /></figure><p>Bingo! it might be possible to get something out of the ASP.NET Tracing Overview, let’s append “Trace.axd” to the end of the traget URL and see what would happen → <a href="https://targetbackend.binginternal.com,/">https://targetbackend.com</a>/Admin/Trace.axd</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*d6tMQLOpQgVrDkAGxRUoFA.png" /></figure><p>My reaction was:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/480/0*ADLpO7e1IoefHjU1.gif" /></figure><p>Let’s explore the View Details →</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*AUaL214aSPbYPYpffABw1w.png" /></figure><p>Me:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/266/0*xc7VjSQhB3tIe7YD.gif" /></figure><p>Finally, I scrolled down a little bit →</p><p>and …. →</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ZkTb5WKJjyw9gQpz4qUktQ.png" /></figure><p>Yes, the target Server is leaking its Variables!!!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/320/0*AjkNt3n45ABORNQQ.gif" /></figure><p>I hope that you find this Writeup helpful and that you get some useful insights from the mentioned Technics to expand your Bug Bounty Journey.</p><p>If you like Azure and Microsoft365 like me, I highly recommend you hunt on the Microsoft Bug Bounty Program, because they have a wide scope where you can sharpen your hacking skills and find some crazy Bugs :)</p><p>Here’s where to register and find more →<br><a href="https://www.microsoft.com/en-us/msrc/bounty">https://www.microsoft.com/en-us/msrc/bounty</a><br>Read the program descriptions before you start to hunt.</p><p>Here are some inspiring Hackers to follow on twitter to help you understand how they hunt on Microsoft →</p><p><a href="https://x.com/DrAzureAD">https://x.com/DrAzureAD</a><br><a href="https://x.com/hillai">https://x.com/hillai</a></p><p>Where to find me →<br>Twitter: <a href="https://x.com/panther86_black">BlackPanther86 (@panther86_black) / X</a><br>Linkedin: <a href="http://www.linkedin.com/in/mohamed-abdalah-bashir-322b941b2">www.linkedin.com/in/mohamed-abdalah-bashir-322b941b2</a></p><p>Thank you and Happy Hacking …</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/480/0*XpSt0gEqBmdwCZ5f.gif" /></figure><h3>Timeline:</h3><p>30 Jul 2024, 17:00 reported to MSRC.</p><p>30 Jul 2024, 17:01 POC was uploaded.</p><p>30 Jul 2024, 17:01 <strong>Status </strong>changed to New.</p><p>30 Jul 2024, 18:48 <strong>Status </strong>changed from New to Review / Repro.</p><p>30 Jul 2024, 19:49 <strong>Status </strong>changed from Review / Repro to Planning.</p><p>22 Aug 2024, 23:25 Status changed to accepted and The Microsoft Bounty team is reviewing the case 89941 for a possible bounty award under the <a href="https://www.microsoft.com/en-us/msrc/bounty">Microsoft Bounty Programs</a>.</p><p>26 Aug 2024, 17:09 <strong>Status </strong>changed from Planning to Develop, and changed from Develop to Pre-Release.</p><p>26 Aug 2024, 17:11 <strong>Status </strong>changed from Pre-Release to Complete. and from Complete to Complete.<br>27 Aug 2024, 22:29 Email communication with MSRC.</p><p>16 Sept 2024, 20:12 I got notified that the reported issue was eligible for a bounty reward and the MSRC Team asked to provide a bounty award payment provider.</p><p>17 Sept 2024, bounty award payment provider has been provided to the MSRC Team.</p><p>18 Sept bounty reward has been issued to the award payment provider (intigriti)</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=53b086379a08" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>