<?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 Shridhar Rajaput on Medium]]></title>
        <description><![CDATA[Stories by Shridhar Rajaput on Medium]]></description>
        <link>https://medium.com/@cybershree?source=rss-f4e46d3c5a2c------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*fBFZSiLouKsvxJUtDk_y0g.jpeg</url>
            <title>Stories by Shridhar Rajaput on Medium</title>
            <link>https://medium.com/@cybershree?source=rss-f4e46d3c5a2c------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Thu, 19 Nov 2026 17:43:26 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@cybershree/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[How I Earned 24 Acknowledgments from Microsoft & Scored Swag + 195 MVR Points and Listed In 2024…]]></title>
            <link>https://cybersecuritywriteups.com/how-i-earned-24-acknowledgments-from-microsoft-scored-swag-195-mvr-points-and-listed-in-2024-2ca472c516b0?source=rss-f4e46d3c5a2c------2</link>
            <guid isPermaLink="false">https://medium.com/p/2ca472c516b0</guid>
            <category><![CDATA[bug-hunting]]></category>
            <category><![CDATA[bounty-program]]></category>
            <category><![CDATA[writer]]></category>
            <category><![CDATA[google-dorking]]></category>
            <category><![CDATA[microsoft]]></category>
            <dc:creator><![CDATA[Shridhar Rajaput]]></dc:creator>
            <pubDate>Thu, 17 Apr 2025 05:18:42 GMT</pubDate>
            <atom:updated>2025-04-17T05:24:06.102Z</atom:updated>
            <content:encoded><![CDATA[<h3>How I Earned 24 Acknowledgments from Microsoft &amp; Scored Swag + 195 MVR Points and Listed In 2024 Q4 Leaderboard(Using Simple Google Dorks!)</h3><p>Let me take you back to a regular evening not too long ago.<br>I was sitting with my laptop, sipping chai, and just browsing around — no fancy tools, no hardcore recon automation running. Just me, my browser, and a weird thought:</p><p><strong>“What if people are overlooking simple bugs that are just… lying out there in the open?”</strong></p><p>Turns out, they were.</p><p>And by just using some Google search tricks — known in the security world as <strong>Google Dorking</strong> — I ended up reporting <strong>13 impactful bugs</strong> to <strong>Microsoft</strong>, got <strong>24 acknowledgments</strong>, earned <strong>195 MVR Points</strong>, and yes, even got some awesome <strong>Microsoft swag</strong>. 🎁</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/678/1*8prkHR3mt9dh8MCZ55QZdg.jpeg" /></figure><p>But let me tell you something even crazier:<br><strong>Most of the bugs were so simple that beginners often ignore them.</strong></p><h3>👨‍💻 A Little About Me</h3><p>I’ve been in the <strong>cybersecurity space for around 3 years now</strong>. I’ve played around with various areas — CTFs, web app pentesting, a bit of red teaming — but I only seriously got into <strong>bug bounty hunting</strong> recently.</p><p>To sharpen my skills, I completed a course from <strong>BugBountyExplained</strong>, and honestly, that course changed the game for me.</p><p>But I wasn’t alone on this journey.</p><h3>🙌 The Mentors Who Made It All Possible</h3><p>Honestly, I wouldn’t be writing this story today without a few key people who’ve guided me, supported me, and pushed me to see potential where others saw nothing.</p><ul><li><strong>Abdul Rehman Parkar</strong> — I don’t even know where to begin with him. Abdul has been there for me in <strong>every situation</strong> — whether I was stuck, frustrated, or doubting myself. He’s the one who <strong>taught me these Google Dorks</strong>, explained how to spot the sensitive stuff most people miss, and always reminded me that even small bugs matter when you look at them the right way. If this was a video game, Abdul would be that one legendary guide you unlock early who helps you beat the entire game.</li><li><strong>BugBountyExplained</strong> — This guy is on another level when it comes to hunting <strong>high-severity bugs</strong>. His course wasn’t just educational — it was <strong>transformational</strong>. It taught me how to look at systems with a critical eye, how to go deep, and how to write reports that scream “triage me now.” I still refer back to his material whenever I’m hunting or trying to level up my skills.</li><li><strong>HackWithSingh</strong> — If you’re trying to automate your recon and scale your efforts without burning yourself out, this is your guy. He helped me build lightweight automations for scanning dorks, organizing results, and reducing noise. His approach helped me go from finding 1–2 files manually to picking up dozens without lifting a finger.</li></ul><p>Each of these mentors gave me a piece of the puzzle — <strong>curiosity, skill, mindset, and efficiency</strong>. And I owe a huge part of my journey to their guidance.</p><h3>🔍 The Power of Google Dorking</h3><p>I didn’t use Burp. I didn’t scan for CVEs. I didn’t brute force anything.<br> I literally just used Google.</p><p>Here are some of the dorks I started with:</p><pre>site:example.com filetype:pdf intext:(confidential | internal | proprietary | secret | &quot;not for public&quot;)<br>site:exampl.com filetype:xlsx OR filetype:xls OR filetype:doc OR filetype:docx intext:(password | username| credentials )</pre><p>I kept it simple.</p><p>And surprisingly, I found <strong>internal presentations</strong>, <strong>market strategy documents</strong>, <strong>vendor collaborations</strong>, <strong>internal system passwords</strong> and more — all publicly accessible, with labels like “company Confidential” or “Not For Public Distribution.”</p><h3>🧠 What Made These Bugs Valuable?</h3><p>Here’s where I think most beginners get it wrong:<br>They find something exposed, drop the link, and expect a reward.</p><p>That’s not how it works.</p><p>The <strong>real skill</strong> is in <strong>explaining why something matters.</strong></p><p>I made sure every report answered questions like:</p><ul><li>Why is this document sensitive?</li><li>What impact could it have if a competitor or attacker got it?</li><li>Is there any mention of company strategies, client data, or internal systems?</li><li>Is the information labeled as “confidential,” and is it meant for internal use only?</li></ul><h3>✉️ Sample Report That Got Instantly Triaged</h3><p>Let me show you one of the reports I sent that required <strong>no back-and-forth</strong>. Microsoft triaged it instantly:</p><p><strong>Title:</strong> Public Exposure of Confidential Document: <em>Transformación digital para MiPyMes</em> (by Edelman México)</p><p><strong>Hi Microsoft Security Team,</strong></p><p>I discovered that a confidential PDF titled <em>“Title of the file”</em>, is publicly accessible on a Microsoft domain.</p><p>This document contains sensitive business information related to Microsoft’s digital transformation strategy for small and medium-sized businesses (MiPyMes) in Latin America.</p><h3>🧩 Key Insights Inside the PDF:</h3><ul><li>Digital transformation trends, challenges, and opportunities in LATAM</li><li>Cybersecurity concerns for small businesses</li><li>Adoption of Microsoft services like Azure, Office, Power BI, and Dynamics 365</li><li>Remote work strategies and talent acquisition plans</li><li>Collaboration details with Edelman México</li><li>Internal strategy and execution models</li></ul><h3>⚠️ Security Implications:</h3><ul><li><strong>Business Intelligence Risk:</strong> Competitors could reverse-engineer Microsoft’s strategy</li><li><strong>Reputation Risk:</strong> Customers and partners may lose trust seeing internal docs publicly available</li><li><strong>Vendor Risk:</strong> Disclosing third-party collaboration details like Edelman’s involvement</li><li><strong>Loss of Competitive Edge:</strong> Market insights and product usage stats give away too much</li></ul><p><strong>Conclusion:</strong><br>This file is labeled as confidential and contains highly sensitive data. I recommend its immediate removal and access control review.</p><p>Happy to provide more details if required.</p><p>Best regards,<br><strong>Shridhar Rajaput</strong></p><p>They didn’t even ask for more info. The report was <strong>clean, detailed, and clear</strong>. That’s what triagers love.</p><h3>🎁 What I Got in Return</h3><p>Thanks to consistent, responsible reporting and keeping things professional, here’s what I earned:</p><p>✅ <strong>24 Microsoft Acknowledgments</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*2xRNf1n3PVpFpt9iT4oaEw.jpeg" /></figure><p>🎉 <strong>195 MVR Points</strong> (which count toward bigger rewards)<br> 📦 <strong>Official Microsoft Swag</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Gj9XidRhykqs9HL1AdCWjw.jpeg" /></figure><p>🏆 <strong>Got listed in the 2024 Q4 Microsoft Security Researcher Leaderboard</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*84l0MEmODjP2kOFKvWZ6bg.png" /></figure><p>💪 And most importantly, the confidence of knowing I contributed to one of the most secure ecosystems in the world</p><p>And remember — this all came from bugs that many people might call “basic.”</p><p>But when reported the right way?<br><strong>Basic turns into valuable.</strong></p><h3>💬 Final Thoughts for Beginner Bug Hunters</h3><p>If you’re new to bug bounty, here’s my advice straight from the heart:</p><ul><li><strong>Don’t chase CVEs if you don’t understand them yet.</strong> Start with misconfigurations and info leaks.</li><li><strong>Google is your best friend.</strong> You don’t always need complex tools.</li><li><strong>Reporting is 50% of the job.</strong> Make your reports readable, respectful, and explain <em>why it matters</em>.</li><li><strong>Never stop learning.</strong> I still learn every single day from people like Abdul Rehman Parkar, HackWithSingh, and the BugBountyExplained community.</li></ul><p>You don’t need to be elite to make an impact.<br>Sometimes, all you need is <strong>curiosity, persistence, and a clean Google search bar.</strong></p><p>📩 If you want help crafting better reports, learning how to use dorks effectively, or just want to chat about your bug bounty journey — <strong>reach out!</strong> I’m happy to help others the same way I was helped.</p><p>Much love to the entire security community.</p><p>— <br> <a href="https://www.instagram.com/hacktive_shree?igsh=NWwxNHozenhuM2oy&amp;utm_source=qr"><strong>Shridhar Rajaput</strong></a> 🛡️<br> <em>Cybersecurity Enthusiast | Bug Bounty Hunter | Proud Learner</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2ca472c516b0" width="1" height="1" alt=""><hr><p><a href="https://cybersecuritywriteups.com/how-i-earned-24-acknowledgments-from-microsoft-scored-swag-195-mvr-points-and-listed-in-2024-2ca472c516b0">How I Earned 24 Acknowledgments from Microsoft &amp; Scored Swag + 195 MVR Points and Listed In 2024…</a> was originally published in <a href="https://cybersecuritywriteups.com/">Cyber Security 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[My Journey Finding Bugs on NASA]]></title>
            <link>https://cybersecuritywriteups.com/my-journey-finding-bugs-on-nasa-a2296d142b0a?source=rss-f4e46d3c5a2c------2</link>
            <guid isPermaLink="false">https://medium.com/p/a2296d142b0a</guid>
            <category><![CDATA[bug-bounty-writeup]]></category>
            <category><![CDATA[inspiration]]></category>
            <category><![CDATA[cybersecurity]]></category>
            <category><![CDATA[bug-bounty]]></category>
            <category><![CDATA[information-technology]]></category>
            <dc:creator><![CDATA[Shridhar Rajaput]]></dc:creator>
            <pubDate>Fri, 22 Nov 2024 09:10:16 GMT</pubDate>
            <atom:updated>2024-11-24T09:00:28.788Z</atom:updated>
            <content:encoded><![CDATA[<h3>My Journey Finding Bugs on NASA: How I Gained Recognition from <strong>NASA</strong></h3><p>Hello researchers, my name is <strong>Shridhar Rajaput</strong>,a security researcher on Bugcrowd. Over time, I’ve hunted down and reported a bunch of vulnerabilities, but one of my most interesting finds happened using google dork when I decided to take a swing at finding bugs at <strong>NASA</strong>. Let me tell you how it all started.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*IIzf4fBLyHrxahI1.jpg" /></figure><h3>What Are Google Dorks?</h3><p>Google Dorking is nothing but a kind of filter, meaning that the dork you provide will only show the results that you need. For example, if you only need PDF files from a particular domain, using Google Dorking will bring up only the PDF files from that site. It won’t show a lot of unrelated data. But it is also used to find sensitive information, such as sensitive files or documents from a particular website, which could include confidential files, etc. Hackers often use Google Dorking to locate exposed or vulnerable files that should not be publicly accessible.</p><h4>So, let’s begin.</h4><p>It all began when I saw a post on Instagram about a “<strong>Letter of Recognition” from NASA</strong>. It caught my eye, and I thought to myself, <em>“</em><strong><em>What is this about?</em></strong><em> </em><strong><em>How can I get one?</em></strong><em>”</em> After some digging, I found out that people were getting these letters by finding bugs on <strong>NASA’s</strong> platforms through <strong>Bugcrowd</strong>. This really sparked my interest, and I decided to give it a go.</p><p>Now, I knew the first step was to gather some information. So, I started with <strong>OSINT</strong> (Open Source Intelligence), looking for subdomains, main domains, and using tools like WaybackURLs. But after all that work, I didn’t find anything useful.</p><p>Then, one day, I stumbled upon an interesting article on Medium about Google Dorks. I’d heard of it before but never really looked into it. The article sparked something in me, and I thought, <strong><em>“Why not give it a try?”</em></strong> So, I began searching using Google Dorks.</p><p>Usually, when I start my search with Google Dorks, I begin with some advanced queries. These are things like:</p><ul><li>site:target.com filetype:pdf &quot;sensitive keywords&quot;</li><li>inurl:admin filetype:sql</li><li>intitle:&quot;index of&quot; &quot;backup&quot;</li><li>filetype:doc confidential</li></ul><p>These queries help me find specific file types or pages that might contain sensitive information. They allow me to dig deeper into a website and uncover things that might have been missed during the initial search.</p><p>At first, I found a bunch of files, but nothing really stood out. I kept searching, but nothing interesting popped up. After a while, I came across a file marked “Confidential.” I thought, <strong><em>“This could be it!”</em></strong> but when I reported it, I was told it was a duplicate. So, I decided to take a break and went out for a coffee.</p><p>A few hours later, I came back and decided to give it one more shot. This time, I thought about modifying my search with some different keywords. I typed in site:target.com filetype:pdf &quot;internal&quot;. And then, I found it—<em>a file called </em><strong><em>&quot;Internal Quality Auditing.&quot;</em></strong></p><p>It immediately caught my attention. I thought, <strong><em>“This could be sensitive. It’s an audit report, and it’s internal. Definitely something that shouldn’t be out in the open.”</em> </strong>I decided to create a bug report and submitted it to Bugcrowd.</p><p>Within 15 hours, I got a message back from Bugcrowd.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/992/1*iYwonqw8iYVyCmNm_VUnbA.png" /></figure><p>I replied, explaining my findings.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/967/1*Bco5bqfMasylzZFfGn_gHg.png" /></figure><p>Two days later, the bug was triaged, and the vulnerability was accepted.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*atRQLIw6w0-jgH-tMiA_Tw.png" /></figure><p>About a month later, I got the notification that the bug was resolved.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*W55nb5zXiIUUox-TLcuH3A.png" /></figure><p>And after one day, I got <strong>Letter of Appreciation</strong> From <strong>NASA</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/639/1*6qpkOEJ9LS_0jmqwH7GcSg.png" /></figure><p>It was a pretty thrilling experience, and it all started from that simple curiosity about <strong>NASA</strong> and that <strong>Instagram</strong> post. It just goes to show how sometimes, a simple idea or a random thought can lead to discovering something significant.</p><p>Thanks for reading, and I hope you found my write-up informative.</p><p>Happy hunting, and remember to test responsibly!</p><p><strong>Shridhar Rajaput:</strong></p><p><strong>LinkedIn:</strong><a href="https://www.linkedin.com/in/shridhar-rajaput/"><strong>https://www.linkedin.com/in/shridhar-rajaput/</strong></a></p><p><strong>Instagram:</strong><a href="https://www.instagram.com/hacktive_mind/profilecard/?igsh=NWwxNHozenhuM2oy"><strong>https://www.instagram.com/hacktive_mind/profilecard/?igsh=NWwxNHozenhuM2oy</strong></a></p><p><strong>Acknowledgments</strong></p><p>Special thanks to my mentors:</p><p><strong>Harsh Sir : </strong><a href="https://www.instagram.com/bugbountyexplained/profilecard/?igsh=MTJyNTFha3pmOWhnOA=="><strong>https://www.instagram.com/bugbountyexplained/profilecard/?igsh=MTJyNTFha3pmOWhnOA==</strong></a></p><p><strong>Abdul Sir : </strong><a href="https://www.instagram.com/abdulprkr/profilecard/?igsh=MWlxYWFhcHVoMzdheg=="><strong>https://www.instagram.com/abdulprkr/profilecard/?igsh=MWlxYWFhcHVoMzdheg==</strong></a></p><p>Their guidance has been instrumental in my journey.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a2296d142b0a" width="1" height="1" alt=""><hr><p><a href="https://cybersecuritywriteups.com/my-journey-finding-bugs-on-nasa-a2296d142b0a">My Journey Finding Bugs on NASA</a> was originally published in <a href="https://cybersecuritywriteups.com/">Cyber Security 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[Easy P3 Bug: A Spoofing Vulnerability]]></title>
            <link>https://medium.com/@cybershree/easy-p3-bug-a-spoofing-vulnerability-ca73a62b6f48?source=rss-f4e46d3c5a2c------2</link>
            <guid isPermaLink="false">https://medium.com/p/ca73a62b6f48</guid>
            <category><![CDATA[cybersecurity]]></category>
            <category><![CDATA[penetration-testing]]></category>
            <category><![CDATA[bug-bounty]]></category>
            <category><![CDATA[linkedin]]></category>
            <category><![CDATA[information-technology]]></category>
            <dc:creator><![CDATA[Shridhar Rajaput]]></dc:creator>
            <pubDate>Fri, 18 Oct 2024 15:51:45 GMT</pubDate>
            <atom:updated>2024-10-19T05:16:08.416Z</atom:updated>
            <content:encoded><![CDATA[<p>My name is Shridhar Rajaput, and as a security researcher, I constantly explore the intricacies of cybersecurity. Recently, I encountered a concerning vulnerability related to email security that revealed significant risks associated with missing protective measures.</p><h3>The Discovery</h3><p>One afternoon, while investigating an email domain, I noticed something alarming: the absence of essential email authentication protocols — SPF, DKIM, and DMARC. These records play a critical role in preventing email spoofing, a technique often used by malicious actors to impersonate legitimate senders and deceive recipients.</p><p>Curious about the implications of this oversight, I delved deeper into the situation. Without SPF, DKIM, and DMARC, the domain was left vulnerable to spoofing attacks, allowing anyone to send emails that appeared to originate from the legitimate domain.</p><h3>The Implications</h3><p>The implications of this missing security were serious. I could envision a scenario where an attacker, armed with just a few simple tools, could easily forge emails that appeared to come from trusted sources. Imagine the chaos that could ensue! Phishing attacks could run rampant, users might unwittingly provide sensitive information, and trust in the domain would plummet. Not to mention the risk of malware spreading like wildfire through unsuspecting recipients.</p><h3>The Experiment</h3><p>Curiosity piqued, I decided to put this vulnerability to the test. I crafted a spoofed email, leveraging the absence of SPF, DKIM, and DMARC records. With a few clicks, I sent the email off into the digital ether, using ProtonMail to receive it. The ease with which I could execute this attack was both alarming and illuminating, confirming my fears about the domain’s security posture.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*MkCkHK1xJ9xG1b3ynA8cJQ.png" /></figure><h3>A Call to Action</h3><p>Realizing the urgency of the situation, I meticulously documented my findings. I outlined the necessity for the domain to implement SPF, DKIM, and DMARC records, emphasizing that each one serves a critical purpose:</p><ul><li><strong>No DKIM</strong>: This oversight classifies the vulnerability as a P5.</li><li><strong>No DMARC</strong>: This elevates it to a P4.</li><li><strong>No valid SPF</strong>: All combined, this amounts to a P3 vulnerability.</li></ul><p>For those looking to check or implement these records, here are some helpful tools:</p><ul><li>SPF, <a href="http://dkimvalidator.com/">DKIM</a> and DMARC Record Checker : <a href="https://easydmarc.com/tools/domain-scanner?domain">https://easydmarc.com/tools/domain-scanner?domain</a></li><li>Fake Email Sender : <a href="https://emkei.cz/">https://emkei.cz/</a></li><li>Email Receiver : <a href="https://proton.me/mail">https://proton.me/mail</a></li></ul><h3>Conclusion</h3><p>With a sense of urgency, I submitted my report, eager for the team to address this critical issue. However, to my surprise, I soon learned that this vulnerability had already been reported as a duplicate and remained unresolved. This experience served as a poignant reminder of the importance of collaboration within the cybersecurity community.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/644/1*7vBHymS2PoDm5BnFEBliHg.png" /></figure><p>If you’d like to connect or discuss further, feel free to reach out to me on LinkedIn: <a href="https://www.linkedin.com/in/shridhar-rajaput/">Shridhar-Rajaput</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ca73a62b6f48" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Easy P4 Bug #2: Account Deletion Lacks Password Verification]]></title>
            <link>https://medium.com/@cybershree/p4-bug-2-account-deletion-lacks-password-verification-a8633a00c9fc?source=rss-f4e46d3c5a2c------2</link>
            <guid isPermaLink="false">https://medium.com/p/a8633a00c9fc</guid>
            <category><![CDATA[cybersecurity]]></category>
            <category><![CDATA[bugs]]></category>
            <category><![CDATA[security-research]]></category>
            <category><![CDATA[bug-bounty]]></category>
            <category><![CDATA[information-technology]]></category>
            <dc:creator><![CDATA[Shridhar Rajaput]]></dc:creator>
            <pubDate>Fri, 18 Oct 2024 15:27:30 GMT</pubDate>
            <atom:updated>2024-10-18T15:29:42.038Z</atom:updated>
            <content:encoded><![CDATA[<p>My name is Shridhar Rajaput, and as a security researcher, I often find myself navigating the intricate pathways of digital applications, always searching for vulnerabilities that could endanger user security. Recently, I stumbled upon a glaring oversight regarding account deletion — a discovery that raised significant concerns about user data protection.</p><h3>The Discovery</h3><p>On a seemingly ordinary day, I was testing the account management features of an application. As I explored, I noticed the option for users to delete their accounts. Intrigued, I followed the prompts to see how the process was designed. Everything appeared straightforward — until I reached the final step.</p><p>To my shock, there was no password confirmation required before completing the account deletion process. It struck me as a severe oversight. In a world where account security is paramount, allowing a user to delete their account without confirming their identity posed a substantial risk.</p><h3>The Implications</h3><p>This absence of a password confirmation step could lead to significant consequences:</p><ol><li><strong>Accidental Deletion</strong>: A user could inadvertently delete their account without realizing it, losing access to valuable data.</li><li><strong>Malicious Activity</strong>: An attacker with access to the user’s device could easily delete their account, causing disruption and loss of information.</li><li><strong>Loss of Trust</strong>: Users may feel uneasy knowing that their accounts could be deleted without proper verification, eroding their trust in the platform.</li></ol><h3>The Experiment</h3><p>Curious about the impact of this oversight, I decided to simulate a potential attack scenario. I documented my steps, highlighting the ease with which someone could exploit this vulnerability. Without any password confirmation, I could delete an account within seconds, leaving no trace of my actions.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/612/1*grNvMxKrbMV-kALQk9Nofg.jpeg" /></figure><h3>A Call to Action</h3><p>Recognizing the urgency of addressing this issue, I crafted a detailed report outlining my findings. I emphasized the necessity for implementing a password confirmation step to safeguard users during the account deletion process. This simple addition could significantly enhance security and user confidence.</p><h3>Conclusion</h3><p>As I submitted my report, I was eager to see how the team would respond. However, to my surprise, I discovered that this bug had been reported before me and marked as a duplicate. While I was disappointed, this experience served as a reminder of the importance of collaboration within the security community. Each discovery contributes to a collective understanding that helps protect users everywhere.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/511/1*ElJzDzzZGl8WnmU7hZgKHg.png" /></figure><p>This journey into the realm of account management underscored the critical need for vigilant security practices. As researchers, we must continue to advocate for enhancements that prioritize user safety and trust in our digital environments.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a8633a00c9fc" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Easy P4 Bug : Failure to Invalidate Sessions Post Password Change]]></title>
            <link>https://medium.com/@cybershree/easy-p4-bug-failure-to-invalidate-sessions-post-password-change-56a3aee9e8cc?source=rss-f4e46d3c5a2c------2</link>
            <guid isPermaLink="false">https://medium.com/p/56a3aee9e8cc</guid>
            <category><![CDATA[cybersecurity]]></category>
            <category><![CDATA[bug-bounty]]></category>
            <category><![CDATA[information-technology]]></category>
            <category><![CDATA[hackerone]]></category>
            <category><![CDATA[ethical-hacking]]></category>
            <dc:creator><![CDATA[Shridhar Rajaput]]></dc:creator>
            <pubDate>Fri, 18 Oct 2024 15:09:49 GMT</pubDate>
            <atom:updated>2024-10-18T15:09:49.664Z</atom:updated>
            <content:encoded><![CDATA[<h3>Easy P4 Bug : Failure to Invalidate Sessions Post Password Change</h3><p>My name is Shridhar Rajaput, and as a security researcher, my days are often filled with exploration and discovery within the digital realm. Recently, I encountered a puzzling scenario that unveiled a significant flaw in session management — a flaw that could compromise user security in unexpected ways.</p><h3>The Discovery</h3><p>One ordinary afternoon, I logged into an application using my valid credentials, ready to test its functionalities. Everything seemed secure, or so I thought. With the mindset of any proactive user, I decided it was time to change my password — a standard practice that every user should follow.</p><p>Navigating to the account settings, I updated my password without hesitation. But then, curiosity struck: what happens to my active session when I change my password? Would it remain intact, or would I be logged out?</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*mj6iOmNvYTe37I-0.png" /></figure><h3>The Experiment</h3><p>To satisfy my curiosity, I opened a new incognito window while keeping my original session active. What I found left me astonished: I was still able to access my account and perform actions seamlessly. It was as if the password change had no impact on my existing session!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/220/1*yOf74R1D6m5pZXsSAogsRQ.gif" /></figure><p>This moment was eye-opening. Here was a significant security oversight — an attacker who managed to gain access to an active session could exploit this flaw, manipulating the account without the user’s knowledge or consent.</p><h3>The Implications</h3><p>The implications of this vulnerability were grave:</p><ol><li><strong>Unauthorized Access</strong>: An attacker could hijack an active session post-password change, leading to potential identity theft or data breaches.</li><li><strong>Loss of Control</strong>: Users believing they had secured their accounts by changing their passwords would remain vulnerable, unaware that their old sessions were still active.</li></ol><h3>A Call to Action</h3><p>Recognizing the urgency of the situation, I documented my findings meticulously. I emphasized the necessity for the application to invalidate all active sessions immediately upon a password change. Additionally, I suggested implementing user notifications regarding active sessions, empowering users to take charge of their security.</p><h3>Conclusion</h3><p>As I submitted my report, I reflected on the lessons learned from this experience. It served as a stark reminder that even minor oversights in session management can lead to substantial vulnerabilities. As security researchers, we must remain vigilant and proactive in our efforts to safeguard user accounts.</p><p>Interestingly, when I submitted my findings, I learned that this bug had been reported before me and was marked as a duplicate. This experience reinforced the importance of collaboration in the security community, where shared knowledge can lead to stronger protections for all users.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/535/1*hpBnOWDD_luZ9l-DBCf12g.png" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=56a3aee9e8cc" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[A Security Researcher’s Journey: Uncovering an Account Takeover Vulnerability]]></title>
            <link>https://medium.com/@cybershree/a-security-researchers-journey-uncovering-an-account-takeover-vulnerability-624763bd4ecd?source=rss-f4e46d3c5a2c------2</link>
            <guid isPermaLink="false">https://medium.com/p/624763bd4ecd</guid>
            <category><![CDATA[cybersecurity]]></category>
            <category><![CDATA[security]]></category>
            <category><![CDATA[bug-bounty-tips]]></category>
            <category><![CDATA[vulnerability]]></category>
            <category><![CDATA[bug-bounty]]></category>
            <dc:creator><![CDATA[Shridhar Rajaput]]></dc:creator>
            <pubDate>Fri, 18 Oct 2024 14:41:19 GMT</pubDate>
            <atom:updated>2024-10-18T14:45:28.270Z</atom:updated>
            <content:encoded><![CDATA[<p>My name is Shridhar Rajaput, and as a security researcher, my journey often takes me into the depths of digital landscapes, where I hunt for vulnerabilities that could put users at risk. Recently, I stumbled upon a chilling vulnerability that revealed just how fragile our online security can be.</p><h3>The Discovery</h3><p>It all began one quiet afternoon as I navigated the familiar interface of <a href="http://www.foreignaffairs.com./"><strong>www.maindomain.com</strong>.</a> I was curious about the account management features, particularly how users could manage their subscription information. Little did I know that what I was about to uncover would send shivers down my spine</p><p>After logging into my test account — let’s call it “User A” — I decided to explore the subscription management section. I was armed with my usual toolkit and a desire to identify potential weaknesses. As I ventured deeper, I encountered the option to change the email address linked to the account.</p><h3>The Twist</h3><p>My curiosity piqued, I opened a separate browser and created a second account, “User B.” This would be the account I would use to test the boundaries of the platform’s security. What happened next was both surprising and alarming.</p><p>Navigating to the subscription management section of <a href="https://subscribe.foreignaffairs.com/"><strong>https://test.maindomain.com/</strong></a>, I entered the email address of my victim account — User A — without any verification or validation checks. I was prepared for an error, perhaps a warning that the email was already in use. Instead, the system accepted my request without a hitch. I felt a rush of adrenaline as I realized the potential implications of this oversight.</p><h3>The Moment of Truth</h3><p>With my heart racing, I logged out of User B’s account and attempted to log into User A’s account using the victim’s email address and the password I had registered for User B. To my astonishment, I was granted access. I found myself staring at the dashboard of User A’s account, with access to saved articles and personal data that were never meant to be mine.</p><p>In that moment, the gravity of what I had just accomplished hit me. This wasn’t just a technical flaw; it was a gaping hole in the security framework of the application. An attacker could easily exploit this vulnerability to take over accounts, leading to severe consequences for unsuspecting users.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/738/1*pFb05nTecbBz_PBfDTDvkA.png" /></figure><h3>The Broader Implications</h3><p>Reflecting on what I had uncovered, I recognized the broader implications of this vulnerability:</p><ol><li><strong>Unauthorized Access</strong>: An attacker could gain access to sensitive data, potentially leading to identity theft.</li><li><strong>Loss of Control</strong>: Victims might find themselves locked out of their accounts, unable to reclaim their identity.</li><li><strong>Erosion of Trust</strong>: Users could lose faith in the platform if they believed their accounts were so easily compromised.</li></ol><h3>A Call to Action</h3><p>Understanding the critical nature of this vulnerability, I knew I had to raise my concerns. I drafted a detailed report outlining my findings, emphasizing the need for stronger validation processes. My recommendations included implementing email verification steps and strengthening account recovery mechanisms to protect users from unauthorized changes.</p><p>I submitted my findings, hoping they would resonate with the security team. However, I was met with a response indicating that the out-of-scope domain had influenced their decision. While I understood the importance of scope, I couldn’t shake the feeling that the vulnerability’s implications warranted further examination.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/969/1*XAXtyjFCzjlmuWA297ZR6g.png" /></figure><h3>Conclusion</h3><p>As a security researcher, my mission is clear: to uncover vulnerabilities and advocate for the protection of users. This experience served as a reminder of the delicate balance between convenience and security in our digital lives. I hope to inspire fellow researchers and developers to prioritize user safety and implement robust security measures.</p><p>The journey continues, and with each discovery, I’m reminded of the critical role we all play in safeguarding our online communities.</p><p>Thank you for joining me on this journey. I welcome your thoughts and insights as we work together to build a more secure digital world.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=624763bd4ecd" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Discovering Facebook OAuth Misconfigurations: A Journey into Pre-Account Takeover]]></title>
            <link>https://medium.com/@cybershree/discovering-facebook-oauth-misconfigurations-a-journey-into-pre-account-takeover-92a38254cbec?source=rss-f4e46d3c5a2c------2</link>
            <guid isPermaLink="false">https://medium.com/p/92a38254cbec</guid>
            <category><![CDATA[bug-bounty]]></category>
            <category><![CDATA[bug-bounty-tips]]></category>
            <category><![CDATA[writing]]></category>
            <category><![CDATA[cybersecurity]]></category>
            <category><![CDATA[bugcrowd]]></category>
            <dc:creator><![CDATA[Shridhar Rajaput]]></dc:creator>
            <pubDate>Mon, 30 Sep 2024 06:23:43 GMT</pubDate>
            <atom:updated>2024-11-11T06:11:39.205Z</atom:updated>
            <content:encoded><![CDATA[<h3><strong>By Shridhar Rajaput (Cyber_Shree)</strong></h3><p>In the ever-evolving landscape of web security, each day can feel like a new adventure. As a bug bounty hunter, I thrive on the challenge of uncovering vulnerabilities and helping platforms strengthen their defenses. Recently, I embarked on an exciting journey with a program that oversees numerous e-commerce websites. Little did I know, I was about to stumble upon a series of Facebook OAuth misconfigurations that led to a fascinating case of pre-account takeover.</p><h3>The Prelude: Setting the Stage</h3><p>It all began when I signed up for the program on <strong>example.com</strong>, a platform managing over ten e-commerce sites. With a reputation for robust security, I was eager to dive into the intricacies of their systems. As I explored the various functionalities, I landed on the registration page. Here, I noticed an option for Facebook Single Sign-On (SSO) — a convenient feature that allows users to log in using their Facebook accounts.</p><p>I’ve encountered similar OAuth misconfigurations before, but this time, I was determined to dig deeper. My mind raced with possibilities as I recalled the concept of pre-account takeover — an alarming vulnerability that could allow an attacker to gain access to another user’s account through improper OAuth configuration.</p><h3>The Discovery: Creating a Test Case</h3><p>Armed with this knowledge, I set out to create a test case. The rules were straightforward:</p><ol><li><strong>No email verification</strong>: The target system did not require users to verify their email addresses.</li><li><strong>Facebook account linkage</strong>: The Facebook account must be associated with the victim’s email.</li></ol><p>With my objectives clear, I crafted an account using the email address victim@gmail.com. The registration process was quick and seamless. I successfully logged in and was greeted by a dashboard, which had no sign of the lurking vulnerability — yet.</p><h3>The Breakthrough: The Moment of Truth</h3><p>Now came the thrilling part. I logged out of my freshly created account and proceeded to register with the Facebook account linked to victim@gmail.com. With bated breath, I initiated the login process, utilizing Facebook SSO.</p><p>Boom! Just like that, I found myself logged into the victim’s account. The seamless transition between accounts highlighted the critical oversight in the OAuth implementation. I was able to see the victim’s details, as my newly created account was now improperly linked to their Facebook profile.</p><h3>Reporting the Findings</h3><p>Elated by my discovery, I quickly documented the findings and prepared my report for the Bugcrowd platform. I identified five instances of this Facebook OAuth misconfiguration across various e-commerce websites managed by example.com. Each bug was a potential gateway for pre-account takeover, a serious risk that could jeopardize user data and trust.</p><p>However, as I submitted my report, I learned that my findings were marked as duplicates. While it was disappointing to realize that other security researchers had uncovered similar issues, I felt a sense of camaraderie with my fellow hunters. The program awarded me points for each of the three bugs I reported, totaling fifteen points for my contributions.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*7XSADUDNm-3zQh78JYnWOA.png" /></figure><h3>A Month of Discoveries</h3><p>Reflecting on this experience, it’s been a productive month and twelve days since I started focusing on bug bounty programs. During this time, I reported a total of <strong>41</strong> <strong>vulnerabilities</strong> on <strong>Bugcrowd.</strong> Each submission not only contributed to improving security for various platforms but also deepened my understanding of the complexities of web applications.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*PCf7xl4C-YAIvnokCZbubg.png" /></figure><h3>The Reflection: Lessons Learned</h3><p>Even though my findings were duplicates, this experience reinforced several vital lessons:</p><ol><li><strong>Vigilance is Key</strong>: Security is an ongoing process, and vulnerabilities can easily slip through the cracks. Regular audits and testing are crucial.</li><li><strong>Collaboration is Valuable</strong>: The bug bounty community thrives on collaboration. Sharing knowledge and insights can help us all build stronger defenses.</li><li><strong>Persistence Pays Off</strong>: Each report contributes to a larger picture of security. Even if duplicates occur, the cumulative effort makes a difference.</li></ol><p>As I wrapped up my findings and reflected on the journey, I felt invigorated by the thrill of discovery. Bug hunting isn’t just about finding bugs; it’s about the stories we tell and the security we help forge. Until the next adventure, I’ll continue to explore the digital realm with curiosity and determination.</p><p><strong>Conclusion</strong></p><p>Through this experience, I learned that the world of cybersecurity is filled with challenges that require diligence and creativity. Every report, whether a duplicate or not, plays a role in enhancing security. I am grateful for the opportunity to contribute and look forward to future discoveries.</p><p><strong>Stay safe, and happy hunting!</strong></p><p>— Shridhar Rajaput, aka Cyber_Shree</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=92a38254cbec" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Finding My First P4 Valid Bug: A Journey Through a Vulnerability Disclosure Program]]></title>
            <link>https://medium.com/@cybershree/finding-my-first-p4-valid-bug-a-journey-through-a-vulnerability-disclosure-program-ccbcf3dfaf24?source=rss-f4e46d3c5a2c------2</link>
            <guid isPermaLink="false">https://medium.com/p/ccbcf3dfaf24</guid>
            <dc:creator><![CDATA[Shridhar Rajaput]]></dc:creator>
            <pubDate>Sun, 15 Sep 2024 12:35:03 GMT</pubDate>
            <atom:updated>2024-09-15T12:35:03.179Z</atom:updated>
            <content:encoded><![CDATA[<p>Hi everyone, I’m Shridhar Rajaput, a passionate bug hunter. Today, I’m excited to share the story of my first P4 valid bug, which I discovered and had accepted through a vulnerability disclosure program (VDP) on Bugcrowd. For privacy reasons, I will refer to the program as “redacted.com.” I hope my journey will provide insights and encourage fellow bug hunters to dive into similar challenges.</p><h4>The Approach: Starting with Subdomain Enumeration</h4><p>My journey began with subdomain enumeration, a critical first step in understanding the surface area of the target application. To identify potential attack vectors, I employed several tools:</p><ul><li><strong>Subfinder</strong></li><li><strong>Sublister</strong></li><li><strong>Findomain</strong></li><li><strong>Assetfinder</strong></li></ul><p>After gathering a list of subdomains, I consolidated them into a single file, focusing on finding those with active and potentially interesting endpoints.</p><h4>Identifying Live Subdomains</h4><p>The next step was to verify which of these subdomains were live. I used <strong>httprobe</strong>, a tool that helps identify live HTTP and HTTPS endpoints. This allowed me to filter out non-functional subdomains and concentrate on the ones that were operational.</p><h4>Discovery: Insecure Communication on HTTP</h4><p>During my investigation, I came across several URLs that allowed login via the HTTP protocol. This was a red flag, as transmitting sensitive information over HTTP can expose data to interception.</p><p>To delve deeper, I used <strong>Wireshark</strong> to capture network traffic and observe the data being transmitted. I performed a test by inputting random credentials — email, password, and OTP — into the login forms.</p><p>To my concern, I could see this information in plain text over the network traffic. This clearly indicated that sensitive information was being sent unencrypted.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*L9IaZthygjQe8bcC8urE5A.png" /><figcaption>capturing traffic with Wireshark</figcaption></figure><h4>Reporting the Vulnerability</h4><p>After confirming the vulnerability, I prepared a detailed report for the VDP team. My report included:</p><ul><li>Evidence of the vulnerability (Wireshark captures)</li><li>Steps to reproduce the issue</li><li>Recommendations for securing the communication channel (e.g., enforcing HTTPS)</li></ul><p>I submitted the report through Bugcrowd’s platform and was pleased to receive a triage response. Despite having reported two similar issues for the program, this one was recognized and accepted as a P4 valid bug.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*NAw_abDLvxokaGkJmeOyeg.png" /><figcaption>Vulnerability Accepted</figcaption></figure><h4>Conclusion</h4><p>Bug hunting is an ever-evolving field, and each discovery contributes to the overall security landscape. My experience with “redacted.com” was both challenging and rewarding. Keep learning, stay curious, and happy hunting!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ccbcf3dfaf24" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>