<?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 Max Klose on Medium]]></title>
        <description><![CDATA[Stories by Max Klose on Medium]]></description>
        <link>https://medium.com/@mxmd?source=rss-8bcd7cb87b92------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*C6LxYGh3T-z5EGqH7ExIjQ.png</url>
            <title>Stories by Max Klose on Medium</title>
            <link>https://medium.com/@mxmd?source=rss-8bcd7cb87b92------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Thu, 28 May 2026 05:47:23 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@mxmd/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[Getting Started with Recon Automation using ReNgine on Windows (WSL): Installation Guide]]></title>
            <link>https://systemweakness.com/getting-started-with-recon-automation-using-rengine-on-windows-wsl-installation-guide-50ad95b8a7a9?source=rss-8bcd7cb87b92------2</link>
            <guid isPermaLink="false">https://medium.com/p/50ad95b8a7a9</guid>
            <category><![CDATA[reconnaissance]]></category>
            <category><![CDATA[bug-bounty-hunting]]></category>
            <category><![CDATA[automation]]></category>
            <category><![CDATA[bug-bounty]]></category>
            <category><![CDATA[guides-and-tutorials]]></category>
            <dc:creator><![CDATA[Max Klose]]></dc:creator>
            <pubDate>Mon, 18 Dec 2023 23:30:24 GMT</pubDate>
            <atom:updated>2023-12-20T15:36:54.352Z</atom:updated>
            <content:encoded><![CDATA[<p>Reconnaissance plays a crucial role in bug hunting and pentesting, serving as a vital step to ensure coverage of all assets. However, many bug hunters, particularly those new to the field, may encounter challenges in establishing an effective reconnaissance flow. By leveraging a Linux system operating as a subsystem of your Windows (10/11) machine, you gain the advantages of both worlds.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/876/1*LgC4K--noYxkGOwH6bPd4A.png" /></figure><h4>1. Understanding ReNgine</h4><p><a href="https://github.com/yogeshojha/rengine">ReNgine 2.0</a> is a collection of tools designed not only for reconnaissance but also equipped with an intuitive graphical user interface, making it particularly suitable for beginners. I recommend utilizing a VPN on your Windows desktop before launching a scan to prevent your IP from being banned across the internet, especially when conducting scans beyond reconnaissance.</p><h4>2. Setting Up Windows Subsystem for Linux (WSL 2)</h4><p>WSL 2 runs with Hyper-V Virtualization, so you might need to <a href="https://www.simplilearn.com/enable-virtualization-windows-10-article#how_to_enable_virtualization_in_windows_1011">enable that in the BIOS</a>, if you haven’t.</p><ul><li>Open the Terminal as an Administrator, copy and paste</li></ul><pre>wsl --install</pre><ul><li>Set WSL default version to avoid future problems</li></ul><pre>wsl --set-default-version 2</pre><ul><li>At this point you can install the below Ubuntu version, which worked for me or Kali Linux directly from the Microsoft Store</li></ul><ul><li><a href="https://www.microsoft.com/store/productId/9PN20MSR04DW?ocid=pdpshare">Ubuntu 22.04.3 LTS - Official app in the Microsoft Store</a></li><li><a href="https://www.microsoft.com/store/productId/9PKR34TNCV07?ocid=pdpshare">Kali Linux - Official app in the Microsoft Store</a></li></ul><h4>3. Installing ReNgine on WSL</h4><ul><li>Install <a href="https://www.docker.com/products/docker-desktop/">Docker Desktop</a> on Windows</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/649/1*6W5DGDTZ13p_VR25rpWGDg.png" /><figcaption><a href="https://youtu.be/idW-an99TAM?t=601">https://youtu.be/idW-an99TAM?t=601</a></figcaption></figure><ul><li>Open it and go the Setting, then make sure “Use the WSL 2 based engine” is enabled</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*5h-ycJv6Ra43kvR6-hUdew.png" /></figure><ul><li>The options in the Resources tab should appear as follows, with the integration enabled on the system you installed (in this case, Ubuntu 22.04).</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*2AEJXNlCoT7Ch6QQhAbikQ.png" /></figure><ul><li>Now to open the Linux System with the Terminal (install the new <a href="https://www.microsoft.com/store/productId/9N0DX20HK701?ocid=pdpshare">Terminal</a> in Case you haven’t)</li><li>Open Terminal and from there you can select the System</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/722/1*0lQsfTfx5sF3IUg1LLvlUQ.png" /></figure><ul><li>Within the Ubuntu instance, use the following command to install prerequisites, clone the GitHub repository, navigate to it, and modify the “POSTGRES_PASSWORD” in the dotenv file using:</li></ul><pre>sudo apt update &amp;&amp; sudo apt upgrade &amp;&amp; sudo apt install make &amp;&amp; sudo apt install build-essential &amp;&amp; git clone https://github.com/yogeshojha/rengine &amp;&amp; cd rengine &amp;&amp; nano .env</pre><ul><li>Inside the dotenv file edit the maximum concurrency to your machines RAM</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/278/1*Y3GEa52ivB4wFbsha7SCdw.png" /></figure><ul><li>Finally running the install script and enter username and a safe password when prompted</li></ul><pre>chmod +x &amp;&amp; sudo ./install.sh</pre><ul><li>ReNgine is now accessible through your web browser at <a href="https://127.0.0.1"><strong>https://127.0.0.1</strong></a></li><li>While you’re in the /rengine folder in the linux terminal you can run the command <strong>sudo make stop</strong>, to stop the instance and <strong>sudo make up</strong> to start it</li></ul><h4>4. Configuring ReNgine</h4><p>As for Configuration its highly recommended to provide an OpenAI API key at the API Vault in ReNgine’s Settings.</p><ul><li>Simply create one at <a href="https://platform.openai.com/api-keys">https://platform.openai.com/api-keys</a></li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/487/1*ovWTu7oANEkrGVab_gfywA.png" /></figure><h4>5. Running Your First ReNgine Scan</h4><ul><li>Select Quick Add</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*-A7Xuvw5gV8p1u5FGcwLCg.png" /></figure><ul><li>Add your target, for example a domain</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/987/1*48Jtr55SC0V0BcK8I-6B5g.png" /></figure><ul><li>Specify a Scan Engine or make a custom one</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*fSC6g8B3HIe6IVk8R4phrg.png" /></figure><ul><li>Optionally import additional Subdomains and add Out-of-Scope Subdomains, as well as Filtering, before initiating the Scan</li></ul><h4>6. Tips for Effective Bug Hunting</h4><ul><li>Mainly use reNgine for Recon, not relying on automated Vulnerability Scans</li><li>Use a customized Scan Engine</li><li>Add your <a href="https://rengine.wiki/usage/notification/">Discord WebHook</a> for additional functionality like Notifications</li></ul><h4>Conclusion</h4><p>ReNgine on Windows WSL offers a user-friendly solution for bug hunting reconnaissance. Its seamless integration and security measures make it a valuable asset for cybersecurity enthusiasts.</p><h4>Additional Resources</h4><ul><li><a href="https://rengine.wiki/">reNgine</a></li><li><a href="https://www.youtube.com/@criticalthinkingpodcast">Critical Thinking - Bug Bounty Podcast</a></li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=50ad95b8a7a9" width="1" height="1" alt=""><hr><p><a href="https://systemweakness.com/getting-started-with-recon-automation-using-rengine-on-windows-wsl-installation-guide-50ad95b8a7a9">Getting Started with Recon Automation using ReNgine on Windows (WSL): Installation Guide</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[Exploring New Vulnerability Vectors: A Systematic Approach to Manual Google Dorking]]></title>
            <link>https://mxmd.medium.com/exploring-new-vulnerability-vectors-a-systematic-approach-to-manual-google-dorking-fdfc79e9825d?source=rss-8bcd7cb87b92------2</link>
            <guid isPermaLink="false">https://medium.com/p/fdfc79e9825d</guid>
            <category><![CDATA[cybersecurity]]></category>
            <category><![CDATA[bug-bounty-tips]]></category>
            <category><![CDATA[bug-bounty]]></category>
            <category><![CDATA[google-dorking]]></category>
            <category><![CDATA[osint]]></category>
            <dc:creator><![CDATA[Max Klose]]></dc:creator>
            <pubDate>Thu, 07 Dec 2023 16:52:05 GMT</pubDate>
            <atom:updated>2023-12-20T17:16:46.596Z</atom:updated>
            <content:encoded><![CDATA[<h3>Exploring Vulnerability Vectors: An Approach to Manual Google Dorking</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*dpINRBVCtfqf1jEtgM08Ug.jpeg" /></figure><h4>Introduction</h4><p>Google Dorking, or Bing Dorking, represents a technique leveraging search engines to uncover sensitive files and intriguing endpoints like login panels. These endpoints often get indexed through various channels, such as User-Generated content.</p><h4>Background</h4><p>Participating in Bug Bounty and Vulnerability Disclosure Programs underscores the importance of uncovering vulnerabilities that Pentesters may have missed due to time constraints. Google Dorking, a component of the passive Reconnaissance Phase, enables the identification of potential vulnerabilities without direct interaction with the target. Success with dorking, however, depends on the target, particularly when only a few pages are indexed.</p><h4>Discovery of Vulnerabilities</h4><p>The nature of these vulnerabilities can range from an organization being obligated to publish financial documents to a misconfiguration, which becomes a potential vulnerability vector when disclosing sensitive information. Determining the relevance of a vulnerability to the organization’s Threat Model involves defining the impact, explaining what adversaries can achieve.</p><h4>Manual Google Dorking Process</h4><p>1. Specify the target domain using <strong>site:example.com</strong><em> </em>or the organization name with an optional <strong>© </strong>symbol, <strong>“© OrganizationName“</strong></p><p>2. Check for various file formats using <strong>ext:</strong> and the or operator<strong>|</strong></p><pre>site:example.com ext:log | ext:txt | ext:pdf | ext:docx | ext:docm | ext:dot | ext:dotx | ext:odt | ext:rtf | ext:xls | ext:xlsx</pre><p>3. Narrow the search for special terms in the files like <strong>“confidential” “internal”</strong></p><pre>site:example.com &quot;confidential&quot; ext:log | ext:txt | ext:pdf | ext:docx | ext:docm | ext:dot | ext:dotx | ext:odt | ext:rtf | ext:xls | ext:xlsx</pre><p>4. If no sensitive files are found, search for other interesting endpoints using <strong>inurl:</strong> and <strong>intitle:</strong></p><pre>site:example.com inurl:login | intitle:login | intitle:dashboard | inurl:dashboard</pre><p>5. Finally, it’s worth checking <a href="https://www.bing.com/">Bing </a>for interesting endpoints, especially if the target is running Windows IIS.</p><pre>site:example.com &quot;login&quot;</pre><h4>Risk Assessment</h4><p>Potential risks of vulnerabilities, such as information disclosure of Personally Identifiable Information (PII) through files, can lead to significant fines by authorities, reputational damage, and more, depending on the scale and sensitivity.</p><h4>Mitigation</h4><p>Mitigating vulnerabilities identified through Google Dorking requires organizations to implement Attack Surface Management, in addition to Pentesting, VDPs/BBPs, and advising employees not to publish sensitive links on social media.</p><h4>Lessons Learned</h4><ul><li>Include Google and Bing Dorking among the initial steps in your methodology</li><li>Adjust your Dorking keywords depending on the target</li><li>Check Bing Dorking for any target with Windows IIS technology (Good Tip by <a href="https://x.com/GodfatherOrwa?s=20">Orwa Atyat</a>)</li></ul><h4>Conclusion</h4><p>While the vulnerability vectors I discovered weren’t groundbreaking, they provided me with valuable insights and leads on vulnerabilities.</p><h4>Other Resources</h4><ul><li><a href="https://www.exploit-db.com/google-hacking-database">OffSec&#39;s Exploit Database Archive</a></li><li><a href="https://infosecwriteups.com/mass-google-dorking-techniques-for-bug-bounty-d2ba87f49fb7">Mass Google Dorking Techniques for Bug Bounty</a></li><li><a href="https://orwaatyat.medium.com/">Orwa Atyat - Medium</a></li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=fdfc79e9825d" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>