<?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 Hamza Khaled on Medium]]></title>
        <description><![CDATA[Stories by Hamza Khaled on Medium]]></description>
        <link>https://medium.com/@0xsussy?source=rss-2c437d357c4d------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*SO4-qkwmecW9vDQ2HefY7g.png</url>
            <title>Stories by Hamza Khaled on Medium</title>
            <link>https://medium.com/@0xsussy?source=rss-2c437d357c4d------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 18 Nov 2026 16:35:12 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@0xsussy/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[The Easiest $$$ I Made from a Business Logic Vulnerability]]></title>
            <link>https://medium.com/@0xsussy/the-easiest-i-made-from-a-business-logic-vulnerability-5c11a31ca455?source=rss-2c437d357c4d------2</link>
            <guid isPermaLink="false">https://medium.com/p/5c11a31ca455</guid>
            <category><![CDATA[bugbounty-writeup]]></category>
            <category><![CDATA[bugbounty-poc]]></category>
            <category><![CDATA[bug-bounty]]></category>
            <category><![CDATA[bugbounty-tips]]></category>
            <dc:creator><![CDATA[Hamza Khaled]]></dc:creator>
            <pubDate>Tue, 19 Nov 2024 09:40:34 GMT</pubDate>
            <atom:updated>2024-11-19T09:42:37.649Z</atom:updated>
            <content:encoded><![CDATA[<p>Let’s dive straight into the topic without any fluff.</p><p>Recently, I received a private invitation to test a ticket broker program — let’s call it <a href="http://www.example.com/"><strong>www.example.com</strong></a> for the sake of this write-up.</p><blockquote>A ticket broker is essentially a platform that facilitates the resale of event tickets, often at a premium above the original face value. Naturally, this kind of platform thrives on dynamic pricing — similar to airline tickets — where prices fluctuate based on demand, availability, and time.</blockquote><p>When hunting for vulnerabilities on any platform, my first and most important step is to explore the domain thoroughly. Understanding the business model and its core functionalities is crucial. For this particular platform, I noted that ticket prices were highly dynamic, increasing as more buyers purchased tickets or as the event drew closer.</p><p>While exploring, I noticed something interesting during the checkout process. The platform offered a <strong>10-minute price lock</strong>, which temporarily froze the ticket price while a countdown timer ran.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/443/1*qDYh_LXM465-8gSuKQAgKw.png" /></figure><p>This intrigued me. A question popped into my head: <em>What if this timer relies on the client-side device clock instead of a server-side implementation? Could I manipulate my device’s clock to extend the price lock period?</em></p><p>So I Navigated to <strong>Settings &gt; Adjust Date and Time</strong> on my device</p><p>and Turned off the “Set time automatically” option.</p><p>Manually set the clock back by <strong>19 minutes</strong>.</p><p>When I returned to the checkout page, I was astonished. The countdown timer jumped from a few remaining seconds to <strong>27:00</strong> minutes. The price lock period had been extended beyond the platform’s intended 10 minutes!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/128/1*Tgul6asEK1Nu2cmliSIuFg.png" /></figure><p>I pushed the experiment further. By repeatedly resetting my device clock, I was able to extend the timer indefinitely — up to <strong>60 minutes </strong>. Essentially, this meant I could bypass the platform’s time-limited price lock mechanism, holding onto a ticket at a frozen price for as long as I wanted.</p><p>lesson learned: Whenever you encounter a timer-based feature on any platform — be it a countdown for price locks, retrying passwords, or similar functionality — try manipulating your device’s clock to see if it’s vulnerable to client-side dependency.</p><p>I reported it and got a $$$ bounty</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/361/1*0-hJ9kkmiLyPv4bNyB-wMw.png" /></figure><p>My social media accounts For more writeups</p><p><a href="https://x.com/__0sussy0">https://x.com/__0sussy0</a></p><p><a href="http://www.linkedin.com/in/hamza-khaled--">www.linkedin.com/in/hamza-khaled--</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5c11a31ca455" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>