<?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 Punisher on Medium]]></title>
        <description><![CDATA[Stories by Punisher on Medium]]></description>
        <link>https://medium.com/@punisher10?source=rss-3df21faad5d8------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*DHoqey0ah26vjIfRs_tIrQ.jpeg</url>
            <title>Stories by Punisher on Medium</title>
            <link>https://medium.com/@punisher10?source=rss-3df21faad5d8------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sat, 21 Nov 2026 08:50:08 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@punisher10/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 Found a Broken Access Control Vulnerability Exposing Private Chat Media]]></title>
            <link>https://medium.com/@punisher10/how-i-found-a-broken-access-control-vulnerability-exposing-private-chat-media-05da6c0ffe45?source=rss-3df21faad5d8------2</link>
            <guid isPermaLink="false">https://medium.com/p/05da6c0ffe45</guid>
            <dc:creator><![CDATA[Punisher]]></dc:creator>
            <pubDate>Fri, 08 May 2026 15:08:30 GMT</pubDate>
            <atom:updated>2026-05-08T15:40:28.642Z</atom:updated>
            <content:encoded><![CDATA[<blockquote>A walkthrough of how predictable identifiers and missing authentication checks can break user privacy at scale.</blockquote><p>Access control bugs are some of the most impactful vulnerabilities you can find in a web application. They’re often hiding in plain sight — not in complex cryptographic logic, but in the simple question: <em>does this server actually check if you’re allowed to see this?</em></p><p>This is the story of how I identified an Insecure Direct Object Reference (IDOR) vulnerability in the chat feature of a private bug bounty program, discovered during a routine testing session in March 2026.</p><blockquote>This writeup respects responsible disclosure. No specific target details, endpoints, file types, or payloads are shared. The vulnerability has been confirmed and resolved by the program.</blockquote><h3>How it started</h3><p>When testing chat functionality, I always intercept and analyze media URLs. Most platforms store uploaded files with some kind of identifier in the path. The interesting question is always: <em>what kind of identifier, and is access properly gated?</em></p><p>After sending a file through the chat, I captured the direct URL where it was stored. The URL contained a UUID, which at first glance looks random and unguessable, and therefore “safe.” But there were two problems.</p><h3>Problem 1 — No authentication check</h3><p>Opening the URL in an incognito browser, completely logged out, returned the file without any authentication challenge. The server never verified identity.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/945/1*TMNcMW6Jx4MrCYaqVRVjiQ.png" /><figcaption>Figure — File</figcaption></figure><h3>Problem 2 — Enumerable identifiers</h3><p>Not all UUIDs are created equal. Some UUID implementations have characteristics that make them partially predictable or enumerable in bulk. Generating a wordlist of plausible candidates and running an enumeration tool against the endpoint revealed valid UUIDs belonging to other users.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*mgPkSdOpK9DyyQ0KT9WvLw.png" /><figcaption>Figure — Fuzz</figcaption></figure><h3>The Attack Flow 💀</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*9HUjtgL7Iyg2QcrUsgFe6Q.jpeg" /><figcaption>Figure — The Attack Flow</figcaption></figure><h3>Why this matters</h3><p>A common misconception is that “the URL is long and random, so it’s fine.” Security through obscurity is not access control. Without server-side authorization checks, any sufficiently motivated attacker with a fuzzer can systematically harvest private media at scale.</p><p>🔓 <strong>Unauthorized access to private content</strong></p><p><strong>⚙️ Automatable at scale via fuzzing</strong></p><p>🕵️ <strong>No authentication required</strong></p><p>⚖️ <strong>Potential regulatory exposure</strong></p><h3>The fix</h3><p>The correct remediation for this class of vulnerability is straightforward in principle: every request to a stored file must be validated server-side. The server should verify that the requesting user’s session corresponds to a participant in the conversation where that file was shared.</p><p>Complementary mitigations include short-lived signed URLs (where access tokens expire after a few minutes), rate limiting on media endpoints, and anomaly detection for enumeration patterns.</p><h3>Key takeaways for hunters</h3><p>When testing storage and media endpoints:</p><p>-&gt; Always capture and analyze resource URLs from network traffic<br>-&gt; Test direct URL access without authentication<br>-&gt; Check if identifiers are sequential, UUID v1, or otherwise enumerable<br>-&gt; Test with a second account — does account B access account A’s content?<br>-&gt; Don’t assume UUIDs = security</p><p><strong>Enjoyed this deep dive?</strong></p><p>If you found this write-up helpful or want to discuss more about bug hunting, recon automation, and web security, let’s connect on LinkedIn!</p><p>🔗 <a href="https://www.linkedin.com/in/pedro-giglioti/">https://www.linkedin.com/in/pedro-giglioti/</a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/390/1*2P345Fo1qm7ylpG_9cjBPA.png" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=05da6c0ffe45" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>