<?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 Ibrahim Abdulhaqq on Medium]]></title>
        <description><![CDATA[Stories by Ibrahim Abdulhaqq on Medium]]></description>
        <link>https://medium.com/@enessyibrahim?source=rss-a626c14085c8------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*wueMcx510B-OJnEiT-6qiA@2x.jpeg</url>
            <title>Stories by Ibrahim Abdulhaqq on Medium</title>
            <link>https://medium.com/@enessyibrahim?source=rss-a626c14085c8------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Fri, 20 Nov 2026 18:10:52 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@enessyibrahim/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[Project Forgery: Automating CSRF Exploit Generation]]></title>
            <link>https://medium.com/@enessyibrahim/project-forgery-automating-csrf-exploit-generation-fd953ca8186a?source=rss-a626c14085c8------2</link>
            <guid isPermaLink="false">https://medium.com/p/fd953ca8186a</guid>
            <category><![CDATA[automation-testing]]></category>
            <category><![CDATA[bug-bounty]]></category>
            <category><![CDATA[penetration-testing]]></category>
            <category><![CDATA[offensive-security]]></category>
            <category><![CDATA[ethical-hacking]]></category>
            <dc:creator><![CDATA[Ibrahim Abdulhaqq]]></dc:creator>
            <pubDate>Wed, 04 Oct 2023 09:32:11 GMT</pubDate>
            <atom:updated>2023-10-04T09:32:11.277Z</atom:updated>
            <content:encoded><![CDATA[<p>A tool for generating Cross-Site Request Forgery (CSRF) exploit HTML for security testing.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/860/0*DfzalSNEmo5ZdaFq" /></figure><p>In the world of web security, it’s crucial to stay one step ahead of cyber threats. Cross-Site Request Forgery (CSRF) attacks remain a prevalent concern for web applications, making it essential to understand and test for these vulnerabilities. That’s where “Project Forgery” comes into play.</p><h4>What is Project Forgery?</h4><p>“Project Forgery” is an open-source security tool designed to streamline the process of generating CSRF exploits. This tool is perfect for security researchers, penetration testers, and developers who want to identify and mitigate CSRF vulnerabilities efficiently.</p><h4>Why CSRF Exploits Matter</h4><p>Before diving into “Project Forgery,” let’s grasp the significance of CSRF exploits. CSRF attacks occur when malicious websites trick users into performing actions on other websites where they are authenticated. These actions can range from changing passwords to making financial transactions, all without the user’s consent.</p><p>For organizations, failing to detect and prevent CSRF vulnerabilities can lead to data breaches, financial losses, and damage to their reputation. This underscores the importance of thorough testing and security assessments.</p><h4>Getting Started with Project Forgery</h4><p>Installation</p><p>To begin using “Project Forgery,” ensure you have Python installed on your machine. You can download it <a href="https://github.com/haqqibrahim/Project-Forgery">here</a>. Once Python is installed, follow these steps:</p><ol><li>Clone the “Project Forgery” repository from GitHub:</li></ol><pre>git clone https://github.com/haqqibrahim/Project-Forgery.git<br>cd project-forgery</pre><p>2. Install the required dependencies:</p><pre>pip install -r requirements.txt</pre><p>Usage</p><p>“Project Forgery” offers an easy-to-use command-line interface. Here’s how to generate CSRF exploits for both POST and GET requests:</p><pre>python3 csrf_script.py</pre><h3>Walkthrough: Creating a CSRF Exploit</h3><p>Let’s walk through an example to demonstrate how “Project Forgery” simplifies CSRF exploit generation.</p><ol><li>Generate Exploit HTML: Suppose we want to test a web application at https://example.com/change-password. We&#39;ll create a CSRF exploit HTML for a POST request.</li></ol><pre>python3 csrf_script.py</pre><p>2. Follow the prompts:</p><ul><li>Target URL: <a href="https://example.com/change-password">https://example.com/change-password</a></li><li>Parameter names: username, new_password</li><li>Parameter values: attacker, new_password_value</li></ul><p>The tool will generate the HTML, and you can customize it further if needed.</p><p>2. Crafting the Attack: Now, you have an HTML file with the CSRF exploit. You can host it on a server or email it to a victim user. When the user opens the HTML, their authenticated session on example.com may perform the password change without their knowledge.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*CbXKXTFJ0IHWxKQN_Pju-g.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*A8Jrlbfdsr3G008xgsrKPw.png" /></figure><h3>Conclusion</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/991/1*GNOVmsU10SiP1yjbkPqYaA.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*80bUyx7c89Fz4r8WgubnzQ.png" /></figure><p>“Project Forgery” empowers security professionals and developers to proactively identify and mitigate CSRF vulnerabilities in web applications. By simplifying CSRF exploit generation, it contributes to a safer online environment.</p><p>Give “Project Forgery” a try and enhance your security testing toolkit. Happy hacking responsibly!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=fd953ca8186a" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Automating Reconnaissance with Sling Shot R3con — powered by project Discovery tools]]></title>
            <link>https://medium.com/@enessyibrahim/automating-reconnaissance-with-sling-shot-r3con-powered-by-project-discovery-tools-2d6b870641da?source=rss-a626c14085c8------2</link>
            <guid isPermaLink="false">https://medium.com/p/2d6b870641da</guid>
            <category><![CDATA[penetration-testing]]></category>
            <category><![CDATA[bug-bounty]]></category>
            <category><![CDATA[automation]]></category>
            <category><![CDATA[cybersecurity]]></category>
            <category><![CDATA[reconnaissance]]></category>
            <dc:creator><![CDATA[Ibrahim Abdulhaqq]]></dc:creator>
            <pubDate>Thu, 21 Sep 2023 09:38:34 GMT</pubDate>
            <atom:updated>2023-09-22T08:31:01.330Z</atom:updated>
            <content:encoded><![CDATA[<h3>Automating Reconnaissance with Sling Shot R3con — powered by project Discovery</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/500/0*9fFN5OjKc8OTzTXP" /></figure><p>As developers and security enthusiasts, we often find ourselves automating repetitive tasks to save time and increase efficiency. In the realm of ethical hacking and bug bounty hunting, reconnaissance is a prime candidate for automation, as it involves tasks like subdomain discovery, DNS resolution, port scanning, and more. That’s where “Sling Shot R3con” comes into play — a powerful reconnaissance tool powered by <a href="https://github.com/projectdiscovery">Project Discovery tools</a>.</p><h3>What is Sling Shot R3con?</h3><p>Sling Shot R3con is an open-source reconnaissance tool designed to simplify the initial phase of bug bounty and penetration testing engagements. With a single command, it automates essential tasks, such as discovering subdomains, resolving DNS records, conducting port scans, identifying HTTP servers, and even crawling websites. Let’s explore how this tool works by delving into its code.</p><h3>Code Walkthrough</h3><p>Sling Shot R3con is written in Bash, making it accessible and easily extensible. It leverages Project Discovery tools and is structured into functions for clarity and modularity. Let’s break down the key functions and their roles:</p><h3>1. Setup Scan (setup_scan function)</h3><pre># Function to create a scan folder and set up necessary files<br>setup_scan() {<br>    local scope_path=&quot;$ppath/scope/$id&quot;<br><br>    # Displaying a banner powered by Project Discovery tools<br>   <br>    # Creating the scan folder for the target domain<br>    echo -e &quot;${CYAN}[INFO] Creating scan folder structure for $id&quot;<br>    mkdir -p &quot;$scope_path&quot;<br>    sleep 3<br><br>    # Creating necessary files and directories<br>    echo -e &quot;${CYAN}[INFO] Creating essential files and directories&quot;<br>    mkdir -p &quot;$scan_path/subdomains&quot;<br>    mkdir -p &quot;$scan_path/resolved&quot;<br>    mkdir -p &quot;$scan_path/ports&quot;<br>    mkdir -p &quot;$scan_path/http&quot;<br><br>    # Additional setup steps<br>    # ...<br>}</pre><p>The setup_scan function initializes the scan environment. It creates the foundation for the scan allowing the code logic to be modular and also mainting a clean folder structure.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*y3SIkHjxjXrXp6w8NjXB_Q.png" /></figure><h3>2. Perform DNS Scan (perform_dns_scan function)</h3><pre># Function to perform DNS enumeration and resolution<br>perform_dns_scan() {<br>    ## DNS Enumeration - Find Subdomains<br>    cat &quot;$scan_path/roots.txt&quot; | subfinder | anew &quot;$scan_path/subs.txt&quot;<br>    cat &quot;$scan_path/roots.txt&quot; | shuffledns -w &quot;$ppath/lists/subdomains-top1million-20000.txt&quot; -r &quot;$ppath/lists/resolvers.txt&quot; | anew &quot;$scan_path/subs.txt&quot; | wc -l<br><br>    ## DNS Resolution - Resolve discovered Subdomains<br>    puredns resolve &quot;$scan_path/subs.txt&quot; -r &quot;$ppath/lists/resolvers.txt&quot; -w &quot;$ppath/resolved.txt&quot; | wc -l<br>    dnsx -list &quot;$scan_path/resolved.txt&quot; -json -o &quot;$scan_path/dns.json&quot; | jq -r &#39;.a?[]?&#39; | anew &quot;$scan_path/ips.txt&quot; | wc -l<br>}</pre><p>The perform_dns_scan function focuses on DNS-related tasks. It uses Project Discovery tools like <a href="https://github.com/projectdiscovery/subfinder">Subfinder</a>, <a href="https://github.com/projectdiscovery/shuffledns">Shuffledns</a>, and <a href="https://github.com/projectdiscovery/dnsx">DNSx </a>with <a href="https://github.com/d3mondev/puredns">Puredns </a>to discover subdomains and resolve DNS records. These functions collectively build a foundation for further reconnaissance.</p><h3>3. Perform Port Scan (perform_port_scan function)</h3><pre># Function to perform port scanning and HTTP server discovery using Naabu<br>perform_port_scan() {<br>    ## Port scanning &amp; HTTP Server Discovery using Naabu<br>    naabu -l &quot;$scan_path/ips.txt&quot; -p 1-65535 -silent | cut -d &#39;/&#39; -f 1 | sort -u &gt; &quot;$scan_path/ports.txt&quot;<br>    tew -x &quot;$scan_path/ports.txt&quot; -dnsx &quot;$scan_path/dns.json&quot; --vhost -o &quot;$scan_path/hostport.txt&quot; | httpx -json -o &quot;$scan_path/http.json&quot;<br><br>    cat &quot;$scan_path/http.json&quot; | jq -r &#39;.url&#39; | sed -e &#39;s/:80$//g&#39; -e &#39;s/:443$//g&#39; | sort -u &gt; &quot;$scan_path/http.txt&quot;<br>}</pre><p>Port scanning is a crucial step in reconnaissance, and the perform_port_scan function leverages <a href="https://github.com/projectdiscovery/naabu">Naabu </a>a Project Discovery tool to conduct comprehensive port scanning. It identifies open ports, HTTP servers, and stores the results for further analysis. It also resolves Vhosting if present with the use of <a href="https://github.com/pry0cc/tew">tew</a>.</p><h3>4. Perform Crawling (perform_crawling function)</h3><pre># Function to perform crawling and JavaScript scraping<br>perform_crawling() {<br>    # CRAWLING<br>    katana -s &quot;$scan_path/http.txt&quot; --json | grep &quot;{&quot; | jq -r &#39;.output?&#39; | tee &quot;$scan_path/crawl.txt&quot;<br><br>    ### JavaScript crawling<br>    cat &quot;$scan_path/crawl.txt&quot; | grep &quot;\.js&quot; | httpx -sr -srd js<br>}</pre><p>Crawling websites and scraping JavaScript files are essential for gathering information, and the perform_crawling function makes this possible. It uses <a href="https://github.com/projectdiscovery/katana">Katana </a>a Project Discovery tool to crawl websites and scrape JavaScript files, which can be invaluable for finding vulnerabilities.</p><h3>5. Main Script</h3><p>The main script orchestrates the entire reconnaissance process, making use of the previously defined functions. It checks for prerequisites, sets up the scan environment, performs DNS enumeration, port scanning, and crawling. It also calculates and displays the scan duration.</p><h3>Getting Started with Sling Shot R3con</h3><p>To start using Sling Shot R3con:</p><ol><li>You can get acess to the project on <a href="https://github.com/haqqibrahim/Sling-Shot-R3con">GitHub</a>.</li><li>Change the mode of the requirements.sh file to execuatble chmod +x ./requirements.sh</li><li>Install the required dependencies by running ./requirements.sh.</li><li>Run the tool with the target domain as a parameter, like this: ./shoot.sh domain.com.</li></ol><p>For example, running ./shoot.sh google.com initiates a reconnaissance scan against google.com.</p><h3>Conclusion</h3><p>Sling Shot R3con is a robust and efficient tool powered by Project Discovery tools, making it a valuable asset for ethical hackers and bug bounty hunters. By automating reconnaissance tasks, it streamlines the initial phase of security assessments, ultimately saving time and effort. Feel free to explore the code further and customize it to suit your specific needs.</p><p>Give Sling Shot R3con a try, and supercharge your reconnaissance efforts today!</p><p>This article provides a detailed walkthrough of the “Sling Shot R3con” tool’s code an optimized version of Project Discovery’s <a href="https://blog.projectdiscovery.io/building-one-shot-recon/">One-Shot-Recon</a> script, emphasizing its modular structure and the integration of Project Discovery tools. Developers and security enthusiasts can use this tool to automate and enhance their bug bounty and penetration testing engagements, making it a valuable addition to their toolkit.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2d6b870641da" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Mastering Reconnaissance with Project Discovery]]></title>
            <link>https://medium.com/@enessyibrahim/mastering-reconnaissance-with-project-discovery-99d7a21e299a?source=rss-a626c14085c8------2</link>
            <guid isPermaLink="false">https://medium.com/p/99d7a21e299a</guid>
            <category><![CDATA[penetration-testing]]></category>
            <category><![CDATA[reconnaissance]]></category>
            <category><![CDATA[ethical-hacking]]></category>
            <category><![CDATA[bug-bounty]]></category>
            <category><![CDATA[cybersecurity]]></category>
            <dc:creator><![CDATA[Ibrahim Abdulhaqq]]></dc:creator>
            <pubDate>Mon, 18 Sep 2023 09:01:44 GMT</pubDate>
            <atom:updated>2023-09-18T09:01:44.845Z</atom:updated>
            <content:encoded><![CDATA[<p>Dissect your target during reconnaissance with <a href="https://projectdiscovery.io/">Project Discovery</a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/720/0*wMCZWLml6Bc6RnkD" /></figure><h3>Reconnaissance: What is it?</h3><p>Information on a target system or network is gathered during reconnaissance in order to find any potential weaknesses that might be exploited. This can be done using a variety of methods, including examining publicly accessible information about the target, utilizing tools to check for open ports and services on the target’s network and systems, and attempting to learn more about the target’s staff and operational procedures.</p><p>The purpose of reconnaissance is to learn as much as you can about the target in order to build a comprehensive profile of the system or network and find any potential vulnerabilities that could be exploited. The target attack can then be successfully planned and carried out using the information provided.</p><p>Reconnaissance is of forms, passive reconnaissance, which involves gathering data from publicly accessible sources without actively interacting with the target system or network, and active reconnaissance, which involves actively interacting with the target to gather data.</p><p>Simply said, reconnaissance gives one the opportunity to gather resources and increase the target’s overall attack surface but does not ensure a weakness.</p><h3>Types of Reconnaissance</h3><p><strong>Passive reconnaissance</strong>, you rely on publicly available knowledge. It is the knowledge that you can access from publicly available resources without directly engaging with the target. Think of it like you are looking at target territory from afar without stepping foot on that territory.</p><p>Passive reconnaissance activities include many activities, for instance looking up DNS records of a domain from a public DNS server, checking job ads related to the target website, and, reading news articles about the target company.</p><p><strong>Active reconnaissance</strong>, on the other hand, cannot be achieved so discreetly. It requires direct engagement with the target. Think of it like you check the locks on the doors and windows, among other potential entry points.</p><p>Examples of active reconnaissance activities include Connecting to one of the company servers such as HTTP, FTP, and SMTP, calling the company in an attempt to get information (social engineering), and, Entering company premises pretending to be a repairman</p><p>The degree of involvement with the target system or network is the primary distinction between active and passive reconnaissance. While passive reconnaissance entails acquiring information without actively interacting with the objective, active reconnaissance requires actively engaging with the target.</p><h3>Recon with Project Discovery Tools</h3><h3>Subdomain Enumeration</h3><p>Subdomain enumeration is a crucial reconnaissance method in penetration testing and bug bounty hunting. It involves recognizing and listing a target domain’s subdomains through active or passive methods. Active subdomain enumeration involves actively engaging the target domain through tools like DNS requests or web crawlers. Passive subdomain enumeration, on the other hand, involves acquiring data on the target domain’s subdomains without actively engaging with the domain itself. This method is less risky and more moral than active techniques, as it can be obtained from publicly accessible sources like papers and databases. Both active and passive techniques are essential for effective reconnaissance in these fields.</p><h3>Subfinder</h3><p><a href="https://github.com/projectdiscovery/subfinder?ref=blog.projectdiscovery.io">Subfinder</a> is a Go-based subdomain enumeration tool that efficiently finds valid subdomains for websites using passive online sources. Its modular architecture is optimized for speed and is specifically designed for passive subdomain enumeration.</p><p><strong>command:</strong></p><pre>subfinder -d target.com</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*So6P7zG2qnMpwVKDRQq8BA.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Km3x1r_bD4Qnt6ox8StGMg.png" /></figure><p>As soon as you execute the command, it will begin rapidly aggregating all accessible subdomains.</p><p>As you can see from the data, the subfinder performed the reconnaissance pretty effectively, finding 5000+ subdomains in about 35 seconds.</p><p>Subfinder is a fast tool that efficiently finds subdomains of a domain, providing results within minutes or less. It uses a passive method of subdomain enumeration, gathering information from publicly available sources and presenting it to the user, making it a stealthy tool that leaves no noticeable traces or logs on the target domain.</p><h3>Subdomain Brute-Forcing</h3><p>Active reconnaissance method known as “subdomain brute forcing” is connecting to a lot of subdomains in a domain to figure out which ones are legitimate. It entails attaching a target domain to a list of popular subdomain names, with the success or failure of these connections deciding whether subdomains are legitimate.</p><h3>ShuffleDNS</h3><p><a href="https://github.com/projectdiscovery/shuffledns">ShuffleDNS</a> is <strong>a MassDNS wrapper written in Go that allows users to enumerate valid subdomains using active bruteforce, as well as resolve subdomains with wildcard handling and easy input-output support</strong>.</p><p><strong>Command:</strong></p><pre>shuffledns -d example.com -list example-subdomains.txt -r resolvers.txt</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*kQiZvyf4umfhavCLx1qy5A.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*qiC4yqUNG9xEhlp4pZst-w.png" /></figure><p>To locate a file containing a list of <a href="https://public-dns.info/nameservers-all.txt?ref=blog.projectdiscovery.io">DNS resolvers</a>, use the option -r. All the terms for subdomain brute-forcing are in <a href="https://github.com/danielmiessler/SecLists/tree/master/Discovery/DNS?ref=blog.projectdiscovery.io">wordlist.txt.</a> (This might take a few minutes to complete).</p><h3>Host and Port Discovery</h3><p>After collecting all available subdomains (subdomain enumeration), the next step filters all valid subdomains based on their HTTP method and response content. The httpx tools is able to gather data about a web server, including the HTTP methods it supports and the information in its HTTP headers.</p><h3>Httpx</h3><p><a href="https://github.com/projectdiscovery/httpx?ref=blog.projectdiscovery.io">httpx</a> is capable for doing reconnaissance to learn more about a web server. This data can be used to find the server’s weak points and vulnerabilities. It provides a number of options and capabilities that can be helpful for filtering legitimate subdomains, seeing response headers, figuring out HTTP methods, and displaying the IP of the subdomain. We can also use httpx with subfinder to get fast results.</p><p><strong>Command:</strong></p><pre>subfinder -d target.com | httpx -status-code -tech-detect -title</pre><p><em>-status-code is used to specify the HTTP status code that is returned</em></p><p><em>-tech-detect allows you to identify the technologies &amp; frameworks used</em></p><p><em>-title allows you to extract the title of a webpage from the HTML source code</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*RtMLgxqmehssCmHxm7a7Vw.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*4vBL0OyJ9MJHfTAF23BuYw.png" /></figure><h3>Port Scanning</h3><p>In order to determine which network ports are open on a target system or network, port scanning is a method that can be employed as part of reconnaissance. Active reconnaissance is what this is. Network ports are used to recognize and distinguish between various forms of network traffic, and each port is connected to a particular service or application.</p><p>A port scan helps identify potential vulnerabilities or attack targets by gathering information about the running services and applications on a target system or network.</p><h3>Naabu</h3><p><a href="https://github.com/projectdiscovery/naabu?ref=blog.projectdiscovery.io">Naabu</a> is a tool written in Go programming language that quickly and accurately find open ports on a target system or network. The target system is subjected to SYN/CONNECT scans, and the program identifies all ports that respond by returning information about the services and programs currently executing on the system. In order to determine which network ports are open on a target system or network, port scanning is a method that can be employed as part of reconnaissance(active reconnaissance). Network ports are used to recognize and distinguish between various forms of network traffic, and each port is connected to a particular service or application.</p><p><strong>Command:</strong></p><pre>naabu -host target.com</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*3801Jix_KApiFEuyAQfXKg.png" /></figure><h3>Template-Based Scanning</h3><p>Template-based scanning is an active reconnaissance technique that uses predefined templates to identify vulnerabilities and misconfigurations in a target system or network. This method of reconnaissance allows users to customize the types of issues they look for and updates the templates as new vulnerabilities or misconfigurations are discovered.</p><h3>Nuclei</h3><p><a href="https://github.com/projectdiscovery/nuclei?ref=blog.projectdiscovery.io">nuclei</a> is a tool developed by ProjectDiscovery that can be used to perform vulnerability scanning and reconnaissance. It is designed to be fast and efficient and can scan a target system or network for a wide range of vulnerabilities and misconfigurations.</p><p>Nuclei uses a library of editable templates that specifies the kinds of vulnerabilities and configuration errors it should search for Both active and passive scanning methods can be used to examine a target system or network.</p><p><strong>Command:</strong></p><pre>nuclei -u target.com -t technologies</pre><p><em>-t option is used to specify the template for scanning.</em></p><p><em>technologies template to detect the technology of the target.</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*VNZeSX7zV49iN5lnYTwaMw.png" /></figure><p><strong>Command:</strong></p><pre>nuclei -u target.com -t cves</pre><p><em>cves template to perform the CVE scan on the target.</em></p><h3>Crawling and Spidering</h3><p>Crawling and spidering aid in identifying web server resources that may not be easily accessible through the application’s public interface, such as directories or files not linked to the application’s main pages.</p><h3>GetAllUrls (GAU)</h3><p><a href="https://github.com/lc/gau?ref=blog.projectdiscovery.io">GetAllUrls</a> (GAU) is a tool used to enumerate, crawl and discover URLs and directories on a web server. GAU fetches known URLs from external sources, including AlienVault’s Open Threat Exchange, the Wayback Machine, Common Crawl, and URLScan.</p><p><strong>Command:</strong></p><pre>gau https://target.com</pre><p>Once you execute, the command gau will start crawling the target domain.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*IExwVOfXSMlD5Y1bBCsbrQ.png" /></figure><h3>Katana</h3><p><a href="https://github.com/projectdiscovery/katana?ref=blog.projectdiscovery.io">katana</a> is a next-generation crawling and spidering framework</p><p><strong>Command:</strong></p><pre>katana -jc -u &lt;https://target.com&gt;</pre><p><em>-jc (JS crawl) is a handy function in katana while performing recon. It allows endpoint parsing and crawling in JS (JavaScript) files.</em></p><p><em>-u to specify target domain.</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*p82uYqFs4l9WSlqnYPgItA.png" /></figure><p>Gau and Katana are fast and similar in scanning, but GAU focuses on URL discovery, while Katana offers more comprehensive options like in-depth JavaScript crawling and custom cookies for requests.</p><h3>Directory Enumeration</h3><p>Directory enumeration is a method used to identify directories and files on a target system or network. It involves a systematic scan using a tool or script to identify potential targets, sensitive files, and information about the system’s layout and structure.</p><h3>Dirsearch</h3><p><a href="https://github.com/maurosoria/dirsearch?ref=blog.projectdiscovery.io">Dirsearch</a> is a Python-based tool used to perform a brute-force search for directories and files on a target system or network by generating and testing many potential directories and file name</p><p><strong>Command:</strong></p><pre>dirsearch -u target.com -i 200 -e php, jsp, js</pre><p><em>-i option is used to specify the status code</em></p><p><em>-e option is used to specify the file extension(s) that should be tested during the directory enumeration process.</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*wq5q7LB-jPPzDgC_TkLBDw.png" /></figure><h3>Conclusion</h3><p>Reconnaissance is an essential part of penetration testing and bug bounty hunting, as it is the process of gathering information about a target to identify potential attack vectors and vulnerabilities. This writeup provides an overview of the various reconnaissance techniques powered majorly by <a href="https://projectdiscovery.io/">Project Discovery</a> tools, as well as advice on how to effectively utilize them to maximize the chances of success.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=99d7a21e299a" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[100 days of hacking: Day 20 — How to Research like a hacker]]></title>
            <link>https://medium.com/@enessyibrahim/100-days-of-hacking-day-20-how-to-research-like-a-hacker-50fdd8f1594?source=rss-a626c14085c8------2</link>
            <guid isPermaLink="false">https://medium.com/p/50fdd8f1594</guid>
            <category><![CDATA[100daysofcode]]></category>
            <category><![CDATA[cybersecurity]]></category>
            <category><![CDATA[ethical-hacking]]></category>
            <dc:creator><![CDATA[Ibrahim Abdulhaqq]]></dc:creator>
            <pubDate>Sun, 17 Sep 2023 15:50:02 GMT</pubDate>
            <atom:updated>2023-09-17T15:50:02.112Z</atom:updated>
            <content:encoded><![CDATA[<h3>100 days of hacking: Day 20 — How to Research like a hacker</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/612/0*El0O8gR4Aru3iF7K" /></figure><h3>Introduction</h3><p>Without a doubt, the ability to research effectively is <em>the</em> most important quality for a hacker to have. By its very nature, hacking requires a <em>vast</em> knowledge base — because how are you supposed to break into something if you don’t know how it works? The thing is: no one knows everything. Everyone (professional or amateur, experienced or totally new to the subject) will encounter problems which they don’t automatically know how to solve. This is where research comes in, as, in the real world, you can’t ever expect to simply be handed the answers to your questions.</p><p>As your experience level increases, you will find that the things you’re researching scale in their difficulty accordingly; however, in the field of information security, there will never come a point where you don’t need to look things up.</p><p>this article will act as a brief overview of some of the most important resources available to you, and will hopefully aid you in the process of building a research methodology that works for you.</p><p>We will be looking at the following topics:</p><ul><li>An example of a research question</li><li>Vulnerability Searching tools</li><li>Linux Manual Pages</li></ul><h3>Example Research Question</h3><p>We’ll begin by looking at a typical research question: the kind that you’re likely to find when working through a CTF on TryHackMe.</p><p>Let’s say you’ve downloaded a JPEG image from a remote server. You suspect that there’s something hidden inside it, but how can you get it out?</p><p>How about we start by searching for “hiding things inside images” in Google:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*H4zR_vgHr__uq6IRUQcLYQ.png" /></figure><p>Notice that the first link gives us the title of a technique: “Steganography”. You can then click that link and read the document, which will teach you <em>how</em> files are hidden inside images.</p><p>Ok, so we know how it’s done, let’s try searching for a way to extract files using steganography:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/873/1*ol17Ttn8jvy_Q0Dj_-bdSQ.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/911/1*uSaTxiFuTUd5QFWWEMMJPw.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/887/1*xiPaVfE6irKEAveGDos4Tg.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/943/1*6gAHUOIwKJTeEocKMnjrhw.png" /></figure><p>Already virtually every link is pointing to something useful. The first link contains a collection of useful tools, the second is more instructions on how to perform steganography in the first place. Realistically any of these links could prove useful, but let’s take a look at that first one (<a href="https://0xrick.github.io/lists/stego/">https://0xrick.github.io/lists/stego/</a>):</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*wk-fhKAUsOgbCJo9.png" /></figure><p>The very first tool there looks to be useful. It can be used to extract embedded data from JPEG files — exactly what we need it to do! This page also tells you that steghide can be installed using something called “apt”.</p><p>Let’s search that up next!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/899/1*g0scROfahgEJy9oanMK5TA.png" /></figure><p>Great — so apt is a package manager that lets us install tools on Linux distributions like Ubuntu (or Kali!).</p><p>How can we install packages using apt? Let’s search it!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/987/1*uj1ovXdqeyzDauEDAhvChw.png" /></figure><p>Perfect — right at the top of the page we’re given instructions. We know that our package is called steghide, so we can go ahead and install that:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/898/0*wD3BD4bY15SvFzsg.png" /></figure><p>Now, let’s switch back to that collection of steganography tools we were looking at before. Did you notice that there were instructions on how to use steghide right there?</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/806/0*3_znrRS90XPdHmKa.png" /></figure><p>There we go! That’s how we can extract an image from a file.</p><h3>Vulnerability Searching</h3><p>Often in hacking you’ll come across software that might be open to exploitation. For example, Content Management Systems (such as Wordpress, FuelCMS, Ghost, etc) are frequently used to make setting up a website easier, and many of these are vulnerable to various attacks. So where would we look if we wanted to exploit specific software?</p><p>The answer to that question lies in websites such as:</p><ul><li><a href="https://www.exploit-db.com/">ExploitDB</a></li><li><a href="https://nvd.nist.gov/vuln/search">NVD</a></li><li><a href="https://cve.mitre.org/">CVE Mitre</a></li></ul><p>NVD keeps track of CVEs (<strong>C</strong>ommon <strong>V</strong>ulnerabilities and <strong>E</strong>xposures) — whether or not there is an exploit publicly available — so it’s a really good place to look if you’re researching vulnerabilities in a specific piece of software. CVEs take the form: CVE-YEAR-IDNUMBER</p><p><a href="https://www.exploit-db.com/">ExploitDB</a> tends to be very useful for hackers, as it often actually contains exploits that can be downloaded and used straight out of the box. It tends to be one of the first stops when you encounter software in a CTF or pentest.</p><p>If you’re inclined towards the CLI on Linux, Kali comes pre-installed with a tool called “searchsploit” which allows you to search ExploitDB from your own machine. This is offline, and works using a downloaded version of the database, meaning that you already have all of the exploits already on your Kali Linux!</p><p>Let’s take an example. Say we’re playing a CTF and we come across a website:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*2pAto3VxG-kx0V5C.png" /></figure><p>Well, this is quite obviously FuelCMS. Usually it won’t be <em>this</em> obvious, but hey, we’ll work with what we’ve got! We know the software, so let’s search for it in ExploitDB.</p><p>(<em>Note: I’m going to use the CLI tool in Kali, as it tends to be quicker from a workflow perspective — however, you are welcome to use the website)</em></p><p>I’m using the command searchsploit fuel cms to search for exploits:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*eS-iMPdlGbFFcaxdb86yBw.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*jgJ6lhZu-qymZakV.png" /></figure><p>Success! We’ve got an exploit that we can now use against the website!</p><p>Actually using the exploit is outwith the scope of this article, but you can see the process.</p><p>If you click on the title you’ll be given a bit more of an explanation about the exploit:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*uEuEOkm0Y3-rUPJH.png" /></figure><p>Pay particular attention to the CVE numbers; you’ll need them for the questions!</p><p>The format will be like so: CVE-YEAR-NUMBER</p><p><strong><em>Note:</em></strong><em> CVEs numbers are assigned when the vulnerability are discovered, not when they are publicised. Bear in mind that if a vulnerability is discovered at the end of a year, or if the process of confirming and rectifying the vulnerability takes a long time, then the release date might be the year after the year in the CVE date… bear this in mind when answering the following questions</em></p><h3>Using ChatGPT for Hacking Research</h3><p>In the world of hacking, having access to a tool like ChatGPT can significantly enhance your research capabilities. While ChatGPT cannot directly hack or break into systems, it can assist you in various ways:</p><h3>Day 20: Introduction to Research</h3><h3>Using ChatGPT for Hacking Research</h3><p>In the world of hacking, having access to a tool like ChatGPT can significantly enhance your research capabilities. While ChatGPT cannot directly hack or break into systems, it can assist you in various ways:</p><ol><li>Idea Generation: ChatGPT can help you brainstorm ideas for potential exploits or vulnerabilities. You can describe a target system or software, and ChatGPT can provide suggestions for attack vectors.</li><li>Code Assistance: If you’re developing custom scripts or tools for hacking purposes, ChatGPT can help you with code snippets, debugging, and troubleshooting.</li><li>Understanding Vulnerabilities: ChatGPT can provide explanations and details about specific vulnerabilities or exploits you come across during your research.</li><li>Information Gathering: You can ask ChatGPT to fetch information about software, systems, or vulnerabilities from reputable sources on the internet.</li></ol><p>Here’s an example of how you can use ChatGPT for research in the context of hacking:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/837/1*o-kQRSiEmMqen6thliZWKg.png" /></figure><h3>Conclusion</h3><p>You may have been told in school that there are good sources and bad sources of information. That may be true when it comes to essays and referencing information; however, it’s my pleasure to state that it does not apply here. Any information can potentially be useful — so feel free to use blogs, AIs, wikipedia, or anything else that contains what you’re looking for! Blogs especially can often be very valuable for learning when it comes to information security, as many security researchers keep a blog.</p><p><em>Thank you for joining me on this 20-day hacking journey. Although I won’t be able to continue daily updates due to work, I’ll be sharing weekly articles. Stay tuned for more cybersecurity insights and happy hacking!</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=50fdd8f1594" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[100 days of hacking day 16 — Uncovering Vulnerabilities: A Practical Walkthrough of Components…]]></title>
            <link>https://medium.com/@enessyibrahim/100-days-of-hacking-day-16-uncovering-vulnerabilities-a-practical-walkthrough-of-components-e693fe3c8dc7?source=rss-a626c14085c8------2</link>
            <guid isPermaLink="false">https://medium.com/p/e693fe3c8dc7</guid>
            <category><![CDATA[100daysofcode]]></category>
            <category><![CDATA[cybersecurity]]></category>
            <category><![CDATA[hacking]]></category>
            <dc:creator><![CDATA[Ibrahim Abdulhaqq]]></dc:creator>
            <pubDate>Wed, 13 Sep 2023 22:02:15 GMT</pubDate>
            <atom:updated>2023-09-13T22:02:15.170Z</atom:updated>
            <content:encoded><![CDATA[<h3><strong>100 days of hacking day 16 — Uncovering Vulnerabilities: A Practical Walkthrough of Components with Known Vulnerabilities</strong></h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/612/0*ghFJxkJdJL2lWnbb" /></figure><p>Welcome back to the next chapter in our exploration of online security flaws, this time with a focus on “Components with Known Vulnerabilities.” This article takes a hands-on approach to investigating this critical area of web security.</p><p>Following on from our previous <a href="https://medium.com/@enessyibrahim/unmasking-vulnerabilities-exploring-owasps-top-10-components-with-known-vulnerabilities-2b983269eea6">talk</a>, we’ll go deeper into this subject, presenting you with a complete practical walkthrough. We’ll use a TryHackMe virtual machine to demonstrate this, providing a real-world situation that will help you understand the importance of resolving known vulnerabilities.</p><p><strong><em>The Setting: CSE Bookstore</em></strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*qQYa1NZXV0GQwFUVRwBxsg.png" /></figure><p>The CSE Bookstore, an online bookstore ripe for penetration testing, will serve as our virtual laboratory for this experiment. Before we get into the technical intricacies, keep this essential rule in mind: manually examine the target online application. This step is critical for understanding the structure of the application, its risks, and how users interact with it.</p><p><strong><em>Getting Acquainted with CSE Bookstore</em></strong></p><p>Let’s begin by getting acquainted with the CSE Bookstore online application. Before we begin probing for weaknesses, we must first understand its functionality and layout. This is similar to a hacker’s initial reconnaissance, in which they gather information about the target.</p><p>After we’ve been acquainted with the application, we’ll get to the meat of the problem: finding and exploiting components with known vulnerabilities. However, as with any penetration test, careful reconnaissance is the key to success.</p><p>Stay tuned as we investigate the CSE Bookstore’s design and find potential flaws. In the following installment, we’ll look more closely at the vulnerabilities, showing how they can be exploited and, most crucially, how to guard against them.</p><p>So buckle your virtual seatbelts and join me on this thrilling adventure into the area of web security, where knowledge and practice meet to build strong defenses against cyber threats.</p><p>· I noticed that the web app is unauthenticated, to start let’s search online for recent unauthenticated bookstore app rce’s. In the search result exploits-db showed up, Let’s take a look and see what we’ll find.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/772/1*SA9P4yzV-cbwfe0U3m6Vrw.png" /></figure><p>· So exploit-db gave us a piece of code we can use to exploit unauthenticated apps.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*qc1DyZpXRqPoWMUPaUS_1g.png" /></figure><ul><li>Let’s download the code and try to execute it on our machine.</li><li>So when I attempted to run the exploit, I ran into an error. Let’s try debugging the code to fix the error stating that the following arguments are required: URL. This means to run this code successfully I need to provide the target URL</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/947/1*gMJQVJd8U07684JV-porZQ.png" /></figure><p>· After some trials I successfully executed the code</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/922/1*yVbM8QtUxtmwU32-MW_YKg.png" /></figure><ul><li>Look at the logs it says web shell uploaded to <a href="http://10.10.210.230/bootstrap/img/hlCcBWQd28.php">http://10.10.210.230/bootstrap/img/hlCcBWQd28.php</a> This means any command we pass as arguments to the above URL will executed and the result will be displayed on the web browser.</li><li>Let’s use the example command so we can have a clearer understanding.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/882/1*raNBeI5su6IusumEo3NCPQ.png" /></figure><p>· We sent a whoami command and it gave us a response. Now let’s try and find How many characters are in /etc/passwd (use wc -c /etc/passwd to get the answer)</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/935/1*5qgyHgiy3h3Nz7nZhqaKgA.png" /></figure><p><strong><em>Conclusion</em></strong></p><p>We’ve delved deep into the world of web security in our investigation of “Components with Known Vulnerabilities,” where proactive measures play a critical role in preserving the digital landscape. This hands-on tutorial has highlighted the crucial need for fixing identified vulnerabilities in web applications.</p><p>We illustrated, using the CSE Bookstore as our virtual playground, that every penetration test, and every security assessment, starts with a simple step: manual investigation. This preliminary investigation not only familiarizes us with the application but also assists us in understanding its structure and potential flaws.</p><p>As we’ve seen, the digital world is full of programs that may unknowingly harbor known vulnerabilities. These are vulnerabilities that have already had patches and remedies written for them, yet they continue to exist owing to a lack of updates and monitoring. This carelessness can be an organization’s Achilles’ heel, allowing malevolent actors to enter with little effort.</p><p>However, education is our most powerful ally in this fight. We empower ourselves to identify and remedy these vulnerabilities properly with each practical exercise and exploration. We’ve shown how, with the correct information, even seemingly sophisticated exploits can be carried out with relative ease.</p><p>Finally, our journey through online security flaws continues, with each step getting us closer to a more secure digital world. Remember that web security is a team effort, not just a security professionals’ responsibility. We can reinforce our digital environments against old and new threats by being aware, using ethical hacking skills, and lobbying for strong security measures.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e693fe3c8dc7" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Unmasking Vulnerabilities: Exploring OWASP’s Top 10 — Components with Known Vulnerabilities]]></title>
            <link>https://medium.com/@enessyibrahim/unmasking-vulnerabilities-exploring-owasps-top-10-components-with-known-vulnerabilities-2b983269eea6?source=rss-a626c14085c8------2</link>
            <guid isPermaLink="false">https://medium.com/p/2b983269eea6</guid>
            <category><![CDATA[hacking]]></category>
            <category><![CDATA[cybersecurity]]></category>
            <category><![CDATA[100daysofcode]]></category>
            <dc:creator><![CDATA[Ibrahim Abdulhaqq]]></dc:creator>
            <pubDate>Tue, 12 Sep 2023 21:28:18 GMT</pubDate>
            <atom:updated>2023-09-12T21:28:18.293Z</atom:updated>
            <content:encoded><![CDATA[<h3><strong>100 days of hacking day 15 -Unmasking Vulnerabilities: Exploring OWASP’s Top 10 — Components with Known Vulnerabilities</strong></h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/860/0*8ozyiPnAr3WFFok2" /></figure><p>As we near the end of our journey through the OWASP Top 10 vulnerabilities, the ten most serious web security threats, we reach a point when the focus is on “Components with Known Vulnerabilities.” In this post, we’ll delve into the complexities of this sometimes overlooked threat, which lurks in the shadows of online applications, waiting for the right opportunity to strike.</p><p><strong><em>Understanding Components with Known Vulnerabilities</em></strong></p><p>Consider the following scenario: a corporation or entity you’ve been charged with pen-testing relies on a specific software or program for its operations. Unbeknownst to them, this program contains a well-documented vulnerability, similar to a ticking time bomb. This vulnerability could be caused by using outdated software versions, plugins, or libraries with known security issues.</p><p>Consider a corporation that has been neglecting to update its WordPress installation for several years. Following a comprehensive examination using tools like as WPScan, you learn that the company’s WordPress version is a dated 4.6. A cursory investigation finds that WordPress 4.6 is vulnerable to an unauthenticated remote code execution (RCE) attack. To make matters worse (from a security standpoint), you may locate an exploit for this vulnerability on Exploit-DB.</p><p><strong><em>The Looming Threat of Known Vulnerabilities</em></strong></p><p>When you consider how easily this might happen, the gravity of the problem becomes clear. A single missed update for a crucial program can expose a business to a slew of threats. Known vulnerabilities, which are classed as a high-level threat (OWASP rating of 3, indicating high prevalence), are especially insidious because the majority of the groundwork has already been prepared for attackers. Exploits and attack vectors are frequently widely available, allowing bad actors to strike with ease.</p><p><strong><em>A Straightforward Path for Attackers</em></strong></p><p>One distinguishing feature of known vulnerabilities is that they take little effort from attackers. Gathering information about the software, painstakingly investigating it, and hunting for the exploit are the primary duties. Others have often done the difficult work of detecting the vulnerability and building an attack, which has been documented in the public domain.</p><p><strong><em>Practical Example: Navigating the Landscape</em></strong></p><p>Let’s look at a practical example to show how to cope with known vulnerabilities. We’ll look at a web application and figure out how to discover, investigate, and perhaps exploit a known vulnerability. This real-world situation will shed light on the proactive efforts required to properly counter such threats.</p><p>Finally, as we near the end of our journey through the OWASP Top 10 vulnerabilities, we must acknowledge that the danger of known vulnerabilities looms big. To protect against these hidden risks, organizations must remain attentive, regularly updating their software components and maintaining a strong security posture. Stay tuned as we explore the fascinating realm of web security.</p><ul><li>What do you know, this server is using the default page for the nostromo web server. Now that we have a version number and a software name, we can use <a href="https://www.exploit-db.com/">exploit-db</a> to try and find an exploit for this particular version.</li><li><strong>(Note: exploit-db is incredibly useful, and for we beginners you’re gonna be using this a lot so it’s best to get comfortable with it)</strong></li></ul><p>·</p><p>Lucky us, the top result happens to be an exploit script. Let’s download it and try and to get code execution. Running this script on it’s own actually teaches us a very important lesson.</p><p>· It may not work the first time. It helps to have an understanding of the programming language that the script is in, so that if needed you can fix any bugs or make any modifications, as quite a few scripts on exploit-db expect you to make modifications.</p><p>· Fortunately for us, the error was caused by an line that should have been commented, so it’s an easy fix.</p><ul><li>Fixing that, let’s try and run the program again.</li><li>Boom! We have RCE. Now it’s important to note here that most scripts will just tell you what arguments you need to provide, exploit developers will rarely make you read potentially hundreds of lines of codes just to figure out how to use the script.</li><li>It is also worth noting that it may not always be this easy, sometimes you will just be given a version number like in this case, but other times you may need to dig through the HTML source, or even take a lucky guess on an exploit script, but realistically if it is a known vulnerability, there’s probably a way to discover what version the application is running.</li><li>That’s really it, the great thing about this piece of the OWASP 10, is that the work is pretty much already done for us, we just need to do some basic research, and as a penetration tester, you’re already doing that quite a bit :).</li></ul><p><strong><em>Conclusion and Prevention</em></strong></p><p>Staying aware and proactive is essential for preventing recognized vulnerabilities:</p><p>· Updates on a regular basis: Update your software, plugins, and systems. Apply patches and security upgrades on a regular basis to reduce your exposure to known vulnerabilities.</p><p>· Vulnerability Scanning: Use vulnerability scanning technologies to proactively discover and address issues.</p><p>· Security Concerns: Inform your employees on the significance of software updates and their role in sustaining strong security.</p><p>Finally, “Components with Known Vulnerabilities” demonstrate the risks associated with ignoring the importance of updates and fixes. In the ever-changing landscape of web security, diligence and prompt action are your most powerful allies in combating this pernicious risk.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2b983269eea6" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[100 days of hacking: day 14 — Unmasking the World of Cyber Threats: Understanding Attackers and…]]></title>
            <link>https://medium.com/@enessyibrahim/100-days-of-hacking-day-14-unmasking-the-world-of-cyber-threats-understanding-attackers-and-9aa69a191984?source=rss-a626c14085c8------2</link>
            <guid isPermaLink="false">https://medium.com/p/9aa69a191984</guid>
            <category><![CDATA[100daysofcode]]></category>
            <category><![CDATA[hacking]]></category>
            <category><![CDATA[cybersecurity]]></category>
            <dc:creator><![CDATA[Ibrahim Abdulhaqq]]></dc:creator>
            <pubDate>Mon, 11 Sep 2023 20:51:49 GMT</pubDate>
            <atom:updated>2023-09-11T20:51:49.771Z</atom:updated>
            <content:encoded><![CDATA[<h3><strong>100 days of hacking: day 14 -Unmasking the World of Cyber Threats: Understanding Attackers and Their Motivations</strong></h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/860/0*CKCxlR-I0u-Ejo18" /></figure><p><strong>Introduction</strong></p><p>Welcome to the fascinating world of cybersecurity, where the battle between hackers and defenders unfolds on the digital frontier. In this engaging article, we will delve into the different types of cyber threats, the motivations driving their actions, and the impact they have on the security industry.</p><p><strong>The Arsenal of Malicious Code</strong></p><p>At the heart of cyber threats lie various forms of malicious code designed to wreak havoc in the digital realm. Computer viruses, cunning entities crafted to disrupt operations and damage data and software, stand among the most notorious culprits. Additionally, worms, capable of replicating and spreading without human intervention, pose a unique challenge in their autonomous propagation.</p><p><strong>Social Engineering: The Art of Manipulation</strong></p><p>Enter the realm of social engineering, a manipulation technique that exploits human error to gain access to private information or valuables. Threat actors, often acting as social engineers, create environments of false trust and deception to exploit unsuspecting victims. From phishing to USB baiting, we uncover the various guises used in social engineering attacks and the alarming effectiveness of these tactics.</p><p><strong>The Menace of Malware</strong></p><p>Malware, a menacing software breed, seeks to harm devices and networks to gain financial advantage or intelligence leverage. Viruses, initiated by users who unknowingly transmit the malicious code, wreak havoc upon activation. On the other hand, worms autonomously propagate across networks, leaving devastation in their wake. Notorious ransomware encrypts critical data, holding it hostage until a ransom is paid, while spyware stealthily gathers sensitive information without consent.</p><p><strong>Unraveling Phishing Attacks</strong></p><p>A prominent form of digital deception, phishing exploits digital communications to trick individuals into revealing sensitive data or deploying malicious software. From spear phishing targeting specific users to vishing using voice communication, we explore the arsenal of phishing tactics employed by cyber adversaries.</p><p><strong>Past Cybersecurity Attacks: Learning from History</strong></p><p>Drawing lessons from the past is crucial in the world of cybersecurity. We take a glimpse at some infamous historical attacks, from the brain virus tracking illegal software copies to the Equifax breach affecting millions of Americans, emphasizing the need for constant vigilance in the ever-changing landscape of threats.</p><p><strong>CISSP Security Domains: Key Pillars of Defense</strong></p><p>Understand the core pillars of cybersecurity with CISSP security domains. From security and risk management to software development security, we explore the fundamental areas of focus that form a resilient defense against cyber threats.</p><p><strong>Understanding Attackers: Motivations and Intentions</strong></p><p>Dive into the minds of cyber adversaries as we explore different types of threat actors and their motivations. Advanced persistent threats (APTs) target critical infrastructure and intellectual property, while insider threats exploit authorized access for sabotage and espionage. Hacktivists, fueled by political agendas, harness digital technology for demonstrations and social change campaigns.</p><p><strong>The Hacker Spectrum: Ethics and Agendas</strong></p><p>Within the hacker community lies a diverse spectrum of motivations and ethics. Authorized hackers, also known as ethical hackers, serve to protect organizations from malicious threats. Semi-authorized hackers explore vulnerabilities without exploitation, while unauthorized hackers engage in malicious activities for financial gain. Delve into this intricate world where skillsets and intentions intertwine.</p><p><strong>Conclusion</strong></p><p>As we conclude this journey into the depths of cyber threats, one thing becomes evident — the digital landscape is a battleground between ingenuity and malevolence. Understanding the motivations and tactics of cyber adversaries empowers us to fortify our defenses and navigate the evolving challenges of cybersecurity. With knowledge as our weapon, let us unite in the pursuit of a safer digital world, resilient against the ever-present menace of cyber threats.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=9aa69a191984" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[100 days of hacking-Day 13 Demystifying the OWASP Top 10: Unearthing Cross-Site Scripting (XSS)]]></title>
            <link>https://medium.com/@enessyibrahim/100-days-of-hacking-day-13-demystifying-the-owasp-top-10-unearthing-cross-site-scripting-xss-b24bbb670165?source=rss-a626c14085c8------2</link>
            <guid isPermaLink="false">https://medium.com/p/b24bbb670165</guid>
            <category><![CDATA[100daysofcode]]></category>
            <category><![CDATA[hacking]]></category>
            <category><![CDATA[cybersecurity]]></category>
            <dc:creator><![CDATA[Ibrahim Abdulhaqq]]></dc:creator>
            <pubDate>Sun, 10 Sep 2023 21:12:46 GMT</pubDate>
            <atom:updated>2023-09-10T21:12:46.412Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/640/0*pwoYch78rst3824z" /></figure><p>Welcome to Day 13 of our 100-day hacking adventure. Today, we’re continuing our look at the OWASP Top 10 vulnerabilities, this time concentrating on one of the most pernicious web security threats: Cross-Site Scripting, also known as XSS. This essay will help you understand the inner workings of this vulnerability, its repercussions, and how to defend yourself from it.</p><p><strong><em>The Essence of Cross-Site Scripting (XSS)</em></strong></p><p>Cross-Site Scripting, or XSS, is a strong enemy in web application security. It exemplifies a security flaw that is typically hiding within web applications and waiting to be exploited. XSS is a type of injection attack that allows attackers to execute malicious scripts within a victim’s web browser.</p><p><strong><em>XSS Unveiled</em></strong></p><p>To really understand XSS, you must first understand its principles. When a web application fails to properly sanitize user input, XSS becomes conceivable. It can appear in a variety of programming languages, such as JavaScript, VBScript, Flash, and CSS. XSS is classified into three types:</p><p>Stored XSS: This is likely the most dangerous type of XSS. A malicious script originates from the website’s database in a stored XSS scenario. This frequently occurs when a website accepts user input that has not been properly sanitized, allowing malicious code to be stored in the database for future execution.</p><p>Reflected XSS occurs when the malicious payload is incorporated into the victim’s request to the website. This payload is then inadvertently included in the website’s response to the user. To carry out their malicious payload, attackers must fool a victim into clicking on a URL containing the malicious script.</p><p>DOM-Based DOM (Document Object Model): A programming interface for HTML and XML documents. It represents a page’s structure, style, and content, allowing programs to change these aspects. DOM-Based XSS occurs when the document model of a web page is changed in order to run malicious code within the browser.</p><p>To explore a treasure trove of XSS payloads, tools, documentation, and more, head to XSS-Payloads.com. Here, you can find payloads ranging from webcam snapshots to advanced port and network scanners.</p><p><strong><em>The XSS Challenge Awaits</em></strong></p><p>To put theory into reality, we’ll use a TryHackMe virtual computer to take on an XSS challenge. This VM is intended to demonstrate various types of XSS, such as DOM-Based, Reflected, and Stored XSS. Stay tuned as we explore the complex area of XSS exploitation and defenses.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/975/1*oK1kLe1QC3MSTVBMDFaDVQ.png" /></figure><ul><li>Let’s start with the Reflected XSS section.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/975/1*nXyRMEz6lAjUOo_IDcR99Q.png" /></figure><ul><li>It has a search bar, we’ll test for Relfected XSS using the payload below to get a pop up “Hello Wordl”:</li><li>Payload:</li></ul><pre>&lt;script&gt;alert(&quot;Hello World&quot;)&lt;/script&gt;</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/975/1*hvUXdkY6ajUrWqYU6FcJgw.png" /></figure><p>· We didn’t get a pop up saying “Hello” because this is a hacking lab and we are meant to find</p><p>flags, instead of getting “Hello” we got a flag — <strong>ThereIsMoreToXSSThanYouThink</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/975/1*cGU1w-KC45jsi0ZLwM77lQ.png" /></figure><ul><li>Let’s see if we can get the webapp hostname.</li><li>payload:</li></ul><pre>&lt;script&gt;alert(window.location.hostname)&lt;/script&gt;</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/975/1*qhrWv3X3SVoEJbtOoNbGfw.png" /></figure><p>· We’ll get the webapp IP address, we’ll also get another popup with a flag –</p><p><strong>ReflectiveXss4TheWin</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/975/1*GQ3_XgpF2O6NU5r-QfTObQ.png" /></figure><p>· Now let’s go back to the home page and then navigate to store XSS, and create an account, using the navbar navigate to stored XSS after being logged in.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/975/1*TTZClclRX6021wg69aYXng.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/975/1*EHkvQKBKOHwa6iGAJWC9zA.png" /></figure><p>· now let’s add some HTML to the comment section.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/975/1*L3-cIkNkzD95oi6wX4tvUA.png" /></figure><p>· Submit the comment and you’ll see the HTML in the list of comments, refresh the browser multiple times the HTML will still be there, we also found a flag — <strong>HTML_T4gs</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/975/1*kkPDSlnK0JLtJOv41NpxmA.png" /></figure><ul><li>Now let’s see if we can sniff out the browser’s cookies using this payload:</li><li>payload:</li></ul><pre>&lt;script&gt;alert(document.cookie)&lt;/script&gt;</pre><ul><li>submit the cookies, you’ll get to different alert box, one with the browser&#39;s cookies and flag.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/975/1*eNfQcQJFw0DdUO5d7Prmow.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/975/1*trMGJrF_AmUUsN6Yo6ruSQ.png" /></figure><ul><li>Now let’s do something more spicey, let’s change “XSS Playground” to “I am a hacker” by adding a comment and using Javascript.</li><li>payload: &lt;script&gt;document.querySelector(‘#thm-title’).textContent = ‘I am a hacker’&lt;/script&gt;</li><li>Check the headeryou’ll see the payload “I am a hacker there” and check the Questions section, you’ll get a flag — <strong>websites_can_be_easily_defaced_with_xss.</strong></li><li>Also notice that after submitting the payload all the stored XSS payload we have used are in action. That is the power of stored XSS.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/975/1*bNlir7NPh-XgPn1Sqzqaag.png" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b24bbb670165" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[100 days of hacking-day 11 — Unraveling the OWASP Top 10: Understanding Security Misconfigurations]]></title>
            <link>https://medium.com/@enessyibrahim/100-days-of-hacking-day-11-unraveling-the-owasp-top-10-understanding-security-misconfigurations-1d2db53ec681?source=rss-a626c14085c8------2</link>
            <guid isPermaLink="false">https://medium.com/p/1d2db53ec681</guid>
            <category><![CDATA[100daysofcode]]></category>
            <category><![CDATA[cybersecurity]]></category>
            <category><![CDATA[hacking]]></category>
            <dc:creator><![CDATA[Ibrahim Abdulhaqq]]></dc:creator>
            <pubDate>Sat, 09 Sep 2023 22:40:05 GMT</pubDate>
            <atom:updated>2023-09-09T22:40:05.943Z</atom:updated>
            <content:encoded><![CDATA[<h3><strong><em>100 days of hacking-day 11 — Unraveling the OWASP Top 10: Understanding Security Misconfigurations</em></strong></h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/500/0*fZ0wlj1DOhWgOyxx" /></figure><p>In our continuous exploration of the realm of web security, we are delving deep into the OWASP Top 10 vulnerabilities — the ten most serious web security threats that keep cybersecurity professionals awake at night. Today’s topic is “Security Misconfigurations.” Security misconfigurations, unlike some of the other vulnerabilities on this list, are caused by a lack of correct configuration rather than by inherent faults in the product. Let’s look into this sometimes overlooked but dangerous weakness.</p><p><strong><em>Understanding Security Misconfigurations</em></strong></p><p>As the name implies, security misconfigurations occur when security settings that should have been specified correctly are left in a vulnerable state. These misalignments manifest in a variety of ways, including:</p><p>1. Incorrectly Set Permissions on Cloud Services: One typical symptom is incorrectly set permissions on cloud services such as S3 buckets. This omission may result in unauthorized access to sensitive data.</p><p>2. Superfluous Services, Pages, Accounts, or Privileges Enabled: Enabling superfluous services, pages, accounts, or privileges creates more attack surfaces. Attackers can take advantage of this to get illegal access.</p><p>3. Default Accounts with unmodified Passwords: In a production setting, leaving default accounts with unmodified passwords is similar to leaving the front door open. It encourages unauthorized access.</p><p>4. Overly Detailed Error Messages: For attackers, error messages that give too much information about the system can be a gold mine. These notifications can reveal vulnerabilities that they can exploit.</p><p>5. Failure to Implement adequate HTTP Security Headers: Failure to implement adequate HTTP security headers can open the door to a variety of web-based assaults.</p><p>6. Too Much Information in the Server: HTTP Headers: The Server’s Name: HTTP headers can sometimes leak information about the underlying infrastructure, allowing attackers to target specific vulnerabilities more easily.</p><p><strong><em>Security Misconfigurations’ Domino Effect</em></strong></p><p>One concerning aspect of security misconfigurations is their ability to cause a chain reaction of vulnerabilities. For example, attackers may gain access to sensitive data if default credentials are kept untouched. Furthermore, security flaws can open the door to more serious exploits such as XML External Entity (XXE) assaults or command injection on administrative sites.</p><p>For individuals interested in learning more about Security Misconfigurations, the OWASP has a useful resource in their Top 10 entry for Security Misconfiguration.</p><p><strong><em>Example: Uncovering a Security Misconfiguration in Practice</em></strong></p><p>Let’s put theory into practice with an example from real life. We’ll use a TryHackMe virtual system to demonstrate a Security Misconfiguration, which corresponds to one of the OWASP Top 10 Vulnerabilities.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*f_NGUUX00V1No05-39ipSg.png" /></figure><ul><li>I used the hint as a starting point: “Can you find the app’s source code? Maybe the documentation gives you default credentials that you can try.” — where can i find the source code? <strong>GitHub</strong></li><li>So i used <strong>Google Dorking</strong> to find the Github page for the website. — <strong>site:github.com pensivenotes</strong></li><li>From the search, i found a github repo for the project</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*UVP7S0EU8fivZVIGrJgVMw.png" /></figure><p>I then visited the GitHub repo, at the bottom of the <a href="http://reade.me/">READE.me</a> there is a message that contains a default credentials — This is bad security practice.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/960/1*WogTqRd_yygfGHjsr-DbhA.png" /></figure><p>I used the default credentials to login to the webapp</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ZFZ6MgRD-qFuD1Ccr-ZS7w.png" /></figure><ul><li>At the home page we found the flag for this VM. — <strong>thm{4b9513968fd564a87b28aa1f9d672e17}</strong></li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*7CTkBuoYaGW4i42aH9E6_g.png" /></figure><p><strong>Other Scenarios:</strong></p><p>Consider coming upon a system that unintentionally discloses a security flaw. This misconfiguration could result in a security breach, making it a perfect scenario to investigate and learn from.</p><p><strong>Conclusion</strong></p><p>Stay tuned as we dive into this practical example, exploring the complexities of Security Misconfigurations and how they can pose a huge threat to web applications and systems.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1d2db53ec681" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[100 days of hacking-Day 11: Understanding and Mitigating Broken Access Control Vulnerabilities]]></title>
            <link>https://medium.com/@enessyibrahim/100-days-of-hacking-day-11-understanding-and-mitigating-broken-access-control-vulnerabilities-2751d519e9dd?source=rss-a626c14085c8------2</link>
            <guid isPermaLink="false">https://medium.com/p/2751d519e9dd</guid>
            <category><![CDATA[cybersecurity]]></category>
            <category><![CDATA[hacking]]></category>
            <category><![CDATA[100daysofcode]]></category>
            <dc:creator><![CDATA[Ibrahim Abdulhaqq]]></dc:creator>
            <pubDate>Fri, 08 Sep 2023 21:16:50 GMT</pubDate>
            <atom:updated>2023-09-08T21:16:50.032Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/856/0*3ttFBsoEOEi2A7bL.png" /></figure><p>Staying ahead of potential dangers is critical in the ever-changing world of web security. The OWASP Top 10 vulnerabilities provide a useful framework for identifying and mitigating the most serious web security concerns. In this article, we’ll delve into one of these flaws: Broken Access Control.</p><p>When websites fail to effectively restrict access to specific pages or capabilities, unauthorized users can obtain sensitive information or do actions they should not be able to. This vulnerability endangers the integrity and security of online applications.</p><p><strong><em>Understanding Broken Access Control</em></strong></p><p>Access control is a critical component of web security. Pages on websites are frequently restricted to select individuals, such as administrators. When normal visitors gain access to protected pages or features that they are not authorized to see or use, the access restrictions are said to be breached.</p><p>Broken access control can have serious repercussions. Unauthorized access can result in:</p><p><strong>Viewing Sensitive Data</strong>: Attackers can get access to sensitive data, jeopardizing user privacy and security.</p><p><strong>Unauthorized Functionality</strong>: Attackers may take advantage of flaws in access control to carry out actions reserved for privileged users, thereby inflicting damage or disruption.</p><p><strong><em>Typical Attack Scenarios</em></strong></p><p>The Open Web Application Security Project (OWASP) has identified several attack scenarios that highlight access control flaws. There are two notable scenarios:</p><p><strong><em>Scenario 1 </em></strong>SQL Injection Attack</p><p>In this example, an application accesses account information by using unverified data in a SQL request. If the ‘acct’ parameter is not correctly checked, an attacker can exploit it to get access to any user’s account. This can lead to the compromise of critical data.</p><p><strong><em>Scenario 2</em></strong>: An Aggressive Browsing Attack</p><p>Without proper authentication or authorization, attackers attempt to access target URLs such as admin pages. It shows a security problem if unauthenticated users may access restricted pages or non-administrative users can access admin pages.</p><p>Broken access control fundamentally allows attackers to circumvent permission, allowing them to view sensitive data or conduct operations as privileged users.</p><p><strong><em>The IDOR (Insecure Direct Object Reference) Challenge</em></strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/571/0*tTPyCEMzJpzCR5fF.png" /></figure><p>IDOR (Insecure Direct Object Reference) is a sort of broken access control vulnerability. It happens when user input is handled incorrectly, allowing unauthorized access to protected resources. Consider the following scenario: a hacker can update an ‘account number’ parameter in a URL to gain access to someone else’s bank information.</p><p><strong><em>As an example,</em></strong></p><p>Consider the following practical example of detecting and exploiting an IDOR vulnerability:</p><p>The user successfully signs in but observes that the URL includes an ‘account number’ argument, which indicates the logged-in user’s note ID.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*4O6vyc1TQ4UMtZZNznFL7A.png" /></figure><p>The user tries to change the note ID in the URL and gains access to another user’s note, demonstrating the presence of an IDOR vulnerability.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*TidMXaL4t61BOsXSIExIdg.png" /></figure><p>This practical example highlights the real-world consequences of broken access control and IDOR vulnerabilities, underlining the significance of dealing with these issues as soon as possible.</p><p><strong><em>IDOR Prevention and Conclusion</em></strong></p><p>A proactive approach to web application security is required to prevent broken access control and IDOR vulnerabilities. Consider the following critical measures:</p><p><strong>Implement Adequate Access Controls</strong>: Make certain that access to sensitive pages or functions is restricted based on user roles and permissions.</p><p><strong>Data Validation and Sanitization</strong>: Validate and sanitize user input to prevent injection attacks like the one mentioned in the SQL injection example.</p><p><strong>Session Management</strong>: To avoid unauthorized access, use secure session management strategies.</p><p><strong>Security Testing</strong>: Perform security testing regularly, including penetration testing and code reviews, to detect and address vulnerabilities.</p><p>Overall, identifying and mitigating broken access control issues, such as IDOR, is critical for preserving web application security and integrity. Developers and organizations may safeguard their users and data from potential risks by adhering to best practices and being attentive.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2751d519e9dd" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>