<?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 Akshay Jain on Medium]]></title>
        <description><![CDATA[Stories by Akshay Jain on Medium]]></description>
        <link>https://medium.com/@akshayjain12?source=rss-3433995c493e------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*mA2jHiWYgEUWtTF1.jpg</url>
            <title>Stories by Akshay Jain on Medium</title>
            <link>https://medium.com/@akshayjain12?source=rss-3433995c493e------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sat, 21 Nov 2026 04:37:38 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@akshayjain12/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[Frida-trace usage]]></title>
            <link>https://akshayjain12.medium.com/frida-trace-usage-70aecead37ce?source=rss-3433995c493e------2</link>
            <guid isPermaLink="false">https://medium.com/p/70aecead37ce</guid>
            <category><![CDATA[ios]]></category>
            <category><![CDATA[frida]]></category>
            <category><![CDATA[mobile-security]]></category>
            <category><![CDATA[reverse-engineering]]></category>
            <dc:creator><![CDATA[Akshay Jain]]></dc:creator>
            <pubDate>Mon, 03 Aug 2020 11:12:21 GMT</pubDate>
            <atom:updated>2020-08-03T11:12:21.479Z</atom:updated>
            <content:encoded><![CDATA[<p>I think working as a Mobile Appsec consultant over the years I have seen something which other researchers don’t use is Frida-trace. It is most useful if you want to trace function calls in any binary.</p><p>If you have a Blackbox application and you want to quickly know how it uses crypto library then here are the options you have</p><ul><li>Open the binary in the hopper or any other disassembler and figure out the logic</li><li>Once you understand the logic now attach a debugger to it and create breakpoints and Hope that it works.</li></ul><p>OR</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fgiphy.com%2Fembed%2FkspkW9pMYyqZAtQaaB%2Ftwitter%2Fiframe&amp;display_name=Giphy&amp;url=https%3A%2F%2Fgiphy.com%2Fgifs%2Fultramusic-ultra-music-trace-kspkW9pMYyqZAtQaaB&amp;image=https%3A%2F%2Fmedia0.giphy.com%2Fmedia%2FkspkW9pMYyqZAtQaaB%2Fgiphy.gif&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=giphy" width="435" height="326" frameborder="0" scrolling="no"><a href="https://medium.com/media/18536ce592b6e7213a23883bd4805643/href">https://medium.com/media/18536ce592b6e7213a23883bd4805643/href</a></iframe><p>You can just use</p><pre>frida-trace -U -F com.blackbox -I &quot;libcommonCrypto*&quot;</pre><p>Let&#39;s dissect the code snippet and understand what it is using</p><ul><li>Frida-trace</li></ul><p>It is something which comes up with Frida and it can be installed via pip install Frida-tools</p><ul><li>-U</li></ul><p>It is used to connect to a USB device which in this case is our phone</p><ul><li>-F com.blackbox</li></ul><p>It is used for spawning out our application whose package name is com.blackbox</p><ul><li>-I “libCommonCrypto*”</li></ul><p>Here -I is used for module name and libCommonCrypto is something which we are tracing. More details on common crypto are here</p><p><a href="https://opensource.apple.com/source/CommonCrypto/">Source Browser</a></p><p>Once you execute the command. You will see that it will create a JS handler within which introspection and hooking related code logic can be written.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FeJM3FSFTkaI%3Ffeature%3Doembed&amp;display_name=YouTube&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DeJM3FSFTkaI&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FeJM3FSFTkaI%2Fhqdefault.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/a4bcfd2b908af2c7f9bf07d29aabe711/href">https://medium.com/media/a4bcfd2b908af2c7f9bf07d29aabe711/href</a></iframe><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=70aecead37ce" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Hacking an Indian Bank]]></title>
            <link>https://akshayjain12.medium.com/hacking-an-indian-bank-b6121bc4e613?source=rss-3433995c493e------2</link>
            <guid isPermaLink="false">https://medium.com/p/b6121bc4e613</guid>
            <category><![CDATA[jenkins]]></category>
            <category><![CDATA[bug-bounty]]></category>
            <category><![CDATA[infosec]]></category>
            <category><![CDATA[cybersecurity]]></category>
            <dc:creator><![CDATA[Akshay Jain]]></dc:creator>
            <pubDate>Sat, 28 Jul 2018 17:32:48 GMT</pubDate>
            <atom:updated>2018-07-28T17:32:48.650Z</atom:updated>
            <content:encoded><![CDATA[<p>So few weeks while I was surfing <a href="https://www.shodan.io/">shodan</a> <a href="https://twitter.com/hashtag/shodansafari?lang=en">#shodansafari</a>, I found an unauthenticated Jenkins CI server on a major Indian bank.</p><p>So some fun facts related to Jenkins that what benefits does it provide to an attacker</p><ul><li>Runs with SYSTEM or high privilege user on Windows and on Unix machines, it runs as user Jenkins.</li><li>No protection against brute force attacks</li></ul><p>The bank left a Jenkins console in an insecure state. Jenkins has a scripting console available which can be used to run an arbitrary Groovy code. It is typically found under Manage Jenkins -&gt; Script Console or just by going to /script from the root of the Jenkins install path.</p><p>Since it was a bank it didn’t go ahead and started exploiting it but one can use <a href="https://www.rapid7.com/db/modules/exploit/multi/http/jenkins_script_console">https://www.rapid7.com/db/modules/exploit/multi/http/jenkins_script_console</a> to get a full-fledged meterpreter shell. The attacker can also deploy his own build with his backdoor into the code. An attacker can also retrieve ssh keys and passwords.</p><p>Disclosure timeline:</p><ul><li>6 July 2018 -Reported to bank and NCIIPC</li><li>7 July 2018 -Received email from the security team and reported the misconfiguration.</li><li>10 July 2018 -Received “Thank you” from the bank security team</li></ul><p>Since its a bank I am not allowed to post screenshots of jenkins instance or any more details.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*gcHXI4cxbOOamDUu4YGtaw.png" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b6121bc4e613" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Google TEZ account takeover]]></title>
            <link>https://akshayjain12.medium.com/google-tez-account-takeover-5b7eaf230a9a?source=rss-3433995c493e------2</link>
            <guid isPermaLink="false">https://medium.com/p/5b7eaf230a9a</guid>
            <category><![CDATA[bugs]]></category>
            <category><![CDATA[bug-bounty]]></category>
            <category><![CDATA[ios]]></category>
            <dc:creator><![CDATA[Akshay Jain]]></dc:creator>
            <pubDate>Sun, 05 Nov 2017 16:50:53 GMT</pubDate>
            <atom:updated>2021-02-06T10:38:36.802Z</atom:updated>
            <content:encoded><![CDATA[<p>I don’t do bug bounties as much as I used to do, but still here is one of my findings which I recently reported to google.</p><h3>Product name: GOOGLE TEZ</h3><p>The vulnerability lies in the ios version of the app which doesn’t implement rate limitation during the login procedure.</p><p>Steps to reproduce:<br> 1. Open Google Tez app link: <a href="https://www.google.com/url?q=https://itunes.apple.com/in/app/tez-a-payments-app-by-google/id1193357041?mt%3D8&amp;sa=D&amp;usg=AFQjCNHT01NZvXTwNZetAOCBh9EtAdkzxA">https://itunes.apple.com/in/app/tez-a-payments-app-by-google/id1193357041?mt=8</a></p><p>2. Enter the phone number<br> 3. It will send the OTP to the number<br> 4. Keep on entering the wrong OTP. The OTP won’t expire.You can use burp intruder or anything other tools.</p><p>Browser/OS: IOS 11</p><p>For the POC purposes, I wrote a small Frida script to automate it.</p><p>Unfortunately, it was marked duplicate.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*EIFGG9yul7zm2rLTAZoZqw.jpeg" /></figure><p><strong>Timeline of Events</strong></p><p><strong>OCT 20 2017</strong> — Report Submitted to Google Security Team</p><p><strong>OCT 21 2017</strong> — Google acknowledged and confirmed the issue and sent it to the appropriate product team for investigation</p><p><strong>OCT 23rd 2017</strong> — Google confirmed that the issue is duplicate</p><p><strong>OCT 25th 2017</strong> — Google fixed the bug and rolled out the patch.</p><p>PS: Stay tuned. I have reported some interesting bugs in CYLANCE and some next-gen products.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5b7eaf230a9a" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>