<?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 TheBountyBox on Medium]]></title>
        <description><![CDATA[Stories by TheBountyBox on Medium]]></description>
        <link>https://medium.com/@thebountybox?source=rss-690fd279bd24------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*O8DiVc0Ht1q6OwzOiHuUKg.png</url>
            <title>Stories by TheBountyBox on Medium</title>
            <link>https://medium.com/@thebountybox?source=rss-690fd279bd24------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 00:05:55 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@thebountybox/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[Param Hunting to Injections]]></title>
            <link>https://infosecwriteups.com/param-hunting-to-injections-4365da5447cf?source=rss-690fd279bd24------2</link>
            <guid isPermaLink="false">https://medium.com/p/4365da5447cf</guid>
            <category><![CDATA[testing]]></category>
            <category><![CDATA[infosec]]></category>
            <category><![CDATA[bug-bounty]]></category>
            <category><![CDATA[ethical-hacking]]></category>
            <category><![CDATA[cybersecurity]]></category>
            <dc:creator><![CDATA[TheBountyBox]]></dc:creator>
            <pubDate>Fri, 16 Dec 2022 07:48:48 GMT</pubDate>
            <atom:updated>2023-10-23T18:08:23.724Z</atom:updated>
            <content:encoded><![CDATA[<h4>Hey hackers! How’s your week going?</h4><p>Here we are back with another blog.</p><p>Today we are going to discuss Effective Param-Hunting to Injections</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/498/1*I33Yi-NXdCJT6zzlt0tbLQ.gif" /></figure><p>So recently we have been working on a private project . Let’s call it <em>redacted.com</em> .</p><p>Since there were a lot of subdomains, we thought of filtering the subdomains based on the <em>content-length</em> to find domains which offer a large number of functionalities.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/875/0*bNwJtD32njEvAFLO" /></figure><p>So after filtering, we landed on &lt;Sub.redacted.com&gt; which had a login page.</p><p>Initially, we were looking for BAC; meanwhile, we noticed that when we enter invalid credentials on the login page, it responds with an error parameter in the url.</p><p>So briskly we started to inject <em>XSS</em> payloads to generate an <em>XSS</em> but no luck since we were unable to bypass the filtering.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/580/0*2cyUSkg9GAX7o8Kk" /></figure><p>Soon after we started to test the password reset functionality .</p><p>Here we noticed that after entering any invalid email there was no error param generated in the url so we thought of manually adding this param .</p><p>To our surprise the param was actually reflecting .</p><p>Again we tried injecting the <em>XSS</em> payloads but WAF was blocking everything.</p><p>Finally we thought of balancing using the &lt;/div&gt; tag since the and boom here comes <strong>HTML Injection</strong> .</p><p>We know what you’re thinking, yeah <strong>IFRAME</strong> did the rest of the work .</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/220/1*IRl67FxRuy8-t3pVALBArg.gif" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*LaHEhOeDT5mc38Xx" /></figure><p><strong>Finding Hidden Parameters :</strong></p><p>There are a lot of tools like Paramminer , Arjun ,x8 etc that help us in finding hidden parameters but unfortunately in our case neither tool worked because the parameter might not be present in the default word list .</p><p><strong>Active Param Hunting :</strong></p><p>Active Param Hunting helps in detecting all the params and generating a custom target specific wordlist .</p><p>For Creating a custom wordlist we need to extract all the parameters related to the domain and for this we will use this beautiful tool <a href="https://github.com/xnl-h4ck3r/GAP-Burp-Extension"><em>getAllParams</em></a> .</p><h4>Steps :</h4><ol><li>Download and configure <a href="https://github.com/xnl-h4ck3r/GAP-Burp-Extension">getAllParams</a> extension in your burp suite</li><li>Now start crawling the website automatically as well as manually .</li></ol><p>A combination of manually testing and automation will always provide you with better results than blinding using the scripts</p><p>3. Now Target -&gt; Sitemap -&gt; Choose the target-&gt;Right Click-&gt; Extensions -&gt; Get All Params (GAP)</p><p>4. Save all the extracted params in a file</p><p>5. You can also gather all the urls using <em>gau</em> , <em>wayback</em> , <em>Katana</em> or any other tool and then extract all the parameters from the extracted urls .</p><p>We have written a very basic script which can extract all the parameters from the urls gathered from various tools :</p><p><a href="https://github.com/302Found1/Param-Extract"><em>Param-Extract</em></a><em> (Yeah lazy script but works also we will update it later)</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/821/0*T_c2gQLAjoCJFokm" /></figure><p>Alternatively you can also use the below one-liner to extract the urls using unfurl tool :</p><blockquote>cat urls | unfurl format %q | cut -d “=” -f1 | sort -u &gt; params.txt</blockquote><p>6. Now merge both the param files and sort -u</p><p>7. Once you have created a custom wordlist with all the params you can easily use the Paraminer burp extension to discover the hidden params .</p><p>8. Once you have identified the hidden parameters you can test for various injection or other bugs based on the case scenarios .</p><p>Happy Hunting !!!!</p><h4>From Infosec Writeups: A lot is coming up in the Infosec every day that it’s hard to keep up with. <a href="https://weekly.infosecwriteups.com/">Join our weekly newsletter</a> to get all the latest Infosec trends in the form of 5 articles, 4 Threads, 3 videos, 2 GitHub Repos and tools, and 1 job alert for FREE!</h4><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4365da5447cf" width="1" height="1" alt=""><hr><p><a href="https://infosecwriteups.com/param-hunting-to-injections-4365da5447cf">Param Hunting to Injections</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[Frida & Objection without Jailbreak! ]]></title>
            <link>https://infosecwriteups.com/frida-objection-without-jailbreak-27a66501bf38?source=rss-690fd279bd24------2</link>
            <guid isPermaLink="false">https://medium.com/p/27a66501bf38</guid>
            <category><![CDATA[bug-bounty]]></category>
            <category><![CDATA[information-security]]></category>
            <category><![CDATA[infosec]]></category>
            <category><![CDATA[cybersecurity]]></category>
            <category><![CDATA[hacking]]></category>
            <dc:creator><![CDATA[TheBountyBox]]></dc:creator>
            <pubDate>Wed, 16 Nov 2022 18:57:59 GMT</pubDate>
            <atom:updated>2023-10-23T18:09:09.865Z</atom:updated>
            <content:encoded><![CDATA[<p>So are you the one who stops security testing if Jailbreak Detection is not bypassed?? No worries, we have got you covered! A method to implement and run Frida Server and Objection without Jailbreaking the device. The best part? Tested on the latest iOS 16.2 Version ;) Let’s do this!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/410/0*0Yti9R_sbP1IWkJK" /></figure><p>Alright! Pre-requisites, All you need is</p><ol><li>A Mac or Maybe VM Image of Mac (A simple guide over here <a href="https://www.wikihow.com/Install-macOS-on-a-Windows-PC">https://www.wikihow.com/Install-macOS-on-a-Windows-PC</a>)</li><li>Provisioning profile (Apple Developer Account): You can create one very easily at <a href="https://developer.apple.com/">https://developer.apple.com/</a></li><li>XCode.</li></ol><p>Step 1: You will require an unencrypted version of the IPA file which is either provided by the Client or the Bug Bounty Program or you can decrypt it using tools such as <a href="https://github.com/KJCracks/Clutch">Clutch</a> or <a href="https://github.com/BishopFox/bfinject">bfinject</a>. Another way to do this is to download the application from 3rd party websites such as <a href="https://www.iphonecake.com/">Iphonecake</a>.</p><p>For this example, I would be downloading a random application from iphonecake.com</p><p>Step 2: Find the valid security Identity for codesigning the IPA file using the command. You can refer to this <a href="https://ioscodesigning.com/generating-code-signing-files/">article</a> to generate codesigning.</p><blockquote>security find-identity -p codesigning -v</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*FX4x-C1YcUbk7rFM9Caylw.png" /></figure><p>Step 3: Patch and Inject Frida Server in the IPA using objection</p><blockquote>objection patchipa — source Application.ipa — codesign-signature</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*81oXNmlTK4RnkTH_dEeWnA.png" /></figure><p>Note: If some dependencies are missing please add them. The method to add them will be shown if the build is failed.</p><p>This step will build a new signed code in the current folder called Application-frida-signed.ipa</p><p>Step 4: Unzip the newly created IPA using the command</p><blockquote>unzip Application-frida-signed.ipa</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*I_vflAV0ANzgYnYljKWotg.png" /></figure><p>A new folder called Payload will be created.</p><p>Step 5: Install the patched IPA to the IOS Device. Ensure your IOS device is connected to the Mac and hit the “Trust” button! You can do this using the following command.</p><blockquote>ios-deploy — bundle Payload/SomeAppName.app -W -d</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ogGjJUljJSrk3BVaGPfvZw.png" /></figure><p>If ios-deploy is not found you can install it using the command:</p><blockquote>sudo npm install -g ios-deploy — unsafe-perm=true — allow-root</blockquote><p>This will install the application on your IOS device and will start the application in paused mode.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*AgFB7r65GMeFANqM26gJlw.png" /></figure><p>To enable and run the application in the resume mode the final step is to run the objection.</p><p>Step 6: Keep the terminal command running and Run objection on a new terminal using the following command</p><blockquote>objection explore</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*BbLA7TF-PeIFu80jBLd7Gw.png" /></figure><p>And this will allow you to bypass SSL pinning and run Frida on a non-jailbroken iOS Device. Now all you have to do is connect your Burp Suite and and capture the requests and Hack it On!!!</p><p>We hope that you loved and enjoyed the article and this will help you in your journey of iOS Pentesting! Stay tuned for more such blogs on iOS Pentesting!</p><p>Happy Hunting!</p><h4>From Infosec Writeups: A lot is coming up in the Infosec every day that it’s hard to keep up with. <a href="https://weekly.infosecwriteups.com/">Join our weekly newsletter</a> to get all the latest Infosec trends in the form of 5 articles, 4 Threads, 3 videos, 2 GitHub Repos and tools, and 1 job alert for FREE!</h4><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=27a66501bf38" width="1" height="1" alt=""><hr><p><a href="https://infosecwriteups.com/frida-objection-without-jailbreak-27a66501bf38">Frida &amp; Objection without Jailbreak! 🔥🔥</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[Cool Recon techniques every hacker misses! Episode 3]]></title>
            <link>https://infosecwriteups.com/cool-recon-techniques-every-hacker-misses-episode-3-3812e7da3425?source=rss-690fd279bd24------2</link>
            <guid isPermaLink="false">https://medium.com/p/3812e7da3425</guid>
            <category><![CDATA[cybersecurity]]></category>
            <category><![CDATA[infosec]]></category>
            <category><![CDATA[penetration-testing]]></category>
            <category><![CDATA[hacking]]></category>
            <category><![CDATA[bug-bounty]]></category>
            <dc:creator><![CDATA[TheBountyBox]]></dc:creator>
            <pubDate>Tue, 08 Nov 2022 18:22:17 GMT</pubDate>
            <atom:updated>2023-10-23T18:10:31.395Z</atom:updated>
            <content:encoded><![CDATA[<p>Welcome to the 3rd Episode of Cool Recon Techniques. We are back with some more cool recon techniques which we think hackers out there usually miss out on! If you haven’t read the first Episode <a href="https://infosecwriteups.com/cool-recon-techniques-every-hacker-misses-1c5e0e294e89">here</a>’s the link! And here is the link to the <a href="https://medium.com/bugbountywriteup/cool-recon-techniques-every-hacker-misses-episode-2-8024e8338756">second</a> Episode</p><p>And Here we Go!!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/480/0*XxcAFj21DVq9DPpn" /></figure><blockquote><strong>Technique 15: Enumerate GitHub Repositories for a particular username</strong></blockquote><p>While doing GitHub Recon, it is very difficult to find the exact organization name and its repositories to find sensitive data. <a href="https://github.com/trickest/enumerepo">enumerepo</a> will help you out to list all the repositories for a valid GitHub account. All you have to do is simply submit account names and see the magic!</p><blockquote><strong>Command:</strong> enumerepo -token-string GITHUB_TOKEN -usernames accounts.txt -o output file</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*871N8lmPkAeNzoukQsSelw.png" /></figure><blockquote><strong>Technique 16: Say a big Hi to Katana</strong></blockquote><p>Woah! Woah! Project Discovery’s new tool is over here! Say Bye to all the different tools such as waybackurls, gau, subjs and hi to <a href="https://github.com/projectdiscovery/katana">Katana</a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*YGRrDK-VFPtYN184bOhpIQ.jpeg" /></figure><p>Katana is an advanced web crawler which crawls all the endpoints. It comes up with various different filters such as JavaScript parsing/crawling, field scopes, crawl scopes, crawling for known files, automatic form fill. It also provides various display options to filter output. And not just this you can infact store field values which can be later useful to build wordlists.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*hvZFPYDbX3QB7gdK7obZBA.png" /></figure><p>The table below describes all features and commands of katana.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*oJKszljbWldzLUTETKScSg.png" /></figure><p><strong>Katana to nuclei — One Liner</strong></p><p>cat subdomains.txt | httpx ––silent &gt;&gt; alive.txt &amp;&amp; cat alive.txt | katana ––silent &gt;&gt; endpoints.txt &amp;&amp; cat endpoints.txt | nuclei -t &lt;YOUR_TEMPLATES&gt;</p><blockquote><strong>Technique 17: Query DNS to get IPs and Subdomains using RapidDNS</strong></blockquote><p>Increase your attack surface by querying DNS to find IP Addresses using <a href="https://rapiddns.io/">RapidDNS</a>. RapidDNS is a DNS query tool with more than 3 billion data and more being added daily.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*_NUIMHn32BU7RD4GnIuL7w.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Z7VTu2FWg7dspIGej-jJyw.png" /></figure><blockquote><strong>Technique 18: Large Scope Application Recon Issues?</strong></blockquote><p>Ever found a large scope domain with huge assets in scope and don&#39;t know how to find the entire information? No worries 3klCon comes to the rescue. <a href="https://github.com/eslam3kl/3klCon">3klCon</a> is an automation Recon tool which works with Large &amp; Medium scopes. It performs more than 20 tasks and gets back all the results in separated files.</p><blockquote><strong>Technique 19: </strong>S3 Bucket Weakness Discovery</blockquote><p>Wanna find S3 buckets from a domain and discover weaknesses in them. Then say hi to <a href="http://github.com/cr0hn/festin">Festin</a>. A tool which finds S3 buckets using various techniques such as crawling, DNS crawling, S3 Response analysis, etc. The best part you do not require any AWS credentials. It also allows to download bucket objects.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*q3hEgltAneeNFGOsmyjWmQ.png" /></figure><blockquote><strong>Technique 20: Wordpress Recon</strong></blockquote><p>Ever came across a Wordpress website and do not know how to start the recon? No worries! <a href="https://github.com/AngraTeam/wprecon">WPRecon</a> is here for you. WPRecon, is a tool for the recognition of vulnerabilities and blackbox information for wordpress.</p><p>Simply add your domain name on <a href="https://wprecon.com/">https://wprecon.com/</a> and gain all the different information.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ZJuZA7e5mxevOFd1uEzKgQ.png" /></figure><p>We hope that these recon techniques might help you to add and update your methodology. Do share your recon methodology in the comments section.</p><p>Happy Hunting!</p><p>From Infosec Writeups: A lot is coming up in the Infosec every day that it’s hard to keep up with. <a href="https://weekly.infosecwriteups.com/">Join our weekly newsletter</a> to get all the latest Infosec trends in the form of 5 articles, 4 Threads, 3 videos, 2 GitHub Repos and tools, and 1 job alert for FREE!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=3812e7da3425" width="1" height="1" alt=""><hr><p><a href="https://infosecwriteups.com/cool-recon-techniques-every-hacker-misses-episode-3-3812e7da3425">Cool Recon techniques every hacker misses! Episode 3🔥🔥</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[Android Pentesting 101 — Part 3]]></title>
            <link>https://infosecwriteups.com/android-pentesting-101-part-3-2bf846b05594?source=rss-690fd279bd24------2</link>
            <guid isPermaLink="false">https://medium.com/p/2bf846b05594</guid>
            <category><![CDATA[pentesting]]></category>
            <category><![CDATA[bug-bounty]]></category>
            <category><![CDATA[cybersecurity]]></category>
            <category><![CDATA[hacking]]></category>
            <category><![CDATA[infosec]]></category>
            <dc:creator><![CDATA[TheBountyBox]]></dc:creator>
            <pubDate>Sun, 30 Oct 2022 10:31:40 GMT</pubDate>
            <atom:updated>2023-10-23T18:10:55.307Z</atom:updated>
            <content:encoded><![CDATA[<h3>Android Pentesting 101 — Part 3</h3><p>Welcome to Part 3 of Android Pentesting. This series is about how you can hack into Android and find vulnerabilities in it using various methods. If you haven’t read parts 1 and 2, I would highly recommend you please read them before jumping to this section. You can find it over <a href="https://medium.com/@302found">here</a>.</p><p>In the third part, the final we aim to cover the Dynamic Analysis of Android Pentesting, along with various tools. Are you ready??</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/480/0*ceacFcCmu_iDQWxt" /></figure><p>So Dynamic Analysis in Android Pentesting is all about playing with the requests and the responses of what the application is sending to the web server. But here is the catch! Two things to do before capturing the request:</p><ol><li>Root Detection Bypass</li><li>SSL Pinning Bypass</li></ol><p>Let’s us talk about them individually.</p><p><strong>Root Detection Bypass: </strong>Rooting is the process of allowing users of the Android mobile operating system to attain privileged control (known as root access) over various Android subsystems. Applications should not be allowed to run on rooted devices. And hence we try out various Root Detection Bypass using <a href="https://github.com/frida">Frida</a> and <a href="https://github.com/sensepost/objection">Objection</a>.</p><p><strong>SSL Pinning Bypass: </strong>SSL Pinning is a technique that most application owners implement so that any request sent by the mobile application is not intercepted. SSL Pinning is considered as the first and the most important step in the security mechanism of an application. But due to improper means, SSL Pinning can usually be bypassed. Again <a href="https://github.com/frida">Frida</a> and <a href="https://github.com/sensepost/objection">Objection</a> are the best tools that will help us over here.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*3sv7Eb55CJRxLfDp" /></figure><p>So how do you start with the Dynamic Analysis? Well, the first step is the need for a Rooted Android Phone. You can easily Root any Android Phone using <a href="https://www.xda-developers.com/how-to-install-magisk/">Magisk</a> (the best and most accurate way) or other methods found <a href="https://www.rootingsteps.com/root-moto-g9-power/">here</a>. Alternatively, you can use Genymotion, which sometimes does not provide accurate results</p><p>Alright, so let’s start by taking a live target, let&#39;s call the application &lt;Redacted&gt;. Okay so &lt;Redacted&gt; has Root Detection implemented which can be seen in the screenshot below.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/406/1*zAMTPmNceVQ_xL969v7G_Q.png" /></figure><p>Now to Bypass, this is very simple:</p><ol><li>Download and install Frida &amp; Objection using <a href="https://infosecwriteups.com/hail-frida-the-universal-ssl-pinning-bypass-for-android-e9e1d733d29">Hail Frida</a>.</li><li>Try connecting Burp Suite and your phone by following this <a href="https://support.portswigger.net/customer/portal/articles/1841101-configuring-an-android-device-to-work-with-burp">article</a></li><li>Start the Frida Server using: adb shell /data/local/tmp/frida-server &amp;</li><li>Open the application and keep the application running in the background.</li><li>Find the Application package name using: frida-ps -Ua</li><li>Now you need to find the right script. This time we are going to run Root Bypass Script which can be found <a href="https://codeshare.frida.re/@dzonerzy/fridantiroot/">here</a>. If this Frida script does not work you can find more online. Other Frida scripts can be found <a href="https://codeshare.frida.re/">here</a>.</li><li>The final step is to hook the script using Frida using the command:</li></ol><pre>frida -U -f com.package.android -l D:\frida\fridascript-root.js --no-paus</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*GO-Xm8BZ7LXFN53YRaKtlg.png" /></figure><p>Alternatively, you can use objection to bypass the Root Detection. That can be quickly done using the following commands:</p><ol><li>objection -g “com.package.android” explore</li><li>android root disable</li><li>android root simulate</li></ol><p>Perfect! Now that we have bypassed the Root Detection, we can move forward. There is still a step left before we can capture the requests which are to bypass SSL pinning.</p><p>Alright, so to bypass the SSL Pinning we will again use Frida and the SSL Pinning Bypass Script which can be found <a href="https://codeshare.frida.re/@pcipolloni/universal-android-ssl-pinning-bypass-with-frida/">here</a>. Uh-Oh! But here is the catch you cannot run 2 Frida scripts simultaneously. But No Problem! Just add the SSL Pinning Bypass Script below Root Detection Bypass Script and re-run Frida and see the magic.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*phanI0RHEE2MXzPlzcPfJQ.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*RjMi5qC_E_X4EfBbs0T2-Q.png" /></figure><p>Dang! Here is how we can capture all the requests! Alternatively, you can use objection to bypass the SSL Pinning. That can be quickly done using the following commands:</p><ol><li>objection -g “com.package.android” explore</li><li>android sslpinning disable</li><li>android sslpinning simulate</li></ol><p>Oh, wait! The application uses the fingerprint as well to authenticate the user. Let’s try to bypass this as well. The script for fingerprint bypass can be found <a href="https://github.com/WithSecureLabs/android-keystore-audit/blob/master/frida-scripts/fingerprint-bypass.js">here</a>. So simply add the fingerprint bypass script below the Root Detection and SSL Pinning Script.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*gEw7HLSFq4kJ1Yptaih2fg.png" /></figure><p>Great! So we were able to bypass the Fingerprint as well! So what next, nothing capture all the requests, and try to play with them as you do while testing a Web Application.</p><p>We have collected and added all the Frida Scripts which we find useful over <a href="https://github.com/302Found1/Awesmoe-Frida-Scripts">here</a>. Please feel free to use them. Besides, we also created a Mind Map which you can use and can be found below.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Ni4ZwqBSbqRTqu4JuJs_Hw.png" /></figure><p>That’s all folks for this article! We hope that you enjoyed the entire series! We will be back with another such series and this time it will be iOS Pentesting, where we will show you’ll the methodology of Dynamic Analysis while performing iOS Pentesting.</p><p>Happy Hunting!</p><h4>From Infosec Writeups: A lot is coming up in the Infosec every day that it’s hard to keep up with. <a href="https://weekly.infosecwriteups.com/">Join our weekly newsletter</a> to get all the latest Infosec trends in the form of 5 articles, 4 Threads, 3 videos, 2 GitHub Repos and tools, and 1 job alert for FREE!</h4><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2bf846b05594" width="1" height="1" alt=""><hr><p><a href="https://infosecwriteups.com/android-pentesting-101-part-3-2bf846b05594">Android Pentesting 101 — Part 3</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[Android Pentesting 101 — Part 2]]></title>
            <link>https://infosecwriteups.com/android-pentesting-101-part-2-419facdf11c1?source=rss-690fd279bd24------2</link>
            <guid isPermaLink="false">https://medium.com/p/419facdf11c1</guid>
            <category><![CDATA[pentesting]]></category>
            <category><![CDATA[android]]></category>
            <category><![CDATA[hacking]]></category>
            <category><![CDATA[cybersecurity]]></category>
            <category><![CDATA[penetration-testing]]></category>
            <dc:creator><![CDATA[TheBountyBox]]></dc:creator>
            <pubDate>Tue, 25 Oct 2022 06:27:36 GMT</pubDate>
            <atom:updated>2023-10-23T18:11:22.448Z</atom:updated>
            <content:encoded><![CDATA[<h3>Android Pentesting 101 — Part 2</h3><p>Welcome to Part 2 of Android Pentesting. This series is about how you can hack into Android and find vulnerabilities in it using various methods. If you haven&#39;t read part 1, I would highly recommend you please read it before jumping to this section. You can find it over <a href="https://infosecwriteups.com/android-pentesting-101-part-1-8e31b8cd8b2b">here</a>.</p><p>In the second part, we aim to cover the Static Analysis of Android Pentesting, along with various tools. So let&#39;s do this !!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/480/0*4UIGpu305LV9LI2L" /></figure><p>So Static Analysis in Android Pentesting is all about reviewing the source code and finding the vulnerabilities, and how can you do that?? The first step is to get the APK file. Well, it’s simple, find an Android Application first and download the APK file on your phone.</p><p>Once you have downloaded the APK, use <a href="https://play.google.com/store/apps/details?id=com.ext.ui&amp;hl=en_IN&amp;gl=US">APK Extractor</a> to extract the APK file and then send it to your PC for further analysis. Simultaneously you can also pull it using ADB. The following are the commands for the same:</p><ol><li>Grab the package name using adb shell pm list packages -f | grep app_name</li><li>Grab the path using the package name obtained above adb shell pm path com.package_name.</li><li>Pull the apk using adb pull /data/app/com.package_name..apk</li></ol><p>Alternatively, you can use <a href="https://github.com/ClaudiuGeorgiu/PlaystoreDownloader">PlaystoreDownloader</a> to download the APK files as well. The next step is to reverse engineer the code. In Part 1 we have already seen how Java Source Code is converted to the APK file, we simply have to reverse the entire procedure so that we get readable files. To perform this:</p><ol><li>Extract the APK file using <a href="https://www.win-rar.com/start.html?&amp;L=0">WinRar</a> or a similar tool. (If not extractable convert the apk file to ZIP first that is MyApp.zip)</li><li>Once extracted, we get the AndroidManifest.xml file and certain DEX Codes. We have to reverse these DEX Codes. This can be easily done using the command d2j-dex2jar -f classes.dex</li><li>The JD-GUI tool can now interpret the jar file and we get to see the source code of the APK file clearly.</li></ol><p>Perfect Now it&#39;s time for all the manual Analysis. In a general case scenario, the following are checked in Static Analysis</p><ol><li>Check if App is Debuggable</li><li>Check if any exported activity is true (If yes exploit it using drozer)</li><li>Check for typographic errors in custom permissions in AndroidManifest.xml file. A similar test case can be found <a href="https://hackerone.com/reports/440749">here</a></li><li>Check for hardcoded API Keys, Comments, Secrets, etc. A similar test case can be found <a href="https://hackerone.com/reports/351555">here</a>.</li><li>Check for exported broadcast behavior.</li></ol><p>Manual testing can sometimes be boring, and hence to speed up the process we have 2 beautiful tools that can help you out:</p><ol><li><a href="https://github.com/MobSF/Mobile-Security-Framework-MobSF">MobSF</a>: It is an automated malware analysis tool that will help you to speed up your process of Static Analysis. It can be easily <a href="https://mobsf.github.io/docs/#/installation">downloaded</a>. Let&#39;s have a quick look at it.</li></ol><p>The first step is to download the APK using various methods as seen above, and then upload the APK to MobSF.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*h7os0pJaWO5PeL7jkaSPnQ.png" /></figure><p>In the screenshot below, you will be able to see about all the Application Details.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*nlaTsfb6yL0aOHHSMp-2xg.png" /></figure><p>The next screen shows about all the activities, services, receivers, providers, etc. You can even view the AndroidManifest.xml file as well and the Source Code and Smali code as well.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*RT7kLk9O9LKO45MWbr7n8Q.png" /></figure><p>You can view all the Security Analysis, Malware Analysis, Code Analysis, File Analysis etc. one by one. A screenshot of the same can be seen below.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Onx45aanhwhmyDOTtSD8Cg.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*op9Z7MK-v2uqS_PfTj9Fqw.png" /></figure><p>You can even print the PDF report for the Static Analysis.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*4AgfFKZcdDB6HZvzthHV3A.png" /></figure><p>2. BeVigil: The world’s first and only security search engine for mobile applications developed by CloudSek. Personally, I love this particular tool more because it&#39;s quite simple to use and you can provide a direct link to the PlayStore URL.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*cX4l6fuovNfEQSMkabbBcg.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*-antUPMLzZaY-1Yq49OCLQ.png" /></figure><p>Over here you can view the security score, all the total detected issues, and their description. Let’s take a random example:</p><ol><li>If you can see this particular application accepts all SSL certificates, which means that in Dynamic analysis, we do not have to bypass SSL Pinning, and thus we can try to report this vulnerability.</li><li>On further analysis we found that some Google API keys were also leaked.</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*xKr_4F2BTXQZp_7dHRzPiQ.png" /></figure><p>3. We were also able to see that Non parameterized queries were also written which allows an attacker to perform SQL Injection</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*KEkJNC2rQ_vFfjknv060Ww.png" /></figure><p>And so on all of the static files can be analyzed.</p><p>That’s all folks for Part Two! We hope that you enjoyed this article! We will be back with another part soon, where we will show you’ll the methodology of Dynamic Analysis while performing Android Pentesting.</p><p>Happy Hunting!</p><p>From Infosec Writeups: A lot is coming up in the Infosec every day that it’s hard to keep up with. <a href="https://weekly.infosecwriteups.com/">Join our weekly newsletter</a> to get all the latest Infosec trends in the form of 5 articles, 4 Threads, 3 videos, 2 GitHub Repos and tools, and 1 job alert for FREE!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=419facdf11c1" width="1" height="1" alt=""><hr><p><a href="https://infosecwriteups.com/android-pentesting-101-part-2-419facdf11c1">Android Pentesting 101 — Part 2</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[Android Pentesting 101 — Part 1]]></title>
            <link>https://infosecwriteups.com/android-pentesting-101-part-1-8e31b8cd8b2b?source=rss-690fd279bd24------2</link>
            <guid isPermaLink="false">https://medium.com/p/8e31b8cd8b2b</guid>
            <category><![CDATA[android]]></category>
            <category><![CDATA[cybersecurity]]></category>
            <category><![CDATA[android-app-development]]></category>
            <category><![CDATA[infosec]]></category>
            <category><![CDATA[bug-bounty]]></category>
            <dc:creator><![CDATA[TheBountyBox]]></dc:creator>
            <pubDate>Sat, 22 Oct 2022 08:57:35 GMT</pubDate>
            <atom:updated>2023-10-23T18:11:59.907Z</atom:updated>
            <content:encoded><![CDATA[<h3>Android Pentesting 101 — Part 1</h3><p>Welcome to this new series of Android Pentesting. This series is about how you can hack into Android and find vulnerabilities in it using various methods. In this series, we aim to achieve all the vulnerabilities which you can find along with the methodology. In the first part, we aim to cover a basic description of how android pentesting is done and all the tools required to perform it. So, Gear Up and load your arsenals!!!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/480/0*Qp-Pn82y2doe4I8U" /></figure><p>Coming to the very basics, Mobile applications are generally of 3 types:</p><ol><li>Native Applications: These are mobile applications developed for a particular Operating System (OS) or a Platform. They usually need an emulator and web-based attacks (such as XSS) are not possible on this kind of application.</li><li>Web-Based Applications: These are browser-based applications and generally use <a href="https://developer.android.com/reference/android/webkit/WebView">WebView</a> (a system component in Android) to display web pages on Android Operating System. They do not need an emulator and web-based attacks (such as XSS) are possible.</li><li>Hybrid Applications: As the name suggests these are the combination of the above two applications and usually require an emulator for testing. These are the applications that you will find in the real world.</li></ol><p>Now, before we learn about android pentesting, it is very important to know how <strong>Android Architecture</strong> works. I will be giving a short description of each component, but if you want to dig in more you can learn it from <a href="https://www.geeksforgeeks.org/android-architecture/">here</a>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/733/0*jn1exwz9CvO_shdE.jpg" /></figure><ol><li>Applications: The topmost layer of the architecture where all 3rd Party Applications are installed. Examples include Camera, WhatsApp, Google, etc.</li><li>Application Framework: This is the layer that provides various classes for the creation of the Android Application. Examples Activity Manager, Content Provider, etc.</li><li>Android Runtime: The most important layer consists of the Dalvik VM. Dalvik Virtual Machine (DVM) is similar to JVM which enables the applications to run and provides various platform libraries such as SSL, SQLite, Media, etc.</li><li>Linux Kernel: This is the heart of the android architecture and provides features such as security, memory management, process management, etc.</li></ol><p>Now let&#39;s quickly have a sneak peek at various <a href="https://www.tutorialspoint.com/android/android_application_components.htm"><strong>Android Components</strong></a>.</p><ol><li>Activity: These are java classes that have some predefined functions which are triggered at different app states. There are in total four app states: Active, Pause, Stop and Destroy. The different methods that can be invoked are onCreate(), onStart(), onResume(), onPause(), onStop(), onDestroy(). Think of a scenario when sensitive data is being transmitted and the onPause() method appears and after n seconds onResume() method is called, how would the application handle the sensitive data then? This could be a good check case.</li><li>Services: These are operations that happen in the background and do not have a UI. Services are critical and should always be checked as attackers usually plant malware here. An example scenario would be a calculator application asking for call logs permission.</li><li>Intents: These are bound to different components in an application and are used to perform different kinds of actions and invoke activities in different applications. Intent filters are used to protect activities.</li><li>Content Providers: Acts as a middle layer to access data from various sources.</li><li>Broadcast Receivers: These receive broadcast messages from various events which could be from one or many applications. For example, when an application receives an SMS it sends a broadcast message to every other application.</li></ol><p>Let’s now talk about the <strong>Android File System. </strong>The following are the folders found inside the file hierarchy:</p><ol><li>/boot: Bootable files consisting of the Android kernel and ramdisk</li><li>/system: The entire Android OS is stored inside this folder. It also consists of the pre-installed system applications which are stored inside /system/app</li><li>/recovery: This folder is designed for backup and is considered as an alternate boot option.</li><li>/cache: This folder stores frequently accessed app data and components</li><li>/misc: Contains miscellaneous system settings</li><li>/sdcard: This folder is the space that is available to users to store their files and data.</li><li>/data: This particular folder consists of all user data.</li></ol><ul><li>/data/data: Consists of all applications data installed by the user</li><li>/data/app: Consists of all APKs of the application installed by the user</li><li>/data/system: Consists of files such as gesture.key, password.key</li><li>/data/local/tmp: Writeable temporary</li></ul><p>Some certain important files and folders are generally created while the application&#39;s creation. In our android pentesting, having a look at these files and folders is critical. The different important files and folders are as follows:</p><ol><li>AndroidManifest.xml: has the structure and metadata of the application. Usually, all permissions, API keys, etc. are stored inside this particular file.</li><li>Java: This particular folder contains the Java source code files.</li><li>drawable: All images, videos, gifs, etc. are stored inside this particular folder.</li><li>layout: A layout defines the visual structure for a user interface, such as the UI for an Android application.</li><li>mipmap: The image Asset folder that usually contains different icons.</li><li>colors.xml: Color resource file of the Android application.</li><li>strings.xml: String resource file of the Android application.</li><li>styles.xml: Styles resource file of the Android application.</li><li>build.gradle: This particular file is used to add various dependencies. This file also has the SDKVersion number and other important details.</li></ol><p>So now let&#39;s talk about the final topic of the Android architecture the Android Data Storage Model. Android stores data in 5ways:</p><ol><li>Shared Preferences: Store private data in key-value pairs on the device.</li><li>Internal Storage: Store private data on the device&#39;s memory.</li><li>External Storage: Store public data on the shared external storage.</li><li>SQLite Databases: Stored structured data on private databases.</li><li>Network Connection: Store data on the web with your Network Server.</li></ol><p>We all know that once the Android application is created a .apk file is generated. Ever wondered what exactly is this .apk file?? Well, a .apk file is nothing but a zip file of the source code which contains all the resources, dex codes, assets, manifest files, etc. The following diagram shows how a Java Source Code is converted to an APK file.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/761/1*U5Fmy2D7E5kWxb_vSGv5rQ.png" /></figure><p>Perfect! Now since we have learned the entire android architecture, let’s learn about how the actual pentesting methodology works!! There are two types of analysis which is usually done while performing Android pentesting.</p><ol><li>Static Analysis: This means viewing the source code of the APK and finding out vulnerabilities by reviewing the APK. This is kinda similar to Source Code Review. We usually look out for different Intent functions, Sources, and Sinks, Dangerous Permissions, Hardcoded API Keys, etc. This was the reason we went into the details of the Android Architecture. (I know it is kinda long and boring but much needed as well :P)</li></ol><p>2. Dynamic Analysis: Dynamic Analysis is all about playing with requests and responses. But here is a catch, like normal Web Pentesting, in Android (as well as iOS) the requests and responses are not caught directly. We first need to bypass Root Detection and then bypass SSL Pinning. We will be learning more about this in the upcoming articles.</p><p>Now its time to pick up your weapons ;) The following is a curated list of all the tools which are required to perform both Static as well as Dynamic Analysis.</p><ol><li>An Android Device: Obviously, you require an Android Device to perform the testing. It can be a real android device or an emulator as well. If it is a real Android device, make sure that the Android device is rooted. Rooting can easily be performed using a tool called <a href="https://magiskmanager.com/">Magisk</a>. For an emulator, you can use <a href="https://www.genymotion.com/">Genymotion</a>. Sometimes emulators do lag and having a real android device is much more beneficial.</li><li><a href="https://dl.google.com/android/repository/platform-tools-latest-windows.zip">Android Debug Bridge (ADB)</a>: This is used to communicate with the device and perform debug operations on the device.</li><li><a href="https://github.com/pxb1988/dex2jar">Dex2jar</a>: Dex2jar is a wonderful tool that helps you to convert the dex code to jar format so that reading the source code is easier.</li><li><a href="http://java-decompiler.github.io/">JD-GUI </a>: JD-GUI is a tool that allows you to view the java source code of an APK file directly.</li><li><a href="https://mobsf.github.io/docs/#/installation">MobSF</a>: MobSF is an all-in-one security tool that helps you to perform automatic static analysis and makes your work a lot simpler.</li><li><a href="https://github.com/WithSecureLabs/drozer">drozer</a>: The Metasploit Framework(MSF)for Android security which allows you to find vulnerabilities and exploit them as well.</li><li><a href="https://github.com/frida">Frida</a>: A tool that is going to help bypass a lot of things ;)</li><li><a href="https://github.com/sensepost/objection">Objection</a>: Another tool that will help us bypass a lot of things ;)</li><li><a href="https://github.com/fornwall/apksigner">apksigner</a>: Used to sign modified APKs.</li><li><a href="https://portswigger.net/burp">Burp Suite</a>: Oh! Don’t forget the GOD!!</li></ol><p>That&#39;s all folks for Part One! We hope that you enjoyed this article! We will be back with another part soon, where we will show you&#39;ll the methodology of Static Analysis while performing Android Pentesting.</p><p>Happy Hunting!</p><p>From Infosec Writeups: A lot is coming up in the Infosec every day that it’s hard to keep up with. <a href="https://weekly.infosecwriteups.com/">Join our weekly newsletter</a> to get all the latest Infosec trends in the form of 5 articles, 4 Threads, 3 videos, 2 GitHub Repos and tools, and 1 job alert for FREE!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8e31b8cd8b2b" width="1" height="1" alt=""><hr><p><a href="https://infosecwriteups.com/android-pentesting-101-part-1-8e31b8cd8b2b">Android Pentesting 101 — Part 1</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[Bugcrowd — Tale of multiple misconfigurations!! ❌]]></title>
            <link>https://infosecwriteups.com/bugcrowd-tale-of-multiple-misconfigurations-cb5b98f09302?source=rss-690fd279bd24------2</link>
            <guid isPermaLink="false">https://medium.com/p/cb5b98f09302</guid>
            <category><![CDATA[bug-bounty]]></category>
            <category><![CDATA[tips]]></category>
            <category><![CDATA[infosec]]></category>
            <category><![CDATA[hacking]]></category>
            <category><![CDATA[cybersecurity]]></category>
            <dc:creator><![CDATA[TheBountyBox]]></dc:creator>
            <pubDate>Tue, 04 Oct 2022 09:23:02 GMT</pubDate>
            <atom:updated>2023-10-23T18:12:11.002Z</atom:updated>
            <content:encoded><![CDATA[<h3>Bugcrowd — Tale of multiple misconfigurations!! ❌</h3><p>Welcome to this new article. This article is a story about misconfigurations found on a domain. Since it is a private program let’s call it redacted.com So do you wanna know how??</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/360/0*wTIs9SSLna9SDidl" /></figure><p>The scope of the application was huge, but starting off with the normal subdomain scan and all of those fancy recon I decided to start testing the main application. The web application was a simple E-commerce website with a lot of deals to grab on! ;)</p><p>I usually try to check all sorts of business logic vulnerabilities on such websites, but this time my eyes captured the authentication mechanism.</p><p>So the first thing was to create an account! But what came to my notice was the OAuth mechanism. Perfect it was time to check for various OAuth vulnerabilities!!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/288/1*-Wh8vHB5G3cM6_fRfHudcg.png" /><figcaption>Email SignUp</figcaption></figure><p>So I used the beautiful methodology from <a href="https://pentestbook.six2dez.com/enumeration/webservices/oauth#bugs">Pentest Book</a> and my 2nd dummy account and started checking for OAuth vulnerabilities, but was not able to find any!</p><p>But Hey!! The basic vulnerability check was forgotten. I instantly tried to create an OAuth account using my 1st dummy account and Boom, I was able to create 2 accounts using the same email ID.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/202/1*GFcPSNAW0-uNY1Ak8o9Mhw.png" /><figcaption>Account Created using Email Signup</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/400/1*4_nsYvtnYWTz7GVfIKwd8w.png" /><figcaption>OAUTH login using same email</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/225/1*6zjDQW1EYxWqByNWv6Cbyw.png" /><figcaption>Misconfigured Oauth to Pre Account Takeover</figcaption></figure><p>To summarize the entire procedure the following steps were performed:</p><ol><li>Visit the website and click on Sign Up.</li><li>Create an account using an unregistered victim email (say <a href="/service/mailto:test@gmail.com">test@gmail.com</a>)</li><li>Create another account using the OAuth mechanism and using the same OAuth account.</li></ol><p><strong>Impact:</strong><br>The account created using email and password should get invalidated but it does not which means the attacker can still log in using the credentials he used while creating the account using email leading to pre-account takeover.</p><blockquote><strong><em>Perfect! I got one, let&#39;s hunt for more! This time my eyes caught the forget password functionality.</em></strong></blockquote><p><strong><em>The password reset mechanism was as follows:</em></strong></p><ol><li>The user enters his email.</li><li>A 6-digit OTP is generated and sent to the email of the user</li><li>The user sets a new password.</li></ol><p>Great, let&#39;s try for Authentication Bypass and check if we are able to change the victim’s password. So I entered my email and requested an OTP, entered the wrong OTP, and captured the response and tried for response manipulation but no luck.</p><p>But my eye caught that the application was using ajax to perform password reset .</p><p><strong>AJAX</strong> <strong>allows web pages to be updated asynchronously by exchanging small amounts of data with the server behind the scenes.</strong></p><p>So here’s what I did :</p><ol><li>Go to Sign in page and click on forgot password</li><li>Enter attackers email (i.e my email say attacker@gmail.com )</li><li>Now enter the correct OTP received on attacker@gmail.com and Capture the Response and save it .</li><li>You will be redirected to set new password page but DONT SET THE PASSWORD instead Again go to Sign in page and click on forgot password</li><li>Enter victims email i.e. victim@gmail.com ( in our case it was aadesh004@protonmail.com )</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*OLFtvmrioYcikz42oB7B-Q.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/291/1*0i-SVEDQq4VqQD1FsJHsbg.png" /><figcaption>Enter Victim Email</figcaption></figure><p>6. Enter random OTP i.e. 000000 and Intercept the request using burp and Do intercept &gt; Response to this request</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/282/1*uQNxftunUHXLLJKdf-xrmw.png" /><figcaption>Enter Random OTP</figcaption></figure><p>7. IN THE RESPONSE MANIPULATE THE RESPONSE TO :{“successTextKey”:”success”,”errors”:null}</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*G147LIqTHdCgq9pSq0OpSw.png" /><figcaption>Generated Response</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*8MvNlurE7k75r73d6adqHg.png" /><figcaption>Response Manipulation</figcaption></figure><p>8. Forward the request and You will be redirected to Set new password . This time Set the password and boom ACCOUNT TAKEOVER .</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/285/1*OErIV6wAkrc7hwEEwwLcbQ.png" /><figcaption>Set New Password</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1007/1*IutgPWVNspBCj5-4NxyHiA.png" /><figcaption>Account Takeover</figcaption></figure><p>We hope that you enjoyed this article! Do let us know your stories about misconfigurations!</p><p>Happy Hunting!</p><h4>From Infosec Writeups: A lot is coming up in the Infosec every day that it’s hard to keep up with. <a href="https://weekly.infosecwriteups.com/">Join our weekly newsletter</a> to get all the latest Infosec trends in the form of 5 articles, 4 Threads, 3 videos, 2 GitHub Repos and tools, and 1 job alert for FREE!</h4><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=cb5b98f09302" width="1" height="1" alt=""><hr><p><a href="https://infosecwriteups.com/bugcrowd-tale-of-multiple-misconfigurations-cb5b98f09302">Bugcrowd — Tale of multiple misconfigurations!! ❌</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[Cool Recon techniques every hacker misses! Episode 2]]></title>
            <link>https://infosecwriteups.com/cool-recon-techniques-every-hacker-misses-episode-2-8024e8338756?source=rss-690fd279bd24------2</link>
            <guid isPermaLink="false">https://medium.com/p/8024e8338756</guid>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[bug-bounty]]></category>
            <category><![CDATA[infosec]]></category>
            <category><![CDATA[hacking]]></category>
            <category><![CDATA[cybersecurity]]></category>
            <dc:creator><![CDATA[TheBountyBox]]></dc:creator>
            <pubDate>Sun, 18 Sep 2022 17:00:04 GMT</pubDate>
            <atom:updated>2023-10-23T18:12:22.852Z</atom:updated>
            <content:encoded><![CDATA[<p>Welcome to the 2nd Episode of Cool Recon Techniques. We are back with some more cool recon techniques which we think hackers out there usually miss out on! If you haven’t read the first Episode <a href="https://infosecwriteups.com/cool-recon-techniques-every-hacker-misses-1c5e0e294e89">here</a>’s the link!</p><p>So here we go!!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/500/0*SS_YQzdwctohfMYc" /></figure><blockquote><strong>Technique 9: Effective Google Dorking</strong></blockquote><p>All of us do perform Google Dorking to find sensitive secrets from Google. But here is one of the effective methods which is going to reduce your manual work. A beautiful tool created by Pentest Tools called as <a href="https://pentest-tools.com/information-gathering/google-hacking">Google-Hacking</a> will help us over here.</p><p>Just provide the target name and choose what you are searching for and it creates Google Dorks for you.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*5FbeHP4ayx0Dp-uDyqKIsw.gif" /></figure><p>You can modify these dorks to create and get something much more interesting and sensitive. For example : <strong><em>site: target.com ext:txt</em></strong> got us access to some internal mails of the organization.</p><p>The above tool has only 18 dorks so in order to perform a better recon you can use another great tool i.e. <a href="https://github.com/opsdisk/pagodo">Pagodo</a></p><p>Pagodo has a large number of dorks and also you can add a list of your customized dorks :</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*T4wV-0QvtbXznE-N5NwQuA.png" /></figure><p>Tip: Try dorking on different search engines like bing. At times bing dorking will give productive results for example “site:firebaseio.com” will give better O/P via bing Dorking</p><blockquote><strong>Technique 10: Virtual Host Scanning</strong></blockquote><p>Virtual Hosts are basically a single machine that acts like multiple systems hosting more than one domain. So for example think of a Bank website that has a single IP address 200.12.45.34 hosting 2 subdomains subdomain1.bank.com and subdomain2.bank.com.</p><p>Enumerating such virtual hosts can increase the attack surface area and help to find hidden endpoints. This can be easily done using the beautiful tool called as <a href="https://github.com/dariusztytko/vhosts-sieve">Vhosts-Sieve</a>.</p><p>The steps are as follows:</p><p>Step 1: Find all the subdomains using various tools (Example: <a href="https://github.com/projectdiscovery/subfinder">subfinder</a>)</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*H9OuR1RdcWy4qDNg7YH4ng.png" /></figure><p>Step 2: Find VirtualHosts for the subdomains using the command:</p><p><strong>python3 vhosts-sieve.py -d subdomain.txt -o vhosts.txt</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Z6fiUn00KnpCRGzx8iE3Zg.png" /></figure><blockquote><strong>Technique 11: Effective JavaScript Analysis</strong></blockquote><p>We all know the entire web application’s functionality is built on JavaScript. An effective JavaScript analysis can help you find and discover hidden contents which are not available. There are a lot of tools that help you to do this. You can also create your own regex pattern and grep them from the JS Files.</p><p>You can grab JS Files first by using the tool called as <a href="https://github.com/lc/subjs">subjs</a> using the below command</p><p><strong>cat urls.txt | gau | subjs</strong></p><p><strong>cat urls.txt | waybackurls | subjs</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/983/1*YXVAWn35DOXGTqJKDnUlmg.png" /></figure><p>Once you collect all the JS files you can use <a href="https://github.com/GerbenJavado/LinkFinder">LinkFinder</a> to analyze them.</p><p>There is also a famous extension to perform JS Analysis — Burp JS Miner . You can read more about it <a href="https://portswigger.net/bappstore/0ab7a94d8e11449daaf0fb387431225b">here</a>.</p><p>Another Great Extension to scan JS files is chrome extension <a href="https://chrome.google.com/webstore/detail/trufflehog/bafhdnhjnlcdbjcdcnafhdcphhnfnhjc">TruffleHog</a>. TruffleHog looks for API keys , secrets and credentials on websites as you visit the websites, and alerts you if anything sensitive is found. It scans the webpage as well as the JS files.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*EW_HX0GBOMMJdQ9jzfCJIA.gif" /></figure><blockquote><strong>Technique 12: Effective Cloud Checkers</strong></blockquote><p>Each and every company might use some or the other cloud services either for internal use (intranet) or for external use. Collecting these data and finding hidden endpoints is the goal over here. <a href="https://github.com/initstring/cloud_enum">cloud_enum</a> is an amazing service that helps to find all of these endpoints along with storage URLs. It tries to perform unauthenticated BlackBox testing on the hidden endpoint.</p><p>The command for the same is as follows:</p><p><strong>python3 cloud_enum.py -k uber.com</strong></p><p>You can add multiple keywords by appending the <em>-k</em> flag to increase the chances of hitting more services.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*knekMVTlPC0Y13zABKNCUw.png" /></figure><blockquote><strong>Technique 13: Finding Admin Panels using URLHunter</strong></blockquote><p>Ever imagined how simpler life would be if we got all of the Admin Panels at once? There’s where <a href="https://github.com/utkusen/urlhunter">URLHunter</a> helps you out to do so. URLHunter is an amazing service that helps you find all the hidden endpoints on basis of keywords that you specify. And here is the catch, give the keyword something like admin and allow URLHunter to find you all the hidden admin dashboards.</p><p>The command for the following would be:</p><p><strong>urlhunter -keywords uber.com,admin -date latest -o output.txt</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*twgyZyVI1V6EeQIs0sosXw.png" /></figure><blockquote><strong>Technique 14: Finding Uncommon Subdomains using AnalyticsRelationships</strong></blockquote><p>We found this very interesting and uncommon subdomain enumeration technique using this tool called as <a href="https://github.com/Josue87/AnalyticsRelationships">AnalyticsRelationships</a>. This tool basically checks out for domains/subdomains by looking at Google Analytics IDs from a URL. Google Analytics’ tracking code (or ID) is a unique identifier that allows Google Analytics to collect data when inserted into a website.</p><p>The command is pretty simple:</p><p><strong>python3 analyticsrelationships.py -u </strong><a href="https://www.uber.com/"><strong>https://www.domain.com</strong></a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*fhXMfcsrfWp4uvsLO8hNug.png" /></figure><p>We hope that these recon techniques might help you to add and update your methodology. Do share your recon methodology in the comments section.</p><p>Happy Hunting!</p><h4>From Infosec Writeups: A lot is coming up in the Infosec every day that it’s hard to keep up with. <a href="https://weekly.infosecwriteups.com/">Join our weekly newsletter</a> to get all the latest Infosec trends in the form of 5 articles, 4 Threads, 3 videos, 2 Github Repos and tools, and 1 job alert for FREE!</h4><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8024e8338756" width="1" height="1" alt=""><hr><p><a href="https://infosecwriteups.com/cool-recon-techniques-every-hacker-misses-episode-2-8024e8338756">Cool Recon techniques every hacker misses! Episode 2🔥🔥</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[Mass Hunting CVE’s Part-1]]></title>
            <link>https://infosecwriteups.com/mass-hunting-cves-part-1-1e162ba6028b?source=rss-690fd279bd24------2</link>
            <guid isPermaLink="false">https://medium.com/p/1e162ba6028b</guid>
            <category><![CDATA[automation]]></category>
            <category><![CDATA[infosec]]></category>
            <category><![CDATA[security]]></category>
            <category><![CDATA[cybersecurity]]></category>
            <category><![CDATA[technology]]></category>
            <dc:creator><![CDATA[TheBountyBox]]></dc:creator>
            <pubDate>Wed, 31 Aug 2022 16:03:22 GMT</pubDate>
            <atom:updated>2023-10-23T18:12:39.403Z</atom:updated>
            <content:encoded><![CDATA[<p>CVE, short for Common Vulnerabilities and Exposures, is a list of publicly disclosed computer security flaws. A CVE number uniquely identifies one vulnerability from the list.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/400/0*DqqZXU16fKbTWIpN" /></figure><p>The first step is to find a CVE which you wanna hunt on! We will be taking an example of <a href="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-37042">CVE-2022–37042</a> . The next step is to find some shodan/fofa dorks using which we can find multiple IP’s vulnerable to this particular CVE. You can create your own Dorks, or Google it up. A lot of researchers do post dorks for the same. In our case it is going to be:</p><blockquote><strong>Shodan-query</strong> : <strong>http.favicon.hash:”1624375939&quot; 200</strong></blockquote><blockquote><strong>fofa-query : app=”zimbra-邮件系统”</strong></blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*g3ZemkVkoWR4oaANUuWv8A.png" /><figcaption>79K Results Found from Shodan</figcaption></figure><p>The next step is to pass this dork to <a href="https://github.com/projectdiscovery/uncover">uncover</a> to get a list of all the domains.</p><blockquote><strong>Command: cat dorks.txt| uncover | tee -a final.txt</strong></blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*1HETYA8vubG34Dpq0xDe2g.jpeg" /></figure><p>Now while checking how many IP’s do we have we found the following result :</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*oU4f5yNl5ZmbKU-Y6uubyA.jpeg" /></figure><p>We have only 200 results from uncover whereas we found almost 79k IP’s from shodan .This is because of the Shodan Api limit.</p><p>So to increase our scope we thought of modifying our dork by adding more filtering to extract more IP’s from shodan via uncover . Also you can add multiple shodan API keys in uncover’s config file .</p><p>Modified dork using country parameter :</p><blockquote><strong>http.favicon.hash:”1624375939&quot; country:”US”</strong></blockquote><p>Now we will create a small list of this dorks :</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*u6RPSjmiDa7AHCPwo6WlMg.png" /><figcaption>Note : You can add more dorks for more results</figcaption></figure><p>Now we will pass this list of dorks to uncover :</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*4F5XYwHwK8Arrp7AX9Oymg.png" /></figure><p>Lets see how many IP’s do we have now :</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*NyXaq3nohePf3QY8MNYYng.jpeg" /></figure><p>So finally we have more IP’s now .</p><p>You can create your own dorks with different parameters to obtain more results from shodan using this technique and do share with us in the comments section.</p><p>Next, pass the list of IP’s to httpx to find the ones which are up and running. And then supply it to nuclei with the template name to find the ones which are valid.</p><blockquote><strong>Command: cat fin.txt | httpx — silent | nuclei -t ../nuclei-templates/cves/2022/CVE-2022–1388.yaml</strong></blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*UXicUOiKnup-wV85HPrTmw.jpeg" /></figure><p>The entire process can be converted with this one liner script:</p><blockquote><strong><em>Command: cat dorks.txt| uncover — silent | httpx — silent | nuclei -t ../nuclei-templates/cves</em></strong></blockquote><p>We hope that this technique might help you to mass hunt CVE’s and find a lot of Vulnerable domains .</p><p>Happy Hunting!</p><p>Also Follow us and Stayed tuned for Part-2 , will be sharing some more cool &amp; interesting methodology for Mass Hunting .</p><p><em>From Infosec Writeups: A lot is coming up in the Infosec every day that it’s hard to keep up with. </em><a href="https://weekly.infosecwriteups.com/"><strong><em>Join our weekly newsletter</em></strong></a><em> to get all the latest Infosec trends in the form of 5 articles, 4 Threads, 3 videos, 2 Github Repos and tools, and 1 job alert for FREE!</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1e162ba6028b" width="1" height="1" alt=""><hr><p><a href="https://infosecwriteups.com/mass-hunting-cves-part-1-1e162ba6028b">Mass Hunting CVE’s Part-1👀🔥</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[Cool Recon techniques every hacker misses! ]]></title>
            <link>https://infosecwriteups.com/cool-recon-techniques-every-hacker-misses-1c5e0e294e89?source=rss-690fd279bd24------2</link>
            <guid isPermaLink="false">https://medium.com/p/1c5e0e294e89</guid>
            <category><![CDATA[tricks]]></category>
            <category><![CDATA[bug-bounty-writeup]]></category>
            <category><![CDATA[vapt]]></category>
            <category><![CDATA[bug-bounty]]></category>
            <category><![CDATA[recon]]></category>
            <dc:creator><![CDATA[TheBountyBox]]></dc:creator>
            <pubDate>Tue, 23 Aug 2022 06:05:13 GMT</pubDate>
            <atom:updated>2023-10-23T18:12:57.599Z</atom:updated>
            <content:encoded><![CDATA[<p>Welcome to this article! This article is about some cool recon techniques every hacker misses! Tighten your belts as we walk you through these beautiful techniques.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/500/0*OmXGNAzZIlDg5GmV" /></figure><blockquote><strong><em>Technique 1: Active subdomain enumeration</em></strong></blockquote><p>A very common technique but a lot of researchers rely on passive subdomain enumeration rather than active subdomain enumeration. Lets talk about active subdomain enumeration:</p><p>There are 2 ways you can perform using active subdomain enumeration</p><p><strong><em>a. Bruteforcing subdomains using wordlist:</em></strong> In this technique we use a DNS wordlist to bruteforce a particular subdomain. This can easily be done using <a href="https://github.com/ffuf/ffuf">FFuF</a> and <a href="https://wordlists-cdn.assetnote.io/data/manual/best-dns-wordlist.txt">Best DNS Wordlist</a>.</p><p><strong><em>Command: ffuf -u “</em></strong><a href="https://fuzz.target.com/"><strong><em>https://FUZZ.target.com</em></strong></a><strong><em>&quot; -w &lt;path_to_wordlist&gt; -mc 200,301,302,403</em></strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*6dHXrt4y2JSwyUbn2UufIQ.png" /></figure><p><strong><em>b. Permutation Bruteforce:</em></strong> In this technique we create a new resolved subdomain list from already known subdomains/domains by using permutation, mutation, and alteration with a wordlist. This can easily be done using <a href="https://github.com/infosec-au/altdns">altdns</a></p><p><strong><em>Command: altdns -i hackerone.txt -o data_output -r -s final.txt -w words.txt</em></strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ODlm5p2KqrqCA4g147K2_w.png" /></figure><blockquote><strong><em>Technique 2: Favicon Hashes</em></strong></blockquote><p>Favicons are icons that serve as branding to your website. Each Favicon has some unique hash values which can be used to gather domains with the same hash function. Favicon hashes are simple to calculate. <a href="https://github.com/devanshbatham/FavFreak">FavFreak</a> is one of the best tools which does this work for us.</p><p><strong><em>Command: cat urls.txt | python3 favfreak.py</em></strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*aBJDQe3DTUiMYiHlDqsmHA.png" /></figure><p>Once the hash is calculated, you can use the same on internet search engines such as <a href="https://www.shodan.io/dashboard">shodan</a> to get the mass websites.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*WXdimyHXCrOkWW_YtDTDOQ.png" /></figure><p>You can read more about FavFreak <a href="https://medium.com/@Asm0d3us/weaponizing-favicon-ico-for-bugbounties-osint-and-what-not-ace3c214e139">here</a></p><blockquote><strong><em>Technique 3: Nrich</em></strong></blockquote><p>A brilliant command line tool, <a href="https://gitlab.com/shodan-public/nrich">Nrich</a>, can be used to analyze IPs in a file for CVEs and open ports and vulnerabilities.</p><p>(NOTE : Nrich only accepts IP address as input and not domain names . Hence the problem of finding IP addresses of hostnames can be easily solved using the tool called as <a href="https://github.com/projectdiscovery/dnsx">dnsx</a>.)</p><p><strong><em>Command: cat subdomains.txt | dnsx -a -resp-only | nrich -</em></strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*EbZJzv09ThHlHe8hU8EQUA.png" /></figure><blockquote><strong><em>Technique 4: Choosing the right target</em></strong></blockquote><p>Assume you have a medium scope application with a lot of subdomains. It is challenging to choose a subdomain and start hunting on this. No worries we have got you covered. You can use the <a href="https://github.com/1ndianl33t/Gf-Patterns/blob/master/interestingsubs.json">interestingsubs</a> <a href="https://github.com/tomnomnom/gf">gf</a> pattern list to find interesting subdomains you can hunt upon.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*TsN_DOGqFOX-CYv7G-Sbjw.png" /></figure><p><strong><em>Command: cat urls.txt | gf interestingsubs</em></strong></p><blockquote><strong><em>Technique 5: Reverse Whoislookup</em></strong></blockquote><p>This test will return WHOIS registration results for a DOMAIN name which can be used to gather all assets belonging to an organization.</p><p><strong><em>Steps :</em></strong></p><ol><li>Perform <a href="https://www.whois.com/">whoislookup</a> on target domain and look for Tech Email.</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Dz43T4JUM49M4vdpgSlCYw.png" /><figcaption>whoislookup</figcaption></figure><p>2. Visit <a href="http://drs.whoisxmlapi.com/">drs.whoisxmlapi.com</a> and Signup/Login (Initially you will get 500 free credits )</p><p>Now Search with the Tech Email to discover all the assets belonging to target organization</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*bVYAtg61mEC2Hg_oO1cevA.jpeg" /><figcaption>All domains via whoislookup</figcaption></figure><p>You can also Export all the above results using a Export CSV option.</p><blockquote><strong><em>Technique 6: Uncover</em></strong></blockquote><p><a href="https://github.com/projectdiscovery/uncover">Uncover</a> is a beautiful tool developed by the team <a href="https://projectdiscovery.io/">Projectdisovery</a>. Uncover allows you to quickly discover exposed hosts on the internet. It finds hosts using shodan, censys and fofa. All you need is API Keys to be configured.</p><p>So what can be done?? Find subdomains and give them to nuclei to automate vulns, Find exposed panels, Mass hunt CVEs, and Find services. Basically, automate everything related to internet search engines.</p><p>To use this effectively, create a dorks list as shown in the below image and feed it to uncover.</p><p><strong><em>Command: cat dorks.txt | uncover</em></strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*pZPEz5xCo0WeLMqOPpKUdQ.png" /></figure><blockquote><strong><em>Technique 7: Finding hidden paths using meg</em></strong></blockquote><p>Hidden paths or Directory bruteforcing is an important recon technique. <a href="https://github.com/tomnomnom/meg">Meg</a> is a powerful tool that allows you to find hidden paths/directories very quickly without flooding traffic.</p><p><strong><em>Command: meg paths.txt hosts.txt output</em></strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*hQwOzRPoo7zWDYUWvO0aoQ.png" /><figcaption>List of files created for the host example.com with the request and the response</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*KeY7DWwHmTOp9n_kKFj0Sw.png" /><figcaption>An example of a request been sent</figcaption></figure><p>You can also add custom headers to the request. Meg also supports RawHTTP.</p><blockquote><strong><em>Technique 8: Finding open ports and services</em></strong></blockquote><p>Every web application might have some other ports which are open and the services on these might be vulnerable. One should always look for these open ports and services running on them. But this might be time-consuming. <a href="https://github.com/projectdiscovery/naabu">Naabu</a> is a fast port scanner that can help you find these ports and services. The best thing is using naabu you can also run nmap scans as well.</p><p><strong><em>Command: naabu -host target.com</em></strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*gIKTRxniZBSGRV2RGHqpzg.png" /></figure><p>We hope that these recon techniques might help you to add and update your methodology. Do tell your recon methodology in the comments section.</p><p>Happy Hunting!</p><p><em>From Infosec Writeups: A lot is coming up in the Infosec every day that it’s hard to keep up with. </em><a href="https://weekly.infosecwriteups.com/"><strong><em>Join our weekly newsletter</em></strong></a><em> to get all the latest Infosec trends in the form of 5 articles, 4 Threads, 3 videos, 2 Github Repos and tools, and 1 job alert for FREE!</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1c5e0e294e89" width="1" height="1" alt=""><hr><p><a href="https://infosecwriteups.com/cool-recon-techniques-every-hacker-misses-1c5e0e294e89">Cool Recon techniques every hacker misses! 🔥🔥</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>
    </channel>
</rss>