<?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 CH3TAN on Medium]]></title>
        <description><![CDATA[Stories by CH3TAN on Medium]]></description>
        <link>https://medium.com/@ch3tanbug?source=rss-132fa5fb717f------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*B1m5MxPFyg5Fb_knQ-Wu_A.jpeg</url>
            <title>Stories by CH3TAN on Medium</title>
            <link>https://medium.com/@ch3tanbug?source=rss-132fa5fb717f------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sat, 21 Nov 2026 15:13:12 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@ch3tanbug/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[Mastering Runtime Hooking with Frida — Real-World Challenges (Part 3)]]></title>
            <link>https://medium.com/@ch3tanbug/mastering-runtime-hooking-with-frida-real-world-challenges-part-3-b70a62ed4395?source=rss-132fa5fb717f------2</link>
            <guid isPermaLink="false">https://medium.com/p/b70a62ed4395</guid>
            <category><![CDATA[bug-bounty]]></category>
            <category><![CDATA[reverse-engineering]]></category>
            <category><![CDATA[jadx]]></category>
            <category><![CDATA[mobile-security]]></category>
            <category><![CDATA[cybersecurity]]></category>
            <dc:creator><![CDATA[CH3TAN]]></dc:creator>
            <pubDate>Tue, 06 May 2025 08:24:53 GMT</pubDate>
            <atom:updated>2025-05-06T08:27:32.156Z</atom:updated>
            <content:encoded><![CDATA[<h3>Mastering Runtime Hooking with Frida — Real-World Challenges (Part 3)</h3><p>Hey folks, welcome back! This is Chetan Kashyap, and I’m excited to bring you <strong>Part 3</strong> of my ongoing series on <strong>runtime hooking using Frida</strong>. If you’re new here or haven’t checked out the previous parts, I recommend reading <a href="https://medium.com/@ch3tanbug/mastering-runtime-hooking-with-frida-real-world-challenges-explained-part-1-17a7f57ea87b">Part 1</a> and <a href="https://medium.com/@ch3tanbug/mastering-runtime-hooking-with-frida-real-world-challenges-explained-part-2-2520d7b1e10c">Part 2</a> first to get the full context.</p><p>So far in this series, we’ve explored how to intercept method calls, override return values, and hook static functions using Frida. These are all incredibly powerful techniques for analyzing and modifying app behavior dynamically — especially when you don’t have access to the source code.</p><p>In today’s article, we’ll be taking things a step further by demonstrating <strong>how to dynamically change the value of a class variable at runtime</strong> to bypass application logic and access privileged functionality — in this case, decrypting a hidden flag.</p><p>As always, the challenge APK used in this lab is available in my <a href="https://github.com/ch3tanbug/runtime-hooking-labs">GitHub repository</a>, so feel free to follow along and practice!</p><h3><strong>🔍 APK Analysis: Understanding the App’s Logic</strong></h3><p>The first step in our analysis — just like before — is to <strong>decompile the APK using JADX</strong> and perform a <strong>static analysis</strong> of the code.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/756/1*aOum9iwJ1UctGQuDbA_JIw.png" /><figcaption>Using APK without hooking</figcaption></figure><p>Upon inspecting the AndroidManifest.xml, we once again notice that the MainActivity is marked as exported=true. This setting means that other apps can interact with this component directly, which opens the door to various attack vectors if proper access control isn’t implemented.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*4_FABUMO3WGPkOdBQRjSbQ.png" /><figcaption>MainActivity exported=true</figcaption></figure><p>Next, we dive into the MainActivity class. Inside the onClick() method, we come across an interesting conditional statement:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*mv-mh6SM7dLaMqc2UETgtw.png" /><figcaption>Main Activiity</figcaption></figure><p>So, it’s clear that <strong>if the value of </strong><strong>code from the </strong><strong>Checker class is 512</strong>, the application will decrypt and show the flag. Otherwise, it simply returns a generic message.</p><p>Now, let’s take a closer look at the Checker class.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*9oYheYVNP2wu3pck8K2QEA.png" /><figcaption>Checker Class</figcaption></figure><p>Here’s what we know:</p><ul><li>The code variable is declared as static and initialized to 0.</li><li>There’s a static method increase() that increments the value of code by 2 every time it&#39;s called.</li><li>Surprisingly, this method isn’t called anywhere in MainActivity.</li></ul><p>This gives us a strong hint: <strong>instead of figuring out a way to trigger </strong><strong>increase() repeatedly, we can directly set the value of </strong><strong>code to 512 at runtime</strong> using Frida, thus satisfying the condition in onView() and getting the flag.</p><h3><strong>🧪 Hooking Time: Modifying Class Variables with Frida</strong></h3><p>Now that we understand the control flow and behavior, it’s time to take action using Frida.</p><p>Our goal is to:</p><ul><li>Hook into the Checker class.</li><li>Directly set the value of the code variable to 512 before the conditional check in onClick() is executed.</li></ul><p>Here’s the <strong>Frida script</strong> I wrote for this task:</p><pre>Java.perform(() =&gt; {<br> var cls = Java.use(&quot;com.ad2001.frida0x3.Checker&quot;);<br> cls.code.value = 512;<br>});</pre><p>This simple yet powerful script uses Frida’s Java.use() API to hook into the Checker class. We then set the value of the static variable code directly.</p><p>To execute this, we attach Frida to the target app using:</p><pre>frida -l ./lab-03.js -F -U</pre><p>Once our script is loaded and the condition in MainActivity is triggered, we immediately see the result: <strong>the flag gets decrypted and shown on the screen!</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/756/1*jHCOSPFS4tphW0KUJc-Dgw.png" /><figcaption>App retrieved after hooking</figcaption></figure><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fplayer.vimeo.com%2Fvideo%2F1081740129%3Fapp_id%3D122963&amp;dntp=1&amp;display_name=Vimeo&amp;url=https%3A%2F%2Fvimeo.com%2F1081740129&amp;image=https%3A%2F%2Fi.vimeocdn.com%2Fvideo%2F2012583158-311c0e656d9fb4f4930d0523f6c24d3ede62480e8f8a019efdcf8166f2b54212-d_1280&amp;type=text%2Fhtml&amp;schema=vimeo" width="1920" height="1080" frameborder="0" scrolling="no"><a href="https://medium.com/media/8037fb6a8e511c052fa8efb26ca4ca34/href">https://medium.com/media/8037fb6a8e511c052fa8efb26ca4ca34/href</a></iframe><h3><strong>🎯 Key Takeaways</strong></h3><p>This lab beautifully demonstrates one of Frida’s most useful capabilities — <strong>runtime variable modification</strong>. Here are the core lessons from this exercise:</p><ul><li><strong>Static analysis</strong> helps us identify key logic and variables worth targeting.</li><li>Misconfigurations like exported=true can make components easily accessible to attackers.</li><li>Frida allows us to <strong>interact with and manipulate Java classes and variables</strong> in memory, without modifying the APK or source code.</li><li>Being able to change class variables at runtime can <strong>bypass validation, trigger hidden features, or unlock premium functionality</strong>, which has both offensive and defensive implications in security research.</li></ul><h3><strong>🧠 Final Thoughts</strong></h3><p>In the real world, apps often rely on runtime variables for enforcing access control or managing internal states. With tools like Frida, these can be intercepted and manipulated — making it critical for developers to build layered defenses and avoid relying solely on client-side checks.</p><p>I hope you found this deep dive into variable manipulation insightful and helpful in your journey through mobile application security. If you have any questions, suggestions, or feedback, feel free to drop a comment or reach out to me on <a href="https://linkedin.com/in/chetan-kashyap">LinkedIn</a>. And if you enjoyed the article, a clap or share would mean a lot!</p><p>Stay tuned for <strong>Part 4</strong>, where we’ll tackle more advanced real-world mobile app challenges with Frida.</p><p>Thanks for reading.<br> Until next time — Cheers!<br> — <em>Chetan Kashyap</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b70a62ed4395" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Mastering Runtime Hooking with Frida — Real-World Challenges Explained (Part 2)]]></title>
            <link>https://medium.com/@ch3tanbug/mastering-runtime-hooking-with-frida-real-world-challenges-explained-part-2-2520d7b1e10c?source=rss-132fa5fb717f------2</link>
            <guid isPermaLink="false">https://medium.com/p/2520d7b1e10c</guid>
            <category><![CDATA[reverse-engineering]]></category>
            <category><![CDATA[android-pentesting]]></category>
            <category><![CDATA[hackerone]]></category>
            <category><![CDATA[frida]]></category>
            <category><![CDATA[bug-bounty]]></category>
            <dc:creator><![CDATA[CH3TAN]]></dc:creator>
            <pubDate>Thu, 01 May 2025 18:31:49 GMT</pubDate>
            <atom:updated>2025-05-01T18:39:44.270Z</atom:updated>
            <content:encoded><![CDATA[<h3>Mastering Runtime Hooking with Frida — Real-World Challenges Explained (Part 2)</h3><p>Hey folks! This is <strong>Chetan Kashyap</strong>, back again with <strong>Part 2</strong> of our series on mastering runtime hooking using <strong>Frida</strong>. If you haven’t already, I highly recommend checking out <a href="https://medium.com/@ch3tanbug/mastering-runtime-hooking-with-frida-real-world-challenges-explained-part-1-17a7f57ea87b">Part 1</a> before diving into this one — we covered the basics of hooking instance methods and overriding return values dynamically.</p><p>Now, in this article, we’re stepping it up a notch by exploring how to hook <strong>static methods</strong>, which is a crucial technique when dealing with Android apps in real-world scenarios. As always, the challenge APK used in this article can be found in the <a href="https://github.com/ch3tanbug/runtime-hooking-labs">GitHub repository.</a></p><h3>🔍 Analyzing the APK</h3><p>As with any reverse engineering challenge, our first step is to <strong>decompile the APK using JADX</strong> and perform a static analysis of the app’s codebase.</p><p>Upon inspecting the AndroidManifest.xml, we observe that the MainActivity is marked as exported=true. This setting implies that the activity can be launched by other applications or tools, which makes it accessible for our testing via Frida.</p><p>Digging into the MainActivity, we identify a static method named get_flag(int a). The logic inside this method is fairly straightforward:</p><ul><li>It accepts an integer as a parameter.</li><li>If the passed integer matches the hardcoded value 4919, the app proceeds to execute a block of code inside a try block that decrypts and reveals the flag.</li></ul><p>This clearly sets up an opportunity for us to hook and exploit the static method at runtime.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*IvUxSkBVHPmN4bb9rjZTMQ.png" /><figcaption>Main Activity Being exported</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*K8cNGmYKlXT5xxZqnjjkig.png" /><figcaption>MainActivity</figcaption></figure><h3>🧪 Hooking Time</h3><p>Now that we have a good understanding of the APK structure and the method responsible for flag decryption, it’s time to <strong>hook the static method</strong> using Frida.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/746/1*zSI6xVUWFBagioBjLsItrw.png" /><figcaption>Normal Flow Of Apk</figcaption></figure><p>Unlike instance methods, static methods don’t require an object instance to be invoked, which makes them easier to call directly once you know the class structure. Here’s the plan:</p><ul><li>Use Frida to attach to the running app.</li><li>Hook into the static method get_flag.</li><li>Directly call it with the required value, i.e., 4919.</li><li>Retrieve the flag without interacting with the app’s UI.</li></ul><p>Here’s a sample Frida script that accomplishes this:</p><pre>Java.perform(()=&gt;{<br>    const Activity = Java.use(&quot;com.ad2001.frida0x2.MainActivity&quot;);<br>    Activity.get_flag(4919);<br>})</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/746/1*qjSEZt0E7hF8j5FMeW-3cQ.png" /><figcaption>Flag After Hooking</figcaption></figure><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fplayer.vimeo.com%2Fvideo%2F1080623276%3Fapp_id%3D122963&amp;dntp=1&amp;display_name=Vimeo&amp;url=https%3A%2F%2Fvimeo.com%2F1080623276&amp;image=https%3A%2F%2Fi.vimeocdn.com%2Fvideo%2F2011236017-4ff2fc70889ee811e82f33173e43117dd5f0064efc4b40818277da8e8a582c05-d_1280&amp;type=text%2Fhtml&amp;schema=vimeo" width="1920" height="1080" frameborder="0" scrolling="no"><a href="https://medium.com/media/714bbf6876f83a253e5b9e8a635d8e63/href">https://medium.com/media/714bbf6876f83a253e5b9e8a635d8e63/href</a></iframe><p>After attaching the script to the process using Frida, we instantly see the decrypted flag printed in the console — proving that the static method has been successfully hooked and manipulated.</p><h3>🎯 Why This Matters</h3><p>This lab showcases an important aspect of mobile application security — <strong>how attackers can hook and abuse static methods</strong> to bypass restrictions, access protected features, or retrieve sensitive data.</p><p>In real-world scenarios, you may come across static utility methods performing checks for:</p><ul><li>License validation</li><li>Unlocking premium features</li><li>Decrypting hidden flags or secrets</li><li>Security enforcement logic</li></ul><p>Understanding how to identify and manipulate such methods at runtime is a powerful skillset for any security researcher, reverse engineer, or mobile application pentester.</p><h3>🧩 Conclusion</h3><p>To sum it up, this lab reinforces the concept that <strong>runtime hooking isn’t limited to just instance methods</strong>. With the right tools and understanding, even static methods can be hijacked to alter an app’s behavior or gain deeper insights into its internal logic.</p><p>This kind of dynamic analysis is incredibly useful when auditing third-party apps, performing security assessments, or researching malicious Android samples.</p><p>That’s it for today’s challenge!<br> Stay tuned for <strong>Part 3</strong>, where we’ll continue our deep dive into real-world exploitation cases and cover more advanced Frida use cases.</p><p>If you have any questions, feel free to drop them in the comments or reach out to me on <a href="https://www.linkedin.com/in/chetan-kashyap/">LinkedIn</a>. And if you found this helpful, don’t forget to give it a clap and share it with fellow learners.</p><p><strong>Happy reversing!</strong><br> — <em>Chetan Kashyap</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2520d7b1e10c" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Mastering Runtime Hooking with Frida — Real-World Challenges Explained (Part -1)]]></title>
            <link>https://medium.com/@ch3tanbug/mastering-runtime-hooking-with-frida-real-world-challenges-explained-part-1-17a7f57ea87b?source=rss-132fa5fb717f------2</link>
            <guid isPermaLink="false">https://medium.com/p/17a7f57ea87b</guid>
            <category><![CDATA[bug-bounty]]></category>
            <category><![CDATA[cybersecurity]]></category>
            <category><![CDATA[reverse-engineering]]></category>
            <category><![CDATA[frida]]></category>
            <category><![CDATA[android-pentesting]]></category>
            <dc:creator><![CDATA[CH3TAN]]></dc:creator>
            <pubDate>Tue, 29 Apr 2025 19:29:44 GMT</pubDate>
            <atom:updated>2025-04-29T19:37:10.539Z</atom:updated>
            <content:encoded><![CDATA[<h3>Mastering Runtime Hooking with Frida — Real-World Challenges Explained (Part -1)</h3><p>Hey folks! I know it’s been a while since I last published an article — but hey, better late than never, right? For those of you who are new here, I’m <strong>Chetan Kashyap</strong>, a security engineer passionate about digging into the internals of mobile applications. While there’s a wealth of content online about web pentesting, the mobile security space is still vastly underexplored.</p><p>In this series, we’re diving deep into <strong>real-world challenges</strong> to uncover how <strong>runtime hooking</strong> works using <strong>Frida</strong>, a powerful tool that every reverse engineer and mobile security enthusiast should have in their toolkit.</p><p>Please find all the labs uploaded on <a href="https://github.com/ch3tanbug/runtime-hooking-labs">Github</a>.</p><p>Let’s jump in.</p><h3><strong>🚀 What Is Frida?</strong></h3><p><strong>Frida</strong> is a dynamic instrumentation framework that lets you inject your own code into running applications. Think of it as your Swiss Army knife for reverse engineering, debugging, and dynamic analysis.</p><p>With Frida, you can:</p><ul><li>Hook into functions without source code access</li><li>Trace internal behavior of black-box apps</li><li>Intercept and modify network traffic</li><li>Spy on or override internal logic — all in real time</li></ul><p>All this is done using <strong>JavaScript</strong>, making Frida incredibly flexible and developer-friendly.</p><h3><strong>🧠 What Is Runtime Hooking?</strong></h3><p><strong>Runtime hooking</strong> refers to intercepting or modifying how an app behaves <strong>while it’s running</strong> — without touching the source code or recompiling the app.</p><p>In the Android world, runtime hooking is used for:</p><ul><li>Reverse engineering</li><li>Debugging</li><li>Mobile app security testing</li><li>Game hacking</li><li>App feature customization</li></ul><p>By changing the runtime behavior of classes or functions, we can manipulate application logic and uncover vulnerabilities that would otherwise go unnoticed.</p><p>Tools like <strong>Frida</strong> and <strong>Objection</strong> make this process simpler. While Frida provides the core hooking capabilities, Objection builds on top of it to offer a user-friendly interface for mobile security assessments — no custom scripting needed.</p><h3>🎯 The Challenge: Understand &amp; Exploit Runtime Behavior</h3><p>After decompiling the app using <strong>Jadx</strong>, we see that the MainActivity is exported. Within it, we discover two critical functions:</p><ul><li>get_random() – generates a random number</li><li>check() – compares user input with a calculated result using this formula: (i * 2) + 4 == i2</li><li>where i is the random number and i2 is the user’s input.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*3aEXgPsLQdj3qZ5asORQ5Q.png" /><figcaption>Main Activity exported=true</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*XZB6oVsFmmhGuyLbFPXdEw.png" /><figcaption>Main Activity Logic</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/930/1*DfowCNsSjIA62PkgHODz2Q.png" /><figcaption>Error when wrong number is entered</figcaption></figure><h3>🔧 Time to Hook</h3><p>The goal? Hook the get_random() method to <strong>return a predictable value</strong> instead of a random one. For instance, if we make get_random() always return 1, then: (1 * 2) + 4 == 6</p><p>So the correct answer will <strong>always be 6</strong>. This completely defeats the purpose of randomness, letting us win the challenge every time.</p><p>Here’s a simple Frida script to hook and override the return value of get_random() (full video walkthrough linked below):</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fplayer.vimeo.com%2Fvideo%2F1079928337%3Fapp_id%3D122963&amp;dntp=1&amp;display_name=Vimeo&amp;url=https%3A%2F%2Fvimeo.com%2F1079928337&amp;image=https%3A%2F%2Fi.vimeocdn.com%2Fvideo%2F2010411286-d8965daff2a288467c85213e5d60f4e04f85872ed04392cbe6a04bf61d2ee6c0-d_1280&amp;type=text%2Fhtml&amp;schema=vimeo" width="1920" height="1080" frameborder="0" scrolling="no"><a href="https://medium.com/media/b0de620d6f82b2cc6f2678ae67e8868f/href">https://medium.com/media/b0de620d6f82b2cc6f2678ae67e8868f/href</a></iframe><pre>Java.perform(()=&gt;{<br>    const Activity = Java.use(&quot;com.ad2001.frida0x1.MainActivity&quot;);<br>    Activity.get_random.implementation = function(){<br>        console.log(&quot;original function returns&quot;, this.get_random());<br>        return 1;<br>    }<br>})</pre><p>And boom — you’ve just bypassed the app’s intended logic.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/930/1*7udWI9a7xArqCor4uPCIkA.png" /><figcaption>Bypassed !</figcaption></figure><h3>🏁 Conclusion</h3><p>This challenge demonstrates the <strong>real-world impact</strong> of runtime hooking. By modifying runtime behavior, attackers can manipulate application logic, bypass validation, or gain unauthorized access — all <strong>without touching a single line of source code</strong>.</p><p>If you enjoyed this write-up, feel free to clap, comment, or share your thoughts. Stay tuned for <strong>Part 2</strong>, where we’ll tackle more advanced mobile app exploitation scenarios.</p><p>Thanks for reading!<br> — <em>Chetan Kashyap</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=17a7f57ea87b" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Introspection Query leaks Graphql schema]]></title>
            <link>https://medium.com/@ch3tanbug/introspection-query-leaks-graphql-schema-e3a07806973b?source=rss-132fa5fb717f------2</link>
            <guid isPermaLink="false">https://medium.com/p/e3a07806973b</guid>
            <category><![CDATA[bug-bounty-tips]]></category>
            <category><![CDATA[bug-bounty]]></category>
            <category><![CDATA[cybersecurity]]></category>
            <category><![CDATA[bugcrowd]]></category>
            <category><![CDATA[graphql]]></category>
            <dc:creator><![CDATA[CH3TAN]]></dc:creator>
            <pubDate>Sat, 24 Jun 2023 07:27:04 GMT</pubDate>
            <atom:updated>2023-06-24T07:27:04.454Z</atom:updated>
            <content:encoded><![CDATA[<h3>Introduction</h3><p>Hey i’m back again with a new bug that i found recently. Those who don’t know me i’m <em>Chetan Kashyap</em> a Bug-Bounty hunter from INDIA. So without wasting any time let’s start.</p><p>So lately i decided to hunt on <a href="https://www.bugcrowd.com/">bugcrowd </a>but i wasn’t getting any program that had good scope and good functionality. So i decided to leave <a href="https://www.bugcrowd.com/">bugcrowd</a> and find some VDP’s through google dorking. So after entering my first dork i checked out some of the websites and finally i got a website ( <em>let’s call it redacted.com </em>) that was looking good to hunt on, however the website was in dutch language I had to use google translate extension the whole time while hunting.</p><p>So when i was reading the responsible disclosure rules i came to know that all the findings on the website had to be submitted through <a href="https://www.bugcrowd.com/">bugcrowd </a>to a third party vendor who later will submit and mitigate those vulnerabilities on the target. I became happy because initially too i want to hunt on programs on <a href="https://www.bugcrowd.com/">bugcrowd </a>because VDP’s take a long time to respond.</p><p>So i started with the recon process and ran my custom recon script that i made which usually finds subdomains by combining all tools that are available and filters the live domains and their titles and saves the output to a new file. While the script was running i went ahead to the main website and tried checking all the functionality while my burp was saving the request history. After spending almost half an hour i didn’t found anything interesting. So i decided to look for login panels. I went to google and used the dork <strong>“site:*.redacted.com inurl:login” . </strong>I found a subdomain <em>“works.redacted.com” </em>that allowed to raise support tickets and check status of the support tickets. When i tried to raise any ticket it said me to login or register but even after registering it showed account didn’t exist. I spent a lot of time on this subdomain even grepped all the urls from waybackurls but found nothing interesting. My whole day was spent trying to figure a way to get the support tickets of the other users but unluckily i didn’t get any success.</p><p>Next day i woke up with a fresh mind and checked all the domains my script has collected. I found an interesting domain “wiki.redacted.com” that contain the information regarding how to use a particular software that the target was selling. I tried to fuzz the subdomain and found an endpoint /admin. When i checked that endpoint it was a admin login page, as usual the default creds didn’t work so I entered wrong creds and intercepted the request in BURP. To my surprise the website was sending a POST request to /graphql endpoint.</p><p>I remembered the article i read from <a href="https://blog.yeswehack.com/yeswerhackers/how-exploit-graphql-endpoint-bug-bounty/">YesWeHack </a>regarding Graphql exploitation. I copied the introspection query from that article pasted it in my repeater and BOOM the request leaked the Graphql schema. Now there are numerous attacks that can be performed from this stage. An introspection can completely reveal the backend system defined by developers including arguments,fields,types,description and so on. The schema serves as an attack ground for attackers for crafting queries and leaking sensitive information but in my case mutations were also possible.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*uzW-GntMXOxoIT0h4H7L0A.png" /><figcaption>Request and response of introspection query</figcaption></figure><p>I quickly prepared a poc and submitted the report to <a href="https://www.bugcrowd.com/">bugcrowd </a>but it turns out they aren’t accepting any domains besides the main domain that is “redacted.com” the traiger suggested to report the vulnerability directly to the VDP through email as they can only accept reports on their behalf which are on the main domain. So i sent an email with all the details and the reply is yet to come.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fgfycat.com%2Fifr%2Funselfishlatebluebottlejellyfish&amp;display_name=Gfycat&amp;url=https%3A%2F%2Fgfycat.com%2Funselfishlatebluebottlejellyfish&amp;image=https%3A%2F%2Fthumbs.gfycat.com%2FUnselfishLateBluebottlejellyfish-size_restricted.gif&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=gfycat" width="1000" height="660" frameborder="0" scrolling="no"><a href="https://medium.com/media/75dd70ddd60475e9e44c7ed63f73bb04/href">https://medium.com/media/75dd70ddd60475e9e44c7ed63f73bb04/href</a></iframe><h3>Conclusion</h3><p>So i was a little upset because the bug was not traiged but this bug helped me to know more about graphql and now im trying to increase the impact of the bug with the help of circular queries in graphql (still learning) which can lead to an internal DOS. Nevertheless bug-hunting is all about patience and learning and i hope you liked my article. You can ask me any questions if you want and if i wasn’t able to explain anything correctly kindly forgive me because im not used to writing articles. Thank you for reading and don&#39;t forget to give a clap.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fgfycat.com%2Fifr%2Flastingdemandingamericancicada&amp;display_name=Gfycat&amp;url=https%3A%2F%2Fgfycat.com%2Flastingdemandingamericancicada-viggo-mortensen&amp;image=https%3A%2F%2Fthumbs.gfycat.com%2FLastingDemandingAmericancicada-size_restricted.gif&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=gfycat" width="1920" height="1080" frameborder="0" scrolling="no"><a href="https://medium.com/media/6da173f7f2345318d8de62a355f1d713/href">https://medium.com/media/6da173f7f2345318d8de62a355f1d713/href</a></iframe><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e3a07806973b" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How I was able to change password of any corporate user]]></title>
            <link>https://medium.com/@ch3tanbug/how-i-was-able-to-change-password-of-any-corporate-user-c68b9509840?source=rss-132fa5fb717f------2</link>
            <guid isPermaLink="false">https://medium.com/p/c68b9509840</guid>
            <category><![CDATA[cybersecurity]]></category>
            <category><![CDATA[bug-bounty-tips]]></category>
            <category><![CDATA[bug-bounty-writeup]]></category>
            <category><![CDATA[bug-bounty]]></category>
            <category><![CDATA[hackerone]]></category>
            <dc:creator><![CDATA[CH3TAN]]></dc:creator>
            <pubDate>Sun, 09 Apr 2023 07:07:03 GMT</pubDate>
            <atom:updated>2023-04-09T07:13:07.566Z</atom:updated>
            <content:encoded><![CDATA[<h3>Introduction</h3><p>Hey guys before we start i want to give you all a little introduction about myself. My name is Chetan kashyap and I am a bug-bounty hunter from India. This is my first time writing an article about my findings. But we all have to start at some point of time, so i guess i will start writing articles more often on my findings.</p><h3>The Story</h3><blockquote>So this week as i was having 2–3 holidays from my college i decided to drop my assignments and try to hunt on a program from a good platform. I chose a program from <a href="http://yeswehack.com/">Yeswehack</a>. The program had a fairly large scope with 5–6 web applications in scope. I created a text file and stored all the in-scope target urls and fed it to my custom recon script which i call as subdig. I got a lot of live subdomains but half of them were login panels of the same type and after like investing 1–2hour on them i was unable to bypass them or get any type of juicy files/directories on those urls.</blockquote><blockquote>So then I decided to jump on the main application itself. I chose the first in-scope web-application of the program to begin my testing, let’s call it as usual redacted.com. The target was basically just like an e-commerce website where you could purchase things or gift things to someone. I tried all basic vulnerabilities like OTP bypass, No-rate limit on OTP , CSRF etc. After I was all exhausted i decided to move to the next in-scope web-application but then one thing on the target caught my eye. There was a small button that said corporate user login. I clicked that button and it redirected me to <a href="https://corporate.redacted.com/corporate/login.">https://corporate.redacted.com/corporate/login.</a> There I was greeted with an option to enter username and password. As i was not having any username i went back to my recon. This time i went to <a href="http://github.com/">Github</a> and used a simple dork “redacted.com” username and after looking at some code i was able to get an username. I did this because default it was not accepting any usernames like admin, test etc. Later after finding username on <a href="http://github.com/">Github</a> I found that username must be in form of user@xyz.com</blockquote><blockquote>I went on the target again and entered that username and entered any random password like userpassword. I intercepted that request in burp it was something like this.</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*EIeE09jhqN6n6DYCi4_45A.png" /></figure><blockquote>I changed the &amp;isPasswordToBeChanged=false parameter to &amp;isPasswordToBeChanged=true and BOOM! I was greeted with a page to enter my new password and confirm it.</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/576/1*CLCayYOpTTezDhlm9zxb5w.png" /></figure><blockquote>I entered a new password but after hitting confirm it was showing an error that said some error occurred please contact the administrator. So i again entered the password and this time intercepted the response to this request in Burpsuite and changed the response key in the response from 3 to 1. And guess what the page said password changed. Now i was able to perform an ATO of any corporate user i just needed their username.</blockquote><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fgfycat.com%2Fifr%2Funacceptablekeenchameleon&amp;display_name=Gfycat&amp;url=https%3A%2F%2Fgfycat.com%2Funacceptablekeenchameleon&amp;image=https%3A%2F%2Fthumbs.gfycat.com%2FUnacceptableKeenChameleon-size_restricted.gif&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=gfycat" width="920" height="624" frameborder="0" scrolling="no"><a href="https://medium.com/media/ad12a374d2dfd2d12467321d2e1ded56/href">https://medium.com/media/ad12a374d2dfd2d12467321d2e1ded56/href</a></iframe><figure><img alt="" src="https://cdn-images-1.medium.com/max/575/1*pmeJq0HXe5Gv45sUvCij8g.png" /></figure><h3>Conclusion</h3><p>At the end i would say that sometimes rather than gathering more and more assets to test on try to focus on a single asset and invest your time on that, you may find something fruity. Also take breaks and keep hustling. Do consider giving a clap if you like my write up it will motivate me to write more. See you next time until then BYE!</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fgfycat.com%2Fifr%2Funawarejadedeft&amp;display_name=Gfycat&amp;url=https%3A%2F%2Fgfycat.com%2Funawarejadedeft-damon-wayans-major-payne-goodbye-silly-bye&amp;image=https%3A%2F%2Fthumbs.gfycat.com%2FUnawareJadedEft-size_restricted.gif&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=gfycat" width="720" height="384" frameborder="0" scrolling="no"><a href="https://medium.com/media/17549bba91ea2c16c19807c52900141b/href">https://medium.com/media/17549bba91ea2c16c19807c52900141b/href</a></iframe><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c68b9509840" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>