<?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 Abhishek Bundela on Medium]]></title>
        <description><![CDATA[Stories by Abhishek Bundela on Medium]]></description>
        <link>https://medium.com/@abhibundela?source=rss-cae42cd27823------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*t6mt0EC3zu8xprhK.</url>
            <title>Stories by Abhishek Bundela on Medium</title>
            <link>https://medium.com/@abhibundela?source=rss-cae42cd27823------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Mon, 16 Nov 2026 18:26:27 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@abhibundela/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[Exploiting an unknown vulnerability]]></title>
            <link>https://infosecwriteups.com/exploiting-an-unknown-vulnerability-a752272ffd7f?source=rss-cae42cd27823------2</link>
            <guid isPermaLink="false">https://medium.com/p/a752272ffd7f</guid>
            <category><![CDATA[security]]></category>
            <category><![CDATA[development]]></category>
            <category><![CDATA[application-security]]></category>
            <category><![CDATA[bug-bounty]]></category>
            <category><![CDATA[infosec]]></category>
            <dc:creator><![CDATA[Abhishek Bundela]]></dc:creator>
            <pubDate>Wed, 03 Oct 2018 15:55:27 GMT</pubDate>
            <atom:updated>2018-10-03T15:55:27.646Z</atom:updated>
            <content:encoded><![CDATA[<p>I found this vulnerability around 2 months ago in a consulting application. Their security team told me this application is already pentested and they will reward bonus if I could find a vulnerability. For new targets, first I analyze application and make a data flow diagram of its functionality then I start hunting for vulnerabilities. I extensively test for logical vulnerabilities because I know from my experience that there will be some critical transitions which might have been missed by application developers or testers.</p><p>I have named it as “unknown” vulnerability because I want to make it as an exercise as well as write up that’s why I haven’t written details in the title.</p><p>There are two types of user roles: consultant and client in target application. The application’s core functionality is to provide consulting services to various clients.</p><ul><li>Consultant set fee in coins for their service.</li></ul><pre><strong>#</strong> <strong>consultant request</strong></pre><pre>POST /set/fee/</pre><pre>{&quot;value&quot;: 5, &quot;timing&quot;:2}</pre><ul><li>Clients visits consultant’s timeline, select an appropriate time slot and book that timing, coins get deducted from client’s account according to fee shown in timeline respective to time slot.</li></ul><pre><strong>#</strong> <strong>client request</strong></pre><pre>POST /consultant_username/book</pre><pre>{&quot;timing&quot;:2}</pre><p>Before reading further, I will suggest you guys to write your test case or your approach to exploit the above functionality. Good luck 👍</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*KYxxMeg9CDzX_NLhCap3Sw.jpeg" /></figure><p>I came up with following test cases 🤔.</p><ol><li>Injection vulnerability like Sqli, Command injection</li><li>Modify content type and request data to xml for testing XML injection</li><li>Booking consultant’s higher value time slots in less coin</li><li>Injecting “<strong>value</strong>” parameter from <strong>consultant request</strong> and using it in <strong>client request</strong></li><li>Parameter pollution by injection two <strong>timing </strong>values in <strong>client</strong> <strong>request</strong></li><li>Array based injection using <strong>timing</strong> value in <strong>client</strong> <strong>request </strong>i.e {“timing[0]”:2}</li><li>HTTP method tampering by changing POST to PUT</li><li>Booking for two or more time slots of same consultant by playing multi-threaded <strong>client</strong> <strong>request</strong> (Race condition)</li><li>Booking two different consultant’s time slots by playing multi-threaded <strong>client</strong> <strong>request</strong> (Race condition)</li></ol><p>I am sure, you might have come up with different test cases so please comment below your test cases.</p><p>Unfortunately, none of the above test cases worked for me 😥. May be their security team mitigated these vulnerabilities or experienced developers built the application.</p><p>Next day, I took a look again and this time my attention goes to more in booking request since there is no coin passed in the request and coins get automatically deducted from client’s account after submitting the <strong>client request</strong>.</p><pre>POST /consultant_username/book</pre><pre>{&quot;timing&quot;:2}</pre><p><strong>What will happen if consultant change fee to some higher amount just before client book the time slot</strong>. I was excited 🤩 thought this should work but again it didn’t work out for me. Since it showed the message “Consultant’s fee for this slot is 10”.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/356/1*W7JE1YcyRLtdXm5G9zfpQg.png" /></figure><p>I was going to give up but the idea of <strong>race condition</strong> came into my mind, for testing it out I sent multi-threaded request to web server with four different consulting fee (5, 15, 15, 5) in four different requests at a time and put those requests in a loop for half an hour. When a client visits consultant timeline during this time period there are 50% chances that client will end up paying higher fee. This way, I was successfully able to exploit 😄 this vulnerability by changing consulting price quickly. Application also has an offer features in which consultants can set discount for a certain period of time.</p><h3><strong>Attack flow</strong></h3><ol><li>Consultant set fee 5 coins for any time slot ‘x’.</li><li>Consultant set offer period i.e 30–60 minutes during a day.</li><li>Clients visit consultant timeline during offer period.</li><li>Consultant quickly change consulting price by playing multi-threaded <strong>consultant request </strong>in loop and send it to server.</li><li>Clients pay the fee by sending booking request to the server.</li><li>Extra coins get deducted from the clients account.</li></ol><h3><strong>Impact</strong></h3><p>Consultants can trick clients in paying higher amount then shown in their timeline for their services.</p><h3><strong>Takeaway</strong></h3><p>As a defender, make a checklist of vulnerabilities and test it for every feature implemented in the application. Rate limiting and race condition based locking system should be implemented for preventing these kind of vulnerabilities.</p><p>As application’s functionalities grow, its complexity grows exponentially and more chances to miss some test cases during design, development or security testing phases of the application. Analyze application functionality by going through request history again and again, understand data flow in application etc. Spend your energy &amp; time in building smarter test cases that can break application’s use case.</p><p>Thank you very much!</p><p>Learn, Build &amp; Break!</p><blockquote>Originally Published at: <a href="https://abhibundela.com/2018/09/25/exploiting-an-unknown-vulnerability/">https://abhibundela.com/2018/09/25/exploiting-an-unknown-vulnerability/</a></blockquote><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a752272ffd7f" width="1" height="1" alt=""><hr><p><a href="https://infosecwriteups.com/exploiting-an-unknown-vulnerability-a752272ffd7f">Exploiting an unknown vulnerability</a> was originally published in <a href="https://infosecwriteups.com/">InfoSec Write-ups</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How I broke into Google Issue Tracker]]></title>
            <link>https://infosecwriteups.com/how-i-broke-into-google-issue-tracker-667b9e33e931?source=rss-cae42cd27823------2</link>
            <guid isPermaLink="false">https://medium.com/p/667b9e33e931</guid>
            <category><![CDATA[cybersecurity]]></category>
            <category><![CDATA[google]]></category>
            <category><![CDATA[security]]></category>
            <category><![CDATA[bug-bounty]]></category>
            <category><![CDATA[infosec]]></category>
            <dc:creator><![CDATA[Abhishek Bundela]]></dc:creator>
            <pubDate>Tue, 10 Apr 2018 12:25:11 GMT</pubDate>
            <atom:updated>2018-04-10T12:25:11.351Z</atom:updated>
            <content:encoded><![CDATA[<p>Hi friends,</p><p>Recently, I published an <a href="https://medium.com/@abhishekbundela/hey-organisations-dont-underestimate-dmarc-policy-23f525df7b99">article</a> where I explained a flaw in google groups functionality. When I submitted that vulnerability to Google I noticed that researchers can comment on the issue in issue tracker by replying to the email from buganizer system.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/880/1*lt6gIPU0ewavgVIIqrrEDg.png" /></figure><p>After submitting three N/A (won’t fix) report to Google, finally I managed to submit one valid report but unfortunately that was marked as duplicate. Thanks to Google security team, they are very responsive and allowed me to write about the vulnerability.</p><p>For learning about Google Issue Tracker’s functionalities, I went through issue tracker’s documentation.</p><blockquote>Issue Tracker is a tool used internally at Google to track bugs and feature requests during product development. It is available outside of Google for use by external public and partner users who need to collaborate with Google teams on specific projects.</blockquote><p>Users can also create issues by sending an email to buganizer system. You can learn more about it <a href="https://developers.google.com/issue-tracker/guides/create-issue-email">here</a>.</p><p>Users are required to send an email to buganizer-system+<em>componentID</em>@google.com for creating an issue.</p><p>componentID:It is an integer value of component where you want to report the issue.</p><p>If they want to comment on an issue then they have to send an email to buganizer-system+<em>componentID+threadID</em>@google.com.</p><p><em>threadID:</em>It is also an integer value for a particular issue.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/854/1*0jLdWlb-52NC2kZkLUyRlw.png" /></figure><p>You can clearly view in the above image, if you want to create an issue using email then your domain should support SPF &amp; DKIM. I had talked about SPF &amp; DKIM in my previous post. Now, a simple question arises “How does Issue Tracker handle unverified emails ( emails that failed SPF &amp; DKIM verification )”. What if the content from unverified emails directly got posted in Issue tracker ? This means that if an attacker knows the victim’s email address, he can create/comment on an issue on behalf of the victim. So for testing this functionality, I sent an email via smtp2go service and I was astonished by the result. Yes, I can create an issues on behalf of any user in the <strong>public issue tracker !</strong> I can also comment on issues just by sending an email to buganizer-system+<em>componentID+threadID</em>@google.com.</p><p>I was successful in creating/commenting on issues in <strong>public issue tracker</strong>,<strong> </strong>so I thought it might be possible that I can also comment on any issue in the <strong>private issue tracker. </strong>I sent an email (random email) to one of my issues (via smtp2gto) but the attempt was unsuccessful in creating a comment on that issue. Then, I tried to comment on the issue (via smtp2gto) using my email address ( the same email that is used while reporting the vulnerability ) and I got success.</p><h3><strong>Impact</strong></h3><p>An attacker can create/comment on issues using anyone’s email address in <strong>public issue tracker</strong>. Creating/Commenting issue does not disclose reporter’s email since email’s only first two characters and domain name are visible. You can check this in the attached image.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/844/1*L_nYuYZKrwYFBD3KpBDEIg.png" /></figure><p>Attacker can see those characters &amp; domain name in <strong>public issue tracker</strong> and can comment on that particular issue using any email that starts with those characters and ends in that particular domain. Attacker can also comment on an issue using random email like abc@googledev.com to fool the public researchers and ask for more details.</p><p>While for commenting on <strong>private issue tracker</strong>,<strong> </strong>attacker has to know the componentID, threadID and email address located to that ID. Google’s security team consider this as p2 (priority) s2(severity) level.</p><p><strong>POC</strong></p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2Fsu149elVbaQ%3Ffeature%3Doembed&amp;url=http%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3Dsu149elVbaQ&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2Fsu149elVbaQ%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/c53cc93c3a199788301b93ca157ae71b/href">https://medium.com/media/c53cc93c3a199788301b93ca157ae71b/href</a></iframe><p>Thanks for your patience.</p><p>Learn, Build &amp; Break!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=667b9e33e931" width="1" height="1" alt=""><hr><p><a href="https://infosecwriteups.com/how-i-broke-into-google-issue-tracker-667b9e33e931">How I broke into Google Issue Tracker</a> was originally published in <a href="https://infosecwriteups.com/">InfoSec Write-ups</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Hey! Organisations don’t underestimate DMARC policy!]]></title>
            <link>https://medium.com/@abhibundela/hey-organisations-dont-underestimate-dmarc-policy-23f525df7b99?source=rss-cae42cd27823------2</link>
            <guid isPermaLink="false">https://medium.com/p/23f525df7b99</guid>
            <category><![CDATA[bug-bounty]]></category>
            <category><![CDATA[security]]></category>
            <category><![CDATA[email]]></category>
            <category><![CDATA[hacking]]></category>
            <category><![CDATA[vulnerability]]></category>
            <dc:creator><![CDATA[Abhishek Bundela]]></dc:creator>
            <pubDate>Tue, 03 Apr 2018 08:31:59 GMT</pubDate>
            <atom:updated>2018-05-21T13:59:48.129Z</atom:updated>
            <content:encoded><![CDATA[<h3>Hey! Organisations don’t underestimate DMARC policy! Attackers might be sending emails or using services as your team members</h3><p>Hi friends,</p><p>It has been a long time since I have written, of course I am lazy. I was desperate to find bugs in Google &amp; Facebook ( at least one valid ) so I thought let’s start with Google services. We all know about <strong>Google Groups</strong>, it is a service that provides <a href="https://en.wikipedia.org/wiki/Internet_forum">discussion groups</a> for people sharing common interests. Google Groups have a nice feature to post on groups by sending emails. At that time, I was logged in Google group by college email. Instantly, an idea popped up in my mind, “how does Google Group handles the emails from the domain that don’t have DMARC record setup ”.</p><p>DMARC ( Domain Message Authentication Reporting &amp; Conformance ). It is a txt records on a DNS server. It’s task is to decide whether to accept or reject emails that fails SPF/DKIM. The unverified messages are handled according to DMARC policy.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/580/1*wOy97psZ2P6l-xKDWX238A.png" /></figure><p>The sending domain should have an SPF and DKIM record before publishing DMARC record. SPF &amp; DKIM are also txt records on a DNS server. SPF entry have list of servers that should be considered to send an email for specific domain while DKIM record is used for verifying message’s content. This is implemented by public and private key signing process. Cathy Patalas have written a nice blog about SPF &amp; DKIM, if you want to get into details check it out <a href="https://blog.woodpecker.co/cold-email/spf-dkim/">https://blog.woodpecker.co/cold-email/spf-dkim/</a>.</p><p>I was looking for the domain that don’t have DMARC record published. I chose my college domain and looked for the records using mxtoolbox <a href="https://mxtoolbox.com/dmarc.aspx">https://mxtoolbox.com/dmarc.aspx</a>. Fortunately/Unfortunately, there were no DMARC record found in my university’s DNS. I quickly used the service of smtp2go and sent an email to myself using my friend’s email address and I got message in my inbox.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/802/1*TcvJz3wg8C3vT__26mSq6A.png" /></figure><p>Finally, I had domain that don’t have DMARC record. For testing group functionality, I sent an email to my class Google Group using the service smtp2go. I found that Google Group allows the email from the domains that don’t have DMARC record that means an attacker can post as member using smtp service, if the email is known to the attacker.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/603/1*wXTQe_d_B1DqUqKpuOwlSg.png" /></figure><p>Since this is an authentication bypass vulnerability, so I reported this to Google via their bug bounty program but they said it is an intended functionality. Now the question arises, Who is responsible for the security Organisations or Google ? I suggested a solution to Google security team.</p><blockquote>If the email arrive from the domain that don’t have DMARC policy published then send an approval email to the sender’s email. Once authorized sender approve the post only then it should be posted on the group.</blockquote><p>Reply from the security team</p><blockquote>That solution would be too much hassle for most groups without any real security benefit.</blockquote><p>I also contacted to our college V.C. sir and told him about the vulnerability. He pointed me to the respective authority in order to fix this vulnerability. So with the help of some faculty members &amp; friends <a href="https://www.facebook.com/profile.php?id=100006911595966">Ronij</a>, <a href="https://www.facebook.com/rajat.tcp">Rajat</a> I managed to add the DMARC policy to DNS server. For confirming the fix, I sent an email using the same service smtp2go. As you can see in the below image, email delivery got failed.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/702/1*K_0I_NLamnA8lbYSpYTMZQ.png" /></figure><h3>POC</h3><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FIFzQNKh_AFI%3Ffeature%3Doembed&amp;url=http%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DIFzQNKh_AFI&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FIFzQNKh_AFI%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/531ef61d68142db3b0b722609788e334/href">https://medium.com/media/531ef61d68142db3b0b722609788e334/href</a></iframe><h3><strong>Takeaway</strong></h3><p>While implementing features, always go through possible security checks for various functionalities in combination with other services to ensure that the functionality is working as intended. Everybody should be responsible for security.</p><p>Thanks you for your patience!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=23f525df7b99" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Little experience in bugbounty hunting]]></title>
            <link>https://medium.com/@abhibundela/little-experience-in-bugbounty-hunting-1a9cca7055d2?source=rss-cae42cd27823------2</link>
            <guid isPermaLink="false">https://medium.com/p/1a9cca7055d2</guid>
            <category><![CDATA[infosec]]></category>
            <category><![CDATA[bug-bounty]]></category>
            <category><![CDATA[hacking]]></category>
            <category><![CDATA[security]]></category>
            <dc:creator><![CDATA[Abhishek Bundela]]></dc:creator>
            <pubDate>Mon, 19 Jun 2017 05:50:29 GMT</pubDate>
            <atom:updated>2018-09-23T18:37:49.929Z</atom:updated>
            <content:encoded><![CDATA[<p>Hello friends, hope you are doing well. Yesterday, I had gone for LinuxChix india meetup. I found some people interested in magic the bugbounty hunters do in finding the security loopholes. So I am sharing some resources as well as my experience. Oh, let me introduce myself, My name is Abhishek Bundela, undergraduate from Shri Mata Vaishno Devi University. I do bugbounty for the feeling of excitement and of course, for the cash. Currently, I am learning android app testing. You can find me on <a href="https://twitter.com/abhibundela">twitter</a>. My hackerone handle is <a href="http://hackerone.com/encrypt">encrypt</a>.</p><p>My senior <a href="http://twitter.com/exploitprotocol">Aditya Agarwal</a> introduced me to bugbounty. Thanks sir jee. I spent 6 months testing vulnerable web apps and reading web application hacker’s handbook, owasp testing guide. After that I thought it is right time to start testing some real world applications. Weeks spent without finding single bug since I was targeting big boy (Facebook). After defeat from facebook, I selected a new program on bugcrowd. I submitted my first bug on bugcrowd to smartsheet. Yup, it was duplicate but I was happy since I got my first Hall Of Fame from smartsheet. I submitted some more bugs to others program but all were duplicate. At that point, I felt something is going wrong. I took a break from bugbounty and decided that I will submit bugs to old programs since I was submitting bugs to new programs and I was not as fast as other successful bug hunters. After some time, I started to look for some programs on hackerone. I submitted a bug to a private program on hackerone and it got accepted and they paid me $125 bounty !!! the feeling was amazing. I started digging more and more and got cool bounties. Sometime I got duplicates, I am lying if I say that dupes don’t affect me. Ya, dupes are pain but that’s how bugbounty works, sometime time defeats us. Time teaches us lesson to use our time efficiently (be accurate &amp; fast). Try to do automation as much as possible. So you don’t find yourself doing repetitive tasks.</p><p>Time to share some resources.<br>There are lot of resources about <a href="http://lmgtfy.com/?q=Bugbounty">bug bounty hunting</a> on web. I will suggest to follow cool infosecs on twitter. You will learn a lot by these smart people. These people share their bug hunting tactics, their achievements (bounties, swag, hof) and cool jokes. Something, I believe worth sharing.</p><p>How to Build a Successful Information Security Career ? <a href="https://danielmiessler.com/blog/build-successful-infosec-career/#gs.wARu9Ks">https://danielmiessler.com/blog/build-successful-infosec-career/#gs.wARu9Ks</a></p><p>How to become bugbounty hunter ?<a href="https://forum.bugcrowd.com/t/researcher-resources-how-to-become-a-bug-bounty-hunter/1102">https://forum.bugcrowd.com/t/researcher-resources-how-to-become-a-bug-bounty-hunter/1102</a><br><a href="https://www.quora.com/How-does-one-become-a-bug-bounty-hunter">https://www.quora.com/How-does-one-become-a-bug-bounty-hunter</a><br><a href="https://www.hackerone.com/blog/become-a-successful-bug-bounty-hunter">https://www.hackerone.com/blog/become-a-successful-bug-bounty-hunter</a></p><p>Best Bugbounty hunter’s AMA : <a href="https://bugbountyforum.com/blogs/">https://bugbountyforum.com/blogs/</a></p><p>What are the ways in which a bug can be discovered in bug bounty program ?<br><a href="https://www.quora.com/What-are-the-ways-in-which-a-bug-can-be-discovered-in-bug-bounty-program">https://www.quora.com/What-are-the-ways-in-which-a-bug-can-be-discovered-in-bug-bounty-program</a></p><p>Pete hacking resources : <a href="https://www.torontowebsitedeveloper.com/hacking-resources">https://www.torontowebsitedeveloper.com/hacking-resources</a></p><p>Learn, Build and Break !!! Stay tuned for next post.</p><p>Stay safe,</p><p>Thanks</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1a9cca7055d2" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>