<?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 Jahswill Eke on Medium]]></title>
        <description><![CDATA[Stories by Jahswill Eke on Medium]]></description>
        <link>https://medium.com/@6ame0va?source=rss-1e16f2f87940------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*RYWmKjF8H2NlUaWj8cBVmA.jpeg</url>
            <title>Stories by Jahswill Eke on Medium</title>
            <link>https://medium.com/@6ame0va?source=rss-1e16f2f87940------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sun, 22 Nov 2026 23:25:10 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@6ame0va/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[Don’t Rush the Report: How Patience Turns “Low Impact” Bugs Into Real Findings]]></title>
            <link>https://6ame0va.medium.com/dont-rush-the-report-how-patience-turns-low-impact-bugs-into-real-findings-970eb2ef6771?source=rss-1e16f2f87940------2</link>
            <guid isPermaLink="false">https://medium.com/p/970eb2ef6771</guid>
            <dc:creator><![CDATA[Jahswill Eke]]></dc:creator>
            <pubDate>Wed, 04 Feb 2026 14:28:23 GMT</pubDate>
            <atom:updated>2026-02-04T14:28:23.531Z</atom:updated>
            <content:encoded><![CDATA[<blockquote><strong><em>Disclosure &amp; Redaction Notice</em></strong><em><br>This article is written strictly for </em><strong><em>educational purposes</em></strong><em>.<br>All domains, endpoints, parameters, tokens, screenshots, and identifiers have been </em><strong><em>redacted or replaced with placeholders</em></strong><em> (e.g. </em><em>example.com).<br>No sensitive systems or users are exposed.</em></blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*oN9WBXPHR9jOAtxQFU8BFA.png" /></figure><blockquote><strong><em>The most valuable skill isn’t how fast you submit a report — it’s patience.</em></strong></blockquote><p>Early on, I rushed to report anything that looked suspicious.<br>Most of those reports ended up as <em>informational</em>, <em>low impact</em>, or <em>duplicate</em>.</p><p>What changed everything was learning to <strong>slow down and chain findings</strong>.</p><h3>The “Small” Bug That Many Beginners Would Report Immediately</h3><p>While testing a web application, I noticed an OAuth login endpoint that accepted a parameter called redirect_uri.</p><p>At first glance, it looked harmless.</p><p>To many beginners, this would be submitted as:</p><ul><li><em>“Open redirect”</em></li><li><em>“Low severity”</em></li><li><em>“Probably informational”</em></li></ul><p>But before rushing to report it, I stopped and asked a simple question:</p><blockquote>Why does this parameter exist in the first place?</blockquote><h3>Quick Detour: What Is an Open Redirect?</h3><p>An <strong>open redirect</strong> happens when an application allows users to control where they are redirected <strong>without proper validation</strong>.</p><h3>Why Developers Use Redirects</h3><p>Redirects are extremely common and legitimate.</p><p>Developers use them for things like:</p><ul><li>Sending users back to the page they originally wanted after login</li><li>Redirecting users after password reset</li><li>Supporting third‑party authentication (OAuth, SSO)</li></ul><h3>A Normal, Safe Example</h3><pre>https://example.com/login?redirect=/dashboard</pre><p>After login, the app redirects the user to:</p><pre>https://example.com/dashboard</pre><p>This is expected behavior.</p><h3>Where It Goes Wrong</h3><p>If the app <strong>doesn’t validate</strong> the redirect destination, an attacker could do this:</p><pre>https://example.com/login?redirect=https://attacker.example</pre><p>Now the user logs in…<br>…and gets redirected to a <strong>malicious site</strong>.</p><p>On its own, this is often considered <strong>low impact</strong>.</p><p>But context matters.</p><h3>Why I Didn’t Submit It Yet</h3><p>In my case, the redirect parameter was part of an <strong>OAuth login flow</strong>.</p><p>That immediately raised red flags.</p><p>Instead of submitting an “open redirect” report, I asked:</p><ul><li><em>What data passes through this redirect?</em></li><li><em>Is anything sensitive included?</em></li><li><em>What happens during the full login flow?</em></li></ul><p>That patience paid off.</p><h3>When a Small Bug Turns Dangerous</h3><p>The OAuth flow used an <strong>implicit grant</strong> (response_type=token), meaning access tokens were returned in the URL fragment after login.</p><p>By carefully modifying the redirect destination to a server I controlled (redacted here), I observed something critical:</p><blockquote><strong><em>The user’s OAuth access token was sent to the redirect endpoint.</em></strong></blockquote><p>This transformed the issue from:</p><ul><li>“Open redirect”<br>into</li><li><strong>Account takeover via token hijacking</strong></li></ul><h3>Chaining the Impact</h3><p>Once the token was captured:</p><ul><li>I replaced my own token in API requests with the victim’s token</li><li>The application accepted it</li><li>All requests executed as the victim</li></ul><p>At that point, the impact was clear:<br><strong>Full account takeover</strong></p><p>This wasn’t a single bug.<br>It was a <strong>chain of small issues</strong> that only became visible by slowing down.</p><h3>The Lesson for Beginners</h3><p>If you’re new to bug bounty, this is the key takeaway:</p><h3>⚠️ Don’t rush to report the first issue you see</h3><p>Instead:</p><ul><li>Ask <em>why</em> something exists</li><li>Understand the <strong>full flow</strong></li><li>Look for <strong>what else depends on it</strong></li><li>See how small weaknesses interact</li></ul><p>Many critical vulnerabilities <strong>start as informational findings</strong>.</p><h3>Practical Advice for Aspiring Bug Hunters</h3><ol><li><strong>Slow Down</strong><br>Speed doesn’t win bounties — impact does.</li><li><strong>Learn Common Concepts</strong><br>OAuth, redirects, tokens, sessions — understanding these turns noise into signal.</li><li><strong>Chain Thoughtfully</strong><br>One bug rarely stands alone.</li><li><strong>Be Patient With Yourself</strong><br>Every “duplicate” or “informational” teaches you something.</li></ol><h3>Final Thoughts</h3><p>Bug bounty isn’t about finding <em>more</em> bugs.</p><p>It’s about finding <strong>better ones</strong>.</p><blockquote><em>The difference between an informational report and a critical one<br>is often just </em><strong><em>patience and curiosity</em></strong><em>.</em></blockquote><p>If you’re starting out, don’t get discouraged.<br>Slow down.<br>Dig deeper.<br>And never underestimate a “small” bug.</p><p>Thanks for reading 🤝<br>More beginner‑friendly write‑ups coming soon — focused on mindset, learning, and real‑world security lessons.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=970eb2ef6771" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How a Single Unauthenticated API Request Exposed Cloud Credentials ($1,000 Bug Bounty)]]></title>
            <link>https://6ame0va.medium.com/how-a-single-unauthenticated-api-request-exposed-cloud-credentials-1-000-bug-bounty-26d2de63ecff?source=rss-1e16f2f87940------2</link>
            <guid isPermaLink="false">https://medium.com/p/26d2de63ecff</guid>
            <dc:creator><![CDATA[Jahswill Eke]]></dc:creator>
            <pubDate>Wed, 04 Feb 2026 12:09:06 GMT</pubDate>
            <atom:updated>2026-02-04T13:02:39.276Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*gIo5shZx3qbtEQdeCPWj1g.png" /></figure><blockquote><strong><em>Disclosure &amp; Redaction Notice</em></strong><em><br>This article is written for </em><strong><em>educational purposes only</em></strong><em>.<br>All domains, endpoints, headers, parameters, identifiers, and values have been </em><strong><em>fully redacted or replaced with placeholders</em></strong><em> (e.g. </em><em>example.com).<br>No real systems, credentials, or infrastructure details are exposed.</em></blockquote><p>When people imagine critical security bugs, they often think of complex exploits, clever payloads, or long attack chains.</p><p>This experience taught me something far more important:</p><blockquote><strong><em>Critical vulnerabilities often reveal themselves quietly — inside “normal” responses.</em></strong></blockquote><h3>The Context</h3><p>While analyzing a mobile backend API, I sent what looked like a routine request.<br>No authentication.<br>No valid session.<br>Nothing special.</p><p>The response wasn’t an error — it was <strong>successful</strong>.</p><p>That alone should already make a tester pause.</p><p>But the real lesson didn’t come from that single request.</p><h3>The Noise Most People Ignore</h3><p>As soon as that endpoint was hit, the application automatically triggered <strong>20+ background API calls</strong>.</p><p>This is completely normal in modern applications:</p><ul><li>Telemetry</li><li>Logging</li><li>Analytics</li><li>Initialization calls</li><li>Internal service communication</li></ul><p>And this is where a very common habit shows up.</p><h3>Why It’s Easy to Skip These Requests</h3><p>When dozens of requests fire at once, it’s very easy to:</p><ul><li>Skim over them quickly</li><li>Assume they’re harmless “app noise”</li><li>Focus only on the request you manually sent</li></ul><p>Most testers are trained to look for:</p><ul><li>Errors</li><li>Crashes</li><li>Obvious failures</li></ul><p>So when a background request quietly returns 200 OK, it rarely gets attention.</p><p>But background traffic is often where applications:</p><ul><li>Fetch configuration</li><li>Request internal tokens</li><li>Talk to cloud services</li><li>Expose infrastructure details</li></ul><p>Skipping these requests doesn’t just save time — <br>it can mean skipping the <strong>most sensitive response in the entire flow</strong>.</p><h3>Following the Background Calls</h3><p>Instead of ignoring them, I decided to <strong>analyze each background call individually</strong>, one by one.</p><p>Most of them looked ordinary.</p><p>Then one stood out — not because the request was special, but because the <strong>response was too informative</strong>.</p><p>No authentication.<br>No user context.<br>No obvious warning signs.</p><p>So I slowed down and inspected it carefully.</p><h3>The Request (Redacted Example)</h3><p>Below is a <strong>sanitized example</strong> of the type of background request that deserved closer attention:</p><pre>POST /heyGiveMeTheCloudCredecialsMan HTTP/1.1<br>Host: api.example.com<br>Content-Type: application/json<br>User-Agent: mobile-client/1.0</pre><pre>{&quot;method&quot;:&quot;POST&quot;}</pre><p>Nothing fancy.<br>Nothing aggressive.</p><p>Just a background call doing its job.</p><h3>The Response (Redacted Example)</h3><p>The server responded with structured JSON:</p><pre>{<br>  &quot;success&quot;: true,<br>  &quot;result&quot;: {<br>    &quot;naYourAccessKeyIdBeThis&quot;: &quot;TEMPORARY_KEY_REDACTED&quot;,<br>    &quot;naYourAccessKeySecretBeThis&quot;: &quot;REDACTED&quot;,<br>    &quot;naYourSecurityTokenBeThis&quot;: &quot;REDACTED&quot;,<br>    &quot;naYourExpirationBeThis&quot;: &quot;YYYY-MM-DDTHH:MM:SSZ&quot;,<br>    &quot;makeSureToUseEndpoint&quot;: &quot;https://logs.examplecloud.com&quot;,<br>    &quot;noForgetProject&quot;: &quot;example-project&quot;,<br>    &quot;useThisOnelogStore&quot;: &quot;example-log-store&quot;<br>  }<br>}</pre><p>This wasn’t random metadata.</p><p>This was <strong>temporary cloud access</strong>.</p><p>Returned without authentication.<br>Returned in the background.<br>Returned quietly.</p><h3>Why This Matters</h3><p>Temporary credentials are often misunderstood.</p><p>Because they:</p><ul><li>Expire</li><li>Are scoped</li><li>Are labeled “internal”</li></ul><p>They’re sometimes treated as low risk.</p><p>That’s a dangerous assumption.</p><p>With credentials like these, an attacker could:</p><ul><li>Read production logs</li><li>Modify or inject log entries</li><li>Enumerate internal resources</li><li>Access operational or sensitive data</li></ul><p>Even short-lived access is <strong>real access</strong>.</p><h3>The Real Lesson: Noise Is Often Signal</h3><p>The main request didn’t scream “critical bug”.<br>The background calls didn’t either.</p><p>But security testing isn’t about chasing what’s loud — <br>it’s about noticing what <strong>shouldn’t be exposed at all</strong>.</p><p>Ask yourself:</p><ul><li><em>Why does this endpoint respond without identity checks?</em></li><li><em>Why is infrastructure data returned to the client?</em></li><li><em>What happens if this is abused at scale?</em></li></ul><h3>How This Changed My Testing Mindset</h3><p>This experience permanently changed how I test APIs:</p><h3>1. I Always Inspect Background Traffic</h3><p>Automated calls deserve the same scrutiny as manual ones.</p><h3>2. I Read Every Response Field</h3><p>Even configuration-looking data can be dangerous.</p><h3>3. I Treat Tokens as High-Value Assets</h3><p>Temporary ≠ harmless.</p><h3>4. I Don’t Dismiss “Working” Endpoints</h3><p>If something works without authentication, it deserves attention.</p><h3>A Note for Developers</h3><p>If an endpoint:</p><ul><li>Issues credentials</li><li>Returns tokens</li><li>Exposes cloud or infrastructure details</li></ul><p>Then <strong>authentication is not optional</strong>.</p><p>Internal endpoints are not private by default.<br>Client-side behavior is not a security boundary.</p><h3>Closing Thoughts</h3><p>This wasn’t about advanced exploitation.</p><p>It was about <strong>attention to detail</strong>.</p><blockquote><em>Sometimes the most critical bugs don’t hide behind complexity — <br>they hide behind familiarity.</em></blockquote><p>If you’re learning security, slow down.<br>Don’t skim.<br>Follow the background calls.<br>Read every response.</p><p>That’s where the real lessons are.</p><p>Thanks for reading 🤝<br>More write-ups coming — focused on mindset, observation, and real-world security learning.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=26d2de63ecff" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>