<?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 Muhammad Ajmal CA on Medium]]></title>
        <description><![CDATA[Stories by Muhammad Ajmal CA on Medium]]></description>
        <link>https://medium.com/@ajju0075?source=rss-1d680c0bea34------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*DrNuGCd015iHyto78u8W6g.jpeg</url>
            <title>Stories by Muhammad Ajmal CA on Medium</title>
            <link>https://medium.com/@ajju0075?source=rss-1d680c0bea34------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Thu, 19 Nov 2026 09:44:55 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@ajju0075/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[Where is linux log files?]]></title>
            <link>https://medium.com/@ajju0075/where-is-linux-log-files-c2c2c1ba0cdf?source=rss-1d680c0bea34------2</link>
            <guid isPermaLink="false">https://medium.com/p/c2c2c1ba0cdf</guid>
            <category><![CDATA[logs]]></category>
            <category><![CDATA[kali-linux]]></category>
            <category><![CDATA[linux-log]]></category>
            <dc:creator><![CDATA[Muhammad Ajmal CA]]></dc:creator>
            <pubDate>Thu, 22 May 2025 01:36:24 GMT</pubDate>
            <atom:updated>2025-05-22T01:36:24.637Z</atom:updated>
            <content:encoded><![CDATA[<h3>Where is Linux log files?</h3><p>Hi all,<br>Today, we’re going to take a look at <strong>log files on Linux</strong>, especially in <strong>Kali Linux</strong>.</p><p>If you ever wondered where your system stores details about logins, errors, software installs, or security alerts — the answer is in the <strong>log files</strong>. These files keep track of everything happening in the background.</p><h3>What Are Log Files?</h3><p>Think of log files like your Linux system’s <strong>diary</strong>.</p><p>They record:</p><ul><li>System messages</li><li>Login attempts</li><li>Software errors</li><li>Boot information</li><li>Security events</li><li>And much more!</li></ul><p>In Kali Linux (or any Debian-based Linux), logs are <strong>stored as text files</strong>, and you can read them using the terminal or a text editor.</p><h3>Where Are Log Files Stored?</h3><p>Log files are usually stored in this folder:</p><pre>/var/log/</pre><p>This is the main location where Linux keeps most of its logs.</p><p>To view the log folder, open your terminal and run:</p><pre>ls /var/log/</pre><p>You’ll see a list of many files. Let’s go over some important ones.</p><h3>Important Log Files You Should Know</h3><h3>1. /var/log/syslog or /var/log/messages</h3><p>These are general system logs.</p><p>In Kali Linux, you can check:</p><pre>sudo cat /var/log/syslog</pre><p>It contains all sorts of messages — system boot info, services, hardware messages, etc.</p><h3>2. /var/log/auth.log</h3><p>This log is all about <strong>security</strong> and <strong>authentication</strong>.</p><p>It records:</p><ul><li>Login attempts (successful &amp; failed)</li><li>sudo usage</li><li>SSH logins</li></ul><p>To view it:</p><pre>sudo cat /var/log/auth.log</pre><p>This is <strong>very important</strong> for cybersecurity!</p><h3>3. /var/log/dmesg</h3><p>This file logs <strong>hardware-related messages</strong>, especially during boot.</p><p>Run:</p><pre>dmesg | less</pre><p>Or just:</p><pre>sudo cat /var/log/dmesg</pre><h3>4. /var/log/apt/</h3><p>This folder stores logs related to <strong>apt commands</strong>, like when you install or update software.</p><pre>ls /var/log/apt/</pre><p>Inside it, you’ll see logs like history.log.</p><h3>5. /var/log/kern.log</h3><p>Contains messages from the <strong>kernel</strong> (the heart of Linux).</p><p>Good for debugging low-level system problems.</p><pre>sudo cat /var/log/kern.log</pre><h3>How to View Logs (Easily)</h3><p>Use these commands:</p><ul><li>cat – shows the whole file</li><li>less – lets you scroll up/down</li><li>tail – shows the last few lines</li><li>tail -f – live view (real-time log updates)</li></ul><p>Example:</p><pre>sudo tail -f /var/log/auth.log</pre><p>This will <strong>watch the log live.</strong></p><h3>Why Are Logs Useful in Cybersecurity?</h3><ul><li>Spot suspicious login attempts</li><li>Detect system errors</li><li>Monitor what tools were used</li><li>Analyze attacker activity (in real-world incidents)</li></ul><p>If you’re learning <strong>SOC, SIEM, or blue teaming</strong>, logs are gold.</p><h3>Clearing Logs (If Needed)</h3><p>You can clear logs like this:</p><pre>sudo truncate -s 0 /var/log/auth.log</pre><p>Be careful — don’t delete logs unless you know what you’re doing. It’s often better to <strong>rotate</strong> them (Linux does this automatically using logrotate).</p><p>Linux log files are stored in:</p><pre>/var/log/</pre><p>Some important files:</p><p>syslog – system messages</p><p>auth.log – security events</p><p>dmesg – hardware logs</p><p>apt – installation logs</p><p>kern.log – kernel logs</p><p>Use cat to view them easily.</p><p>Learning to read logs is <strong>must</strong> if you want to get good at Linux, especially for C<strong>ybersecurity</strong> .</p><p>Start exploring your /var/log/ folder, and you will start to <strong>see the full story of your system</strong>.</p><p>Let me know in the comments if you want a blog about <strong>how to analyze logs to detect attack!</strong></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c2c2c1ba0cdf" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How to Create a Linux user and grant root permission]]></title>
            <link>https://medium.com/@ajju0075/how-to-create-a-linux-user-and-grant-root-permission-108bceaccb59?source=rss-1d680c0bea34------2</link>
            <guid isPermaLink="false">https://medium.com/p/108bceaccb59</guid>
            <category><![CDATA[root-access]]></category>
            <category><![CDATA[create-user-in-linux]]></category>
            <category><![CDATA[kali-linux]]></category>
            <dc:creator><![CDATA[Muhammad Ajmal CA]]></dc:creator>
            <pubDate>Thu, 22 May 2025 01:19:29 GMT</pubDate>
            <atom:updated>2025-05-22T01:19:29.415Z</atom:updated>
            <content:encoded><![CDATA[<p>Hi all,<br>If you’re new to Kali Linux don’t know how to create a new user and give them root (admin) access, you’re in the right place.</p><p>In this blog, I’ll walk you through everything step by step</p><h3>Why Add a New User?</h3><p>When you install Kali Linux, you usually get a default user. But it’s a good idea to create a separate user for your work. You may also want to give that user admin (root) powers to install software, change system settings, etc.</p><h3>Step 1: Open Terminal</h3><p>Kali is a Linux system, and most things happen through the <strong>terminal</strong>.<br> Just click on the terminal icon (or press Ctrl + Alt + T) to open it.</p><h3>Step 2: Create a New User</h3><p>Type the following command to create a new user (replace ajmal with your username):</p><pre>sudo adduser ajmal</pre><p>It will ask you to enter a password for the new user. You can skip other info by pressing Enter again and again.</p><p>Done! You just created a new user.</p><h3>Step 3: Add User to Sudo Group (for Root Access)</h3><p>To give the new user <strong>root/admin</strong> permission, add them to the <strong>sudo group</strong>. Type:</p><pre>sudo usermod -aG sudo ajmal</pre><p>This command adds the user to the sudo group, which means they can now use sudo to run commands as root.</p><h3>Step 4: Test the New User</h3><p>Now, switch to the new user:</p><pre>su - ajmal</pre><p>Try running a command with sudo to check if it works:</p><pre>sudo apt update</pre><p>If it asks for your password and runs the command successfully — congrats! You now have a working user with root powers.</p><h3>Tip: Keep It Safe</h3><p>Just because you can use root doesn’t mean you always should.<br> Only use sudo when needed — like installing tools or changing system settings. It helps protect your system from accidental damage.</p><p>And that’s it! You’ve now:</p><p>Created a new user<br> Given them root permission<br> Switched and tested it</p><p>This method works not just on Kali Linux, but also on most Debian-based Linux systems (like Ubuntu, Parrot OS, etc.).</p><p>If this helped you, feel free to share or bookmark it for later. Got any questions? Drop them in the comments — I’ll try to help!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=108bceaccb59" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How to setup Linux webserver]]></title>
            <link>https://medium.com/@ajju0075/how-to-setup-linux-webserver-0b879f1c6ea7?source=rss-1d680c0bea34------2</link>
            <guid isPermaLink="false">https://medium.com/p/0b879f1c6ea7</guid>
            <category><![CDATA[kali-linux-on-virtualbox]]></category>
            <category><![CDATA[linux]]></category>
            <category><![CDATA[kali-linux]]></category>
            <category><![CDATA[web-server]]></category>
            <category><![CDATA[kali]]></category>
            <dc:creator><![CDATA[Muhammad Ajmal CA]]></dc:creator>
            <pubDate>Thu, 22 May 2025 00:56:32 GMT</pubDate>
            <atom:updated>2025-05-22T00:56:32.398Z</atom:updated>
            <content:encoded><![CDATA[<p>Hi all,<br>Today in these blog I will be setup my own web server using <strong>Kali Linux</strong> running inside a <strong>Virtual Machine (VM)</strong>. I did this to understand how web servers work and to host my own simple web pages. So here’s a step-by-step guide,</p><h3>Step 1: My Setup</h3><p>Here’s what I used:</p><ul><li><strong>Kali Linux </strong>installed inside <strong>VirtualBox (or VMware)</strong></li><li>Host OS: Windows (but it works on Linux or Mac too)</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/852/1*4LMEKIIuAV-Wrq2j3PFD4g.png" /></figure><h3>Step 2: Update Kali Linux</h3><p>I opened the terminal in Kali and ran the update commands to make sure everything was fresh:</p><pre>sudo apt update &amp;&amp; sudo apt upgrade -y</pre><h3>Step 3: Install Apache Web Server</h3><p>Next, I installed Apache, web server:</p><pre>sudo apt install apache2 -y</pre><p>Once installed, I start the server using:</p><pre>sudo systemctl start apache2</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/927/1*Iqu9dv0_NgaxdO2EwLucWA.png" /></figure><p>You should see something like “active (running)”.</p><p>To test it, I opened the browser inside Kali and visited:</p><pre>http://127.0.0.1</pre><p>There you will saw the <strong>Apache2 default page</strong>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/832/1*xRvN-Nih8WQ_FvXZEqe81A.png" /></figure><h3>Step 4: Create Your Own Web Page</h3><p>Apache serves files from this directory:</p><pre>/var/www/html</pre><p>So I replaced the default file with my own:</p><pre>sudo nano /var/www/html/index.html</pre><p>I added a simple HTML page like:</p><pre>&lt;h1&gt;Hello from my Kali Linux web server!&lt;/h1&gt;</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/911/1*CtL0c0QbR2IQWv12_eYpag.png" /></figure><p>I saved the file and refreshed the browser — my custom page appeared</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/957/1*PKFT5MTGCW8qXD9ear8ptA.png" /></figure><h3>Auto-Start Apache on Boot</h3><p>To make sure the server starts automatically every time I boot Kali:</p><pre>sudo systemctl enable apache2</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/886/1*bh6s3hm4lwVaTRGySdoAEA.png" /></figure><h3>Optional: To access from Host Machine (Port Forwarding / Bridged Mode)</h3><p>If you want to view your web server <strong>from your main computer (outside the VM)</strong>, you can do this:</p><ol><li>In <strong>VirtualBox</strong>, go to <strong>Settings &gt; Network</strong>.</li><li>Change the adapter to <strong>Bridged Adapter</strong> (or use <strong>Port Forwarding</strong> if using NAT).</li><li>Note the IP address of Kali using:</li></ol><pre>ip a</pre><p>Then, on your host browser, visit:</p><pre>http://kali_ip_address</pre><p>Now you can view your web page from the main computer!</p><h3>At last Add a Simple Firewall</h3><p>Kali comes with ufw (Uncomplicated Firewall). I enabled it and allowed Apache:</p><pre>sudo apt install ufw<br>sudo ufw allow &#39;Apache Full&#39;<br>sudo ufw enable</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/457/1*nXfb9_TgA3rnwJy7PGPaAw.png" /></figure><p>That’s it, I now have a fully working web server running <strong>inside Kali Linux</strong> on my <strong>Virtual Machine</strong>. It’s a great way to test and build simple websites, run local tools, or just learn how web hosting works.</p><p>I hope this helped someone! If you’re trying it out too, let me know how it goes.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=0b879f1c6ea7" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Email Analysis: Identifying a Phishing Attempt]]></title>
            <link>https://medium.com/@ajju0075/email-analysis-identifying-a-phishing-attempt-d9f828bfc6d8?source=rss-1d680c0bea34------2</link>
            <guid isPermaLink="false">https://medium.com/p/d9f828bfc6d8</guid>
            <category><![CDATA[scam]]></category>
            <category><![CDATA[header-analysis]]></category>
            <category><![CDATA[malware]]></category>
            <category><![CDATA[phishing-email]]></category>
            <category><![CDATA[email-analysis]]></category>
            <dc:creator><![CDATA[Muhammad Ajmal CA]]></dc:creator>
            <pubDate>Tue, 25 Jun 2024 09:13:07 GMT</pubDate>
            <atom:updated>2024-06-25T12:59:20.617Z</atom:updated>
            <content:encoded><![CDATA[<p>Recently, I received an email that appeared to be from Microsoft Office 365. The email included an attachment. Given that Microsoft typically doesn’t send direct emails with attachments and links, I decided to investigate further. Below, I outline the steps I took to analyze the email and confirm whether it was a phishing attempt.</p><h3>Step-by-Step Analysis</h3><h4>1. Email Headers Verification</h4><p>The first step was to verify if the email was legitimate. To do this, I examined the email headers, which I copied from the email header’s and analyzed using the MX Tool.</p><h4>MX Tool Analysis Result:</h4><p>The analysis revealed that the domain does not have a DKIM signature, indicating potential issues with the email’s authenticity.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*oYwKbP8EiRqnfMPnUSDWiQ.png" /></figure><h4>2. Domain and IP Address Check</h4><p>Next, I checked the domain from which the email originated, “185.192.125.152,” using the IP Abuse site. The domain and IP address were not reported as malicious, but the IP location was suspiciously traced back to the Netherlands. This raised further doubts about the trustworthiness of the domain.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/678/1*zV1Mz2GdNsjO0PvIKQvpRw.png" /></figure><h4>3. Attachment Analysis</h4><p>The email contained an HTML file attachment, which seemed suspicious. To investigate further, I used VirusTotal to scan the file by uploading the html file.</p><h4>VirusTotal Scan Result:</h4><p>The scan identified the file as a trojan, confirming that the attachment was indeed malicious.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*EIqvSLYk4WS8zTsyUNdfrA.png" /></figure><h4>Conclusion</h4><p>From the steps outlined above, it became clear that:</p><p><em>- The domain lacked proper DKIM configuration.<br>- The IP address and domain raised suspicions due to their unusual location.<br>- The attachment was identified as a trojan.</em></p><p>Based on this analysis, I concluded that the email was a phishing attempt designed to steal credentials.</p><p>By using tools such as MX Tool, IP Abuse, and VirusTotal, I was able to thoroughly analyze the email and determine its malicious nature. These steps are crucial for anyone looking to understand and identify phishing emails. Stay vigilant and always verify the authenticity of unsolicited emails, especially those containing attachments or links.</p><p>Thank you, and I hope this guide helps in understanding the process of email analysis.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d9f828bfc6d8" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[5 Alert Strategies: Creating Alert Ideas with MITRE ATT&CK Framework]]></title>
            <link>https://medium.com/@ajju0075/5-alert-strategies-creating-alert-ideas-with-mitre-att-ck-framework-48fe9eff565b?source=rss-1d680c0bea34------2</link>
            <guid isPermaLink="false">https://medium.com/p/48fe9eff565b</guid>
            <category><![CDATA[seim]]></category>
            <category><![CDATA[kibana]]></category>
            <category><![CDATA[defence-strategies]]></category>
            <category><![CDATA[blue-team]]></category>
            <category><![CDATA[mitre-attack-framework]]></category>
            <dc:creator><![CDATA[Muhammad Ajmal CA]]></dc:creator>
            <pubDate>Tue, 11 Jun 2024 06:14:53 GMT</pubDate>
            <atom:updated>2024-06-18T09:35:58.676Z</atom:updated>
            <content:encoded><![CDATA[<p>In this blog, we will explore alert strategies inspired by the MITRE ATT&amp;CK framework that I’ve implemented for detecting security threats using Kibana alerts. I’ve developed five detection ideas designed to identify potential attacks.</p><h3>1. User Discovery (T1033)</h3><h4>Indicators of Compromise (IOCs):</h4><p>User Discovery activities involve querying or listing user account information on a system or network. Key IOCs include commands executed to gather information about logged-in users, enumerating user accounts, or querying directories. Such activities may involve tools and commands such as whoami, net user, net group, and directory queries like LDAP.</p><h4>Formulating the Detection Logic:</h4><p>Monitor command execution and log events that capture user account enumeration or information gathering. Key event sources include Windows Event Logs, such as <strong><em>Event ID 4624</em> </strong>for logon events, <strong><em>Event ID 4768</em> </strong>for Kerberos Ticket Requests, and <strong><em>Event ID 4627</em> </strong>for Group Membership Enumeration. Additionally, Sysmon logs, particularly <strong><em>Event ID 1</em></strong> for process creation, are crucial for detecting such activities. Track changes to commands and activities like whoami, net user, net group, and directory queries.</p><h3>2. Unusual File Modifications (T1070.004 — File Deletion)</h3><h4>Indicators of Compromise (IOCs):</h4><p>Unusual file modifications in critical system directories, such as C:\Windows\System32, can indicate malicious activity. Key IOCs include changes to executable files, scripts, or libraries, particularly outside of normal update schedules. This may involve tools and commands that modify or delete files to cover tracks or disrupt system operations.</p><h4>Formulating the Detection Logic:</h4><p>Monitor file creation and modification events in sensitive directories. Key event sources include Sysmon Event ID 11 for file creation and Event ID 23 for file deletion. Focus on changes to file types commonly associated with malware, such as .exe, .dll, .sys, .bat, and .ps1. Detecting unusual file modifications helps identify and mitigate potential threats before they can execute and cause harm. Implement alerting mechanisms to notify security teams of these changes for immediate investigation.</p><h3>3. System Information Discovery (T1082)</h3><h4>Indicators of Compromise (IOCs):</h4><p>System Information Discovery involves querying or retrieving information about the operating system, hardware, and software configurations. Key IOCs include commands that gather system details, such as systeminfo, hostname, and ipconfig.</p><h4>Formulating the Detection Logic:</h4><p>Monitor command execution and log events that capture system information queries. Key event sources include Windows Event Logs, such as Event ID 4688 for process creation. Additionally, Sysmon logs, particularly Event ID 1 for process creation, are crucial for detecting these activities. Track execution of commands like systeminfo, hostname, and ipconfig. Detecting these activities helps identify potential reconnaissance attempts by adversaries. Implement alerting mechanisms to notify security teams immediately upon detecting such queries for timely investigation and response.</p><h3>4. Credential Dumping (T1003)</h3><h4>Indicators of Compromise (IOCs):</h4><p>Credential Dumping involves extracting credentials from operating systems to obtain user account information. Key IOCs include the use of tools like Mimikatz, and commands that access the Local Security Authority Subsystem Service (LSASS) process memory.</p><h4>Formulating the Detection Logic:</h4><p>Monitor for suspicious process creation and access to sensitive memory areas. Key event sources include Windows Event Logs, such as Event ID 4624 for logon events and Event ID 4688 for process creation. Additionally, Sysmon logs, particularly Event ID 10 for process access, are crucial for detecting these activities. Track the use of tools like Mimikatz and suspicious access to the LSASS process. Detecting these activities helps identify potential attempts to compromise credentials. Implement alerting mechanisms to notify security teams immediately upon detecting such suspicious activities for swift investigation and response.</p><h3>5. Persistence via Scheduled Task/Job (T1053.005)</h3><h4>Indicators of Compromise (IOCs):</h4><p>Persistence via Scheduled Task/Job involves creating or modifying scheduled tasks to maintain access to a system. Key IOCs include the creation or modification of tasks outside of normal administrative activities, often used to execute malicious payloads at scheduled intervals.</p><h4>Formulating the Detection Logic:</h4><p>Monitor for the creation and modification of scheduled tasks. Key event sources include Windows Event Logs, such as Event ID 4698 for new scheduled tasks and Event ID 4702 for modified tasks. Additionally, Sysmon logs, particularly Event ID 1 for process creation and Event ID 5 for process terminated, can be useful. Track the creation and modification of tasks and look for anomalies outside of regular administrative patterns. Detecting these activities helps identify potential persistence mechanisms used by adversaries. Implement alerting mechanisms to notify security teams immediately upon detecting such suspicious activities for prompt investigation and mitigation.</p><h4>Summary</h4><p>This is a test case I created using the MITRE ATT&amp;CK framework. It can be useful for developing alert ideas in ELK Cloud. By implementing these alerts, the system becomes more protective, notifying you when an adversary is attempting to attack. I hope you find it helpful.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=48fe9eff565b" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Altoro Mutual Vulnerability AssessmentAnd Penetration Testing]]></title>
            <link>https://medium.com/@ajju0075/altoro-mutual-vulnerability-assessmentand-penetration-testing-ad50f9ca3f6f?source=rss-1d680c0bea34------2</link>
            <guid isPermaLink="false">https://medium.com/p/ad50f9ca3f6f</guid>
            <category><![CDATA[hacking]]></category>
            <category><![CDATA[vapt]]></category>
            <category><![CDATA[owasp-top-10]]></category>
            <category><![CDATA[web-pen-testing]]></category>
            <category><![CDATA[pentesting]]></category>
            <dc:creator><![CDATA[Muhammad Ajmal CA]]></dc:creator>
            <pubDate>Thu, 02 May 2024 11:46:34 GMT</pubDate>
            <atom:updated>2024-07-09T05:59:10.285Z</atom:updated>
            <content:encoded><![CDATA[<h3><strong>Altoro Mutual Vulnerability Assessment And Penetration Testing VAPT</strong></h3><p><strong>PROJECT SUMMARY</strong></p><p>This document is a comprehensive security assessment of the Altoro Mutual website. The purpose of this assessment is to determine the existing vulnerability and its security risks. The document contains the different vulnerabilities that were found in the assessment process and the mitigation of these vulnerabilities .</p><p><strong>FINDINGS OVERVIEW</strong></p><p>A penetration test was conducted to assess the security of Altoro Mutual. The objective of this penetration test was to simulate a threat actor’s actions by conducting cyber-attacks against Altoro Mutual. The purpose was to uncover any existing application vulnerabilities listed in the OWASP Top 10 checklist that could potentially lead to a breach and allow unauthorized access to sensitive data. Automated and manual exploitation techniques were employed to identify and verify any issues present withinAltoro Mutual’s Application. A brief technical overview is listed below:</p><p><strong>Scope:</strong><a href="https://altoromutual.com/"><strong>https://altoromutual.com/</strong></a><strong> Web pentesting</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/669/1*Wbqoe2Xqi8hPQ5mNIhSquQ.png" /></figure><p><strong>Score severity</strong></p><p>10–9 critical</p><p>8.9–7 high</p><p>6.9–4 medium</p><p>3.9–0.1 low</p><p><strong>Final Report</strong></p><p><strong>METHODOLOGY</strong></p><p>The testing methods that are widely adopted in the cyber security assessment industry are used. This includes 3 phases: Vulnerability Assessment, Exploitation, and Reporting/Mitigation.</p><p>During these phases, both automated and manual audit techniques ensure the best possible results.</p><p><strong>Vulnerability Assessment</strong></p><p>The vulnerability assessment is done to verify that a vulnerability exists that may be exploitable by an attacker. All vulnerabilities listed in the OWASP Top 10 have been found. Through thorough examination and testing, each vulnerability has been successfully identified, ensuring a complete assessment of the Application security posture.</p><p><strong>SQL Injection Vulnerability</strong></p><p><strong>CVSS Score:10.0</strong></p><p><strong>Vulnerable instance:</strong><a href="http://altoromutual.com/login.jsp">https://altoromutual.com/login.jsp</a></p><p><strong>Description:</strong></p><p>SQL Injection is a vulnerability found in web applications that arises when user-supplied input is improperly sanitized and directly incorporated into SQL queries. In the context of the provided scenario, the SQL Injection vulnerability exists in the login page of the application, allowing attackers to bypass authentication mechanisms and gain unauthorized access, potentially as an administrator. Attackers exploit this vulnerability by injecting malicious SQL commands into the login form, manipulating the SQL query executed by the application, and thereby bypassing the authentication process.</p><p><strong>Impact:</strong></p><p>The impact of the SQL Injection vulnerability on the login page, allowing users to login as the admin, is severe. Attackers can exploit this vulnerability to gain unauthorized access to sensitive information, manipulate data, or perform unauthorized actions within the application. By injecting malicious SQL commands, attackers can potentially bypass authentication mechanisms entirely, granting them unrestricted access to the application’s functionalities, including those reserved for administrators. This can lead to unauthorized data access, modification, or deletion, as well as compromise of other users’ accounts and exposure of sensitive information. Moreover, the exploitation of SQL Injection can damage the reputation of the affected application, erode user trust, and lead to regulatory penalties or legal consequences.</p><p><strong>Mitigation:</strong></p><p>To mitigate the SQL Injection vulnerability on the login page, organizations should implement secure coding practices and input validation mechanisms. User-supplied input should be properly sanitized and validated before being used in SQL queries, using parameterized queries or prepared statements to separate SQL code from user input. Additionally, input validation should be performed on both client and server sides to prevent malicious input from reaching the database. Web application firewalls (WAFs) can also be employed to detect and block SQL Injection attacks in real-time. Regular security testing, including vulnerability scanning and penetration testing, should be conducted to identify and remediate SQL Injection vulnerabilities in the application. Furthermore, educating developers about secure coding practices and the dangers of SQL Injection can help prevent similar vulnerabilities from being introduced in future development efforts.</p><p><strong>Proof of Concept (PoC):</strong></p><p><strong>Step 1:</strong>Navigate to the login page and attempt to disrupt the query by inserting a single quote in the username field. This action should trigger an error.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/627/0*2c2GJ6tkzCNuffOT" /></figure><p><strong>Step 2:</strong>After encountering the error, it becomes apparent that the website is susceptible to SQL injection. In order to bypass the authentication mechanism, you can inject a payload such as `’ OR 1=1 — ` to return a true statement.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/627/0*uS92ZrW9J62vaO_s" /></figure><p><strong>Step 3:</strong> Upon successfully injecting the payload, access to the first user in the database, typically the admin user, will be granted.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/768/0*MJLufGb83ACWLR8Y" /></figure><p><strong>Lack of HTTP Strict Transport Security (HSTS)</strong></p><p><strong>CVSS Score: 8.2</strong></p><p><strong>Description</strong>:</p><p>The lack of HTTP Strict Transport Security (HSTS) vulnerability pertains to the absence or misconfiguration of the HSTS mechanism, which is designed to enforce the use of HTTPS connections and mitigate security risks associated with unsecured HTTP traffic. Without HSTS, websites are susceptible to downgrade attacks, where adversaries can intercept and manipulate communication between users and servers, compromising the confidentiality and integrity of transmitted data.</p><p><strong>Impact</strong>:</p><p>The vulnerability exposes organizations to various security risks, including man-in-the-middle attacks, session hijacking, and data tampering. Attackers can exploit the absence of HSTS to intercept sensitive information exchanged between users and servers, potentially leading to unauthorized access to user accounts, disclosure of confidential data, and manipulation of online sessions. Furthermore, the lack of HSTS compliance may result in regulatory non-compliance, leading to potential legal and financial repercussions.</p><p><strong>Mitigation</strong>:</p><p>To mitigate the lack of HSTS vulnerability, organizations should promptly enable and correctly configure HSTS headers on their web servers. This involves specifying appropriate values for directives such as max-age and includeSubDomains to enforce HTTPS connections and extend HSTS protection across subdomains. Additionally, organizations should implement web application firewalls (WAFs) to detect and block suspicious traffic.</p><p><strong>PoC (Proof of Concept):</strong></p><p><strong>Step 1:</strong> Send an HTTP request using curl</p><p>curl -I <a href="http://altoromutual.com/">http://altoromutual.com/</a></p><p><strong>Step 2:</strong> Inspect the response headers</p><p>Look for the presence of the Strict-Transport-Security header in the response. In this case, it is not present.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/602/0*_4Jb2Nbi4ephkZ8x" /></figure><p><strong>Step 3:</strong> Determine HSTS implementation</p><p>Since the Strict-Transport-Security header is not present in the response, it indicates that HTTP Strict Transport Security (HSTS) is not implemented on the server for the domain altoromutual.com</p><p><strong>Insecure Direct Object Reference (IDOR) Leading to Unauthorized Access of Bank Account Balances</strong></p><p><strong>CVSS Score: 6.56.5</strong></p><p><strong>Description:</strong></p><p>Insecure Direct Object Reference (IDOR) is a vulnerability that occurs when an application exposes internal implementation objects such as files, directories, or database records directly to users. In the context of the provided scenario, the “showAccount” functionality of the Altoro Mutual banking application is vulnerable to IDOR. By manipulating the “id” parameter in the URL, an authenticated user can access the bank account details of other users, potentially leading to unauthorized disclosure of sensitive information.</p><p><strong>Impact:</strong></p><p>The impact of an IDOR vulnerability in a banking application is severe, as it enables unauthorized users to access and view sensitive financial data belonging to other users. Exploitation of this vulnerability can lead to breaches of confidentiality, privacy violations, and financial fraud. Attackers could leverage the exposed account details to conduct identity theft, unauthorized fund transfers, or targeted phishing attacks, jeopardizing the trust and financial security of affected users.</p><p><strong>Mitigation:</strong></p><p>To mitigate the IDOR vulnerability, Altoro Mutual should implement proper access controls and validation mechanisms to restrict users’ access to only their own account data. This includes implementing server-side authorization checks to ensure that users can only access resources associated with their authenticated session. Additionally, sensitive operations such as viewing account details should require strong authentication and authorization measures, such as multi-factor authentication and role-based access control. Regular security testing, including code reviews and penetration testing, should be conducted to identify and remediate IDOR vulnerabilities in the application. Furthermore, user education and awareness campaigns can help users understand the importance of protecting their account credentials and recognizing potential security threats.</p><p><strong>Proof of Concept (PoC):</strong></p><p><strong>Step 1:</strong> Begin by logging in with user privileges and navigate to the following URL: <a href="https://altoromutual.com/bank/main.jsp">https://altoromutual.com/bank/main.jsp</a> Once on the page, proceed to click on the Go button on “View Account Details” option.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1019/0*2pVJ7Oi4ugagRsFw" /></figure><p><strong>Step 2: </strong>After accessing the “View Account Details” page, manipulate the URL parameter “id” to another user account id.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*mmVvoOxRpqCGrg1w" /></figure><p><strong>Step 3: </strong>Upon modifying the URL parameter “id” to view the account history details of another user, you will be able to access information pertaining to their account history, including transactions, balances, and other relevant financial data.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/786/0*-V3ulfNE9LH9EW3n" /></figure><p><strong>Lack of rate limiting</strong></p><p><strong>CVSS Score:9.8</strong></p><p><strong>Vulnerable instance:</strong><a href="http://altoromutual.com/login.jsp">https://altoromutual.com/login.jsp</a></p><p><strong>Description:</strong></p><p>The lack of rate limit vulnerability on the login page occurs when there are no restrictions placed on the number of login attempts a user can make within a specific timeframe. Without rate limiting, attackers can conduct brute-force or credential stuffing attacks by repeatedly attempting to guess usernames and passwords until successful authentication is achieved. This vulnerability is particularly concerning as it provides adversaries with unrestricted access to attempt unauthorized logins, increasing the likelihood of successful account compromise.</p><p><strong>Impact:</strong></p><p>The impact of the lack of rate limit on the login page is significant, as it exposes the application to various security risks. Attackers can exploit this vulnerability to launch automated attacks, such as brute-force or credential stuffing, to gain unauthorized access to user accounts. Successful exploitation may lead to account takeover, unauthorized data access, identity theft, or fraudulent activities. Moreover, prolonged attacks may overwhelm the authentication system, causing denial-of-service (DoS) conditions, disrupting service availability, and impacting legitimate users.</p><p><strong>Mitigation:</strong></p><p>To mitigate the lack of rate limit vulnerability on the login page, it is essential to implement rate limiting mechanisms that restrict the number of login attempts allowed per user or IP address within a defined time interval. Organizations can configure thresholds for failed login attempts and enforce temporary lockouts or CAPTCHA challenges for users who exceed these limits. Additionally, implementing multi-factor authentication (MFA) can add an extra layer of security to mitigate the risk of account compromise even if credentials are successfully guessed. Regular monitoring and logging of login attempts can help identify and respond to suspicious activities promptly. Training users on secure password practices and encouraging the use of strong, unique passwords can also enhance the overall security posture of the application.</p><p><strong>Proof of Concept (PoC):</strong></p><p><strong>Step 1:</strong> Attempt to log in as a user and capture the request. Send the request to the intruder and set the target as “uid” and “passw” values. Start the attack using the Pitchfork mode with the word list “common.txt”.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*8GXuGaCoLN7YtWG7" /></figure><p><strong>Step 3 :</strong> After completing the attack, analyze the response. All status codes returned are 302. To determine whether the attack was successful, analyze the response length. The response length is consistently 126, except for the 31st request, which has a response length of 325.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*f1-aH0cNwq-_2Y0u" /></figure><p><strong>Step 3 :</strong> After analyzing the response, it’s evident that the web server sent the cookie and the authentication was successful, leading to a redirection to the main page. In this scenario, we can conclude that the website lacks rate limiting measures.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/731/0*0eJUXnui2Sag-71C" /></figure><p>______________________________________________________________________</p><p><strong>Account Enumeration and Guessable User Account IDs</strong></p><p><strong>CVSS Score: 7.5</strong></p><p><strong>Vulnerable instance:</strong><a href="https://altoromutual.com/admin/admin.jsp">https://altoromutual.com/admin/admin.jsp</a></p><p><strong>Description:</strong></p><p>This vulnerability arises when an application advises or enforces a predictable username pattern, such as using the first initial followed by the last name, for user creation. While this may seem convenient for administrators, it introduces a security risk as it allows attackers to easily guess valid usernames based on publicly available information, such as users’ names. By adhering to the suggested pattern, every user account follows the same predictable format, which can be exploited by attackers to launch targeted attacks or unauthorized access attempts.</p><p><strong>Impact:</strong></p><p>The predictable username pattern introduces significant security risks to the application and its users. By adhering to a standardized format of first initial followed by last name, attackers can easily deduce valid usernames, exploiting publicly available information. This vulnerability increases the likelihood of successful brute force attacks, as attackers can systematically guess usernames and attempt to compromise user accounts. Furthermore, it compromises user privacy and confidentiality, enabling attackers to target specific individuals based on their easily guessable usernames. Overall, the predictable username pattern undermines the security posture of the application, potentially leading to unauthorized access to sensitive information and resources.</p><p><strong>Mitigation:</strong></p><p>To mitigate the risks associated with the predictable username pattern, several measures should be implemented. First, revise the user creation guidelines to recommend more randomized or complex username patterns, reducing predictability and making it harder for attackers to guess valid usernames. Provide administrators with flexibility in selecting usernames, allowing them to deviate from the suggested pattern if necessary. Additionally, enhance the application’s security posture by implementing additional measures such as account lockout policies or CAPTCHA challenges to deter brute force attacks. Regular monitoring of user account activities should be conducted to detect and respond to any suspicious behavior or unauthorized access attempts promptly. Lastly, educate administrators and users about the importance of selecting unique and non-predictable usernames to bolster the overall security of the application.</p><p><strong>Proof of Concept (PoC):</strong></p><p><strong>Step 1:</strong> Login as an admin and navigate to the user creation section.</p><p><strong>Step 2 :</strong> Observe the policy guidance message advising administrators to adhere to a specific username format: “It is highly recommended that you leave the username as first initial last name.”</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*3IlSLSHH__6PvL6X" /></figure><p><strong>Default Credentials</strong></p><p><strong>CVSS Score:9.8</strong></p><p><strong>Vulnerable instance:</strong><a href="http://altoromutual.com/login.jsp">https://altoromutual.com/login.jsp</a></p><p><strong>Description:</strong></p><p>The vulnerability of default credentials arises when an application or system is deployed with pre-configured usernames and passwords that are widely known or easily guessable. Often, developers or administrators may use default credentials for convenience during deployment or testing, but neglect to change them before production use. Attackers can exploit this oversight to gain unauthorized access to the system or application, as default credentials are well-documented and widely available. This vulnerability poses a significant security risk as it provides attackers with a straightforward method to bypass authentication controls and potentially compromise the entire system or sensitive data.</p><p><strong>Impact:</strong></p><p>The utilization of default credentials poses a critical security threat to systems and applications. By leveraging widely known or easily guessable default usernames and passwords, attackers can bypass authentication controls with ease, gaining unauthorized access to sensitive resources. This unauthorized access opens the door to a range of malicious activities, including data theft, manipulation, or destruction, as well as the potential compromise of the entire system. Default credentials introduce a significant risk, particularly in networked environments or internet-facing systems, where they can be readily discovered and exploited by malicious actors, leading to severe consequences for the organization’s security posture and data integrity.</p><p><strong>Mitigation:</strong></p><p>To address the risk posed by default credentials, robust measures must be implemented to safeguard systems and applications. It is imperative to ensure that default credentials are promptly changed to unique, strong, and complex passwords before deploying any system or application into production. Establishing and enforcing stringent password management policies and practices is essential to prevent the inadvertent use or retention of default credentials. Regular audits should be conducted to identify and eliminate any instances of default credentials, reducing the likelihood of unauthorized access. Additionally, educating administrators and users about the importance of employing strong, unique passwords and avoiding default or easily guessable credentials is crucial for enhancing security awareness and adherence to best practices. Furthermore, the implementation of advanced authentication mechanisms such as multi-factor authentication (MFA) can provide an additional layer of security, mitigating the risk of unauthorized access, even in the event of default credential compromise. By implementing these mitigation measures, organizations can effectively address the vulnerability posed by default credentials and bolster their overall security posture.</p><p><strong>Proof of Concept (PoC):</strong></p><p><strong>Step 1:</strong>Navigate to the sign-in page and log in as an administrator. Currently, the administrator password has not been changed, and you can use the default common username and password combination, such as username=admin and password=admin, to log in as an admin user in this application.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/961/0*GJeC6yHy0Us9_A-V" /></figure><p><strong>Absence of Multi-Factor Authentication (MFA) Implementation</strong></p><p><strong>CVSS Score:8.1</strong></p><p><strong>Vulnerable instance:</strong><a href="http://altoromutual.com/login.jsp">https://altoromutual.com/login.jsp</a></p><p><strong>Description:</strong></p><p>The “Absence of Multi-Factor Authentication (MFA) Implementation” vulnerability refers to the lack of a secondary authentication mechanism beyond the traditional username and password combination. Multi-factor authentication (MFA) adds an extra layer of security by requiring users to provide additional evidence of identity, such as a one-time password (OTP) sent to a mobile device or a biometric scan, before gaining access to an account or system. The absence of MFA leaves user accounts vulnerable to unauthorized access through credential theft, phishing attacks, or brute-force attempts, as attackers only need to compromise the user’s password to gain entry.</p><p><strong>Impact:</strong></p><p>The absence of Multi-Factor Authentication (MFA) alongside weak password policies and the lack of rate limiting on the website’s login page significantly increases the risk of unauthorized access. Without MFA, attackers can easily exploit weak passwords or conduct brute-force attacks without restriction. This raises the likelihood of account takeovers, unauthorized data access, and service disruptions. Moreover, the organization’s compliance with regulatory standards may be compromised, leading to potential legal consequences and financial penalties. It’s crucial to address these vulnerabilities promptly to enhance the website’s security. Furthermore, regulatory compliance requirements such as GDPR, HIPAA, or PCI DSS may not be met without adequate MFA measures in place, potentially resulting in legal consequences and fines.</p><p><strong>Mitigation:</strong></p><p>To mitigate the absence of MFA implementation, organizations should prioritize the adoption of MFA across all systems and applications, especially those handling sensitive data or providing access to critical resources. This involves deploying MFA mechanisms such as OTP tokens, biometric authentication, or push notifications to users’ registered devices. Additionally, organizations should enforce MFA as a mandatory requirement for accessing accounts, systems, and privileged resources. User awareness and training programs should emphasize the importance of MFA and educate users on how to enable and use MFA effectively. Regular security assessments and audits should be conducted to ensure compliance with MFA implementation standards and to identify and address any vulnerabilities or weaknesses in the authentication process. By implementing MFA, organizations can significantly enhance their security posture and mitigate the risk of unauthorized access and account compromise.</p><p><strong>Proof of Concept (PoC):</strong></p><p><strong>Step 1: </strong>Navigate to the Signin page and Login with the username and password, in here i am using the username:jsmith and the password:demo1234</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/957/0*7D14-pna_aIVo4yY" /></figure><p><strong>Step 2: </strong>After entering the user credential it’s validating without the MFA(Multi Factor Authentication) and navigating to the main page.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1002/0*td8Mb0LQIWCUdv8l" /></figure><p><strong>Session Fixation Vulnerability in Website Logout Mechanism</strong></p><p><strong>CVSS Score:7.1</strong></p><p><strong>Vulnerable instance:</strong><a href="http://altoromutual.com/">https://altoromutual.com</a></p><p><strong>Description:</strong></p><p>The website’s logout mechanism fails to properly invalidate the session identifier upon user logout. Despite redirecting users to the login page after logout, it allows users to navigate back to the previously accessed secure area without requiring re authentication, thereby exposing a session fixation vulnerability.</p><p><strong>Impact:</strong></p><p>The impact of the session fixation vulnerability in the website’s logout mechanism is significant. Attackers can exploit this vulnerability to hijack active user sessions, potentially gaining access to sensitive user data, such as personal information, financial details, or login credentials. By fixing the session identifier, attackers can impersonate legitimate users and perform unauthorized actions on their behalf, leading to account compromise, data breaches, and privacy violations. Additionally, the compromised sessions may remain accessible even after users attempt to log out, further exacerbating the risk of unauthorized access and exploitation.</p><p><strong>Mitigation:</strong></p><p>To mitigate the session fixation vulnerability in the website’s logout mechanism, organizations should implement robust session management practices. This includes properly invalidating session identifiers upon logout and generating new session identifiers for subsequent user sessions. Additionally, organizations should enforce secure session handling techniques, such as using random and unpredictable session identifiers, implementing secure cookie attributes, and employing mechanisms to detect and prevent session fixation attacks, such as session regeneration. Regular security testing, including vulnerability assessments and penetration testing, can help identify and remediate session fixation vulnerabilities in the website’s logout mechanism. Furthermore, educating users about secure browsing practices, such as logging out from websites after use and avoiding sharing session identifiers, can help mitigate the risk of session fixation attacks.</p><p><strong>Proof of Concept (PoC):</strong></p><p><strong>Step 1: </strong>Login as a valid user and sign off from the application.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*9RuJZnEoTdMOXHyg" /></figure><p><strong>Step 2:</strong> After signing off, you will be redirected to the home page. If you then click the browser’s back button, you’ll be taken to the previous page with full access to the privileges of the logged-in user.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*lsOP73CSct1jslLR" /></figure><p><strong>Step 3: </strong>You can observe that the “JSESSIONID” still exists in the browser even after signing off by using the application option in the browser’s developer tools.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*LSKenLWiqIHDd6Xs" /></figure><p><strong>Improper Error Handling</strong></p><p><strong>CVSS Score:5.0</strong></p><p><strong>Vulnerable instance:</strong><a href="http://altoromutual.com/bank/transfer.jsp">https://altoromutual.com/bank/transfer.jsp</a></p><p><strong>Description:</strong></p><p>The “Improper Error Handling” vulnerability refers to a weakness in a web application’s error handling mechanisms, where error messages or stack traces containing sensitive information are disclosed to users or attackers. This vulnerability occurs when the application fails to properly handle and sanitize error messages, exposing internal system details, such as database queries, file paths, or configuration settings, to unauthorized parties. Attackers can exploit this vulnerability to gain insights into the application’s infrastructure and potentially launch further attacks, such as SQL injection, directory traversal, or information disclosure.</p><p><strong>Impact:</strong></p><p>The impact of improper error handling can be significant, as it exposes sensitive information that attackers can exploit to compromise the security of the application. Exposed error messages may reveal valuable insights into the application’s architecture, making it easier for attackers to identify and exploit vulnerabilities. Furthermore, sensitive data disclosed in error messages, such as user credentials, session tokens, or database queries, can be leveraged by attackers to conduct unauthorized access, data manipulation, or privilege escalation attacks. Moreover, the disclosure of internal system details may violate regulatory compliance requirements, leading to legal consequences and reputational damage for the organization.</p><p><strong>Mitigation:</strong></p><p>To mitigate the improper error handling vulnerability, organizations should implement secure error handling practices throughout the application’s codebase. This includes configuring the application to display generic error messages to users, rather than exposing detailed system information. Additionally, error messages should be logged securely and only accessible to authorized personnel for debugging and troubleshooting purposes. Input validation and output encoding should be performed rigorously to prevent injection attacks and sanitize user-supplied data before displaying it in error messages. Regular security reviews, code audits, and penetration testing can help identify and remediate improper error handling vulnerabilities in the application. Furthermore, educating developers about secure coding practices and the importance of error handling can help prevent similar vulnerabilities from being introduced in future development efforts.</p><p><strong>Proof of Concept (PoC):</strong></p><p><strong>Step 1: </strong>Proceed to the “Transfer Funds” section and attempt to initiate a transfer to any bank account.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*3Ey85Nh9W2cUqphF" /></figure><p><strong>Step 2: </strong>Capture the request in Burp and change the value of the “transferAmount” parameter to a string value, such as “asdfasdf.” After modifying the parameters, forward the request and examine the application’s response.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*G_bUxtE32ObQfX0t" /></figure><p><strong>Step 3: </strong>The application lacks proper validation for string values, as evident from the error it displays. This error exposes system information, revealing potential vulnerabilities in the application.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*LcaSUrm7T2VFV1k5" /></figure><p><strong>Reflected XSS</strong></p><p><strong>CVSS Score:6.5</strong></p><p><strong>Vulnerable instance:</strong><a href="http://altoromutual.com/search.jsp">https://altoromutual.com/search.jsp</a></p><p><strong>Description:</strong></p><p>Reflected Cross-Site Scripting (XSS) is a vulnerability found in web applications where user-supplied input is echoed back in the application’s response without proper sanitization. In the context of the provided scenario, the Reflected XSS vulnerability occurs in the application’s search bar query input field. Attackers can exploit this vulnerability by injecting malicious scripts or payloads into the search query, which are then executed within the context of other users’ sessions when they view the search results. This allows attackers to steal session cookies, perform unauthorized actions on behalf of users, or deface the website.</p><p><strong>Impact:</strong></p><p>The impact of the Reflected XSS vulnerability in the application’s search bar query input field is significant. Attackers can exploit this vulnerability to execute malicious scripts in the context of other users’ browsers, leading to various security risks such as session hijacking, data theft, or website defacement. By tricking users into clicking on a crafted link or visiting a specially crafted webpage, attackers can execute arbitrary code, steal sensitive information (such as session tokens or login credentials), or redirect users to phishing sites. Moreover, the exploitation of Reflected XSS can damage the reputation of the affected website, erode user trust, and lead to financial losses or regulatory penalties.</p><p><strong>Mitigation:</strong></p><p>To mitigate the Reflected XSS vulnerability in the application’s search bar query input field, organizations should implement robust input validation and output encoding mechanisms. Input validation should be performed to ensure that user-supplied input is sanitized and conforms to expected formats, rejecting any input that contains suspicious characters or patterns indicative of XSS payloads. Additionally, output encoding should be applied to dynamically generated content before rendering it in the response, preventing malicious scripts from being executed in users’ browsers. Security headers, such as Content Security Policy (CSP), can also be implemented to restrict the sources from which scripts can be loaded, further mitigating the risk of XSS attacks. Regular security testing, including vulnerability scanning and penetration testing, should be conducted to identify and remediate XSS vulnerabilities in the application. Furthermore, educating developers about secure coding practices and the dangers of XSS can help prevent similar vulnerabilities from being introduced in future development efforts.</p><p><strong>Proof of Concept (PoC):</strong></p><p><strong>Step 1:</strong>Navigate to the search bar and input a HTML element into the search input field.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/530/0*3SI2IJ9GwX4zCOlu" /></figure><p>S<strong>tep 2:</strong> intercept the request and resend it to Repeater. Upon sending the request, observe that the application returns the query as an HTML element, indicating that the search bar is vulnerable to reflected XSS.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*hoBuXhjlkAJVojpy" /></figure><p><strong>ClickJacking</strong></p><p><strong>CVSS Score:5.9</strong></p><p><strong>Vulnerable instance:</strong><a href="http://altoromutual.com/">https://altoromutual.com</a></p><p><strong>Description:</strong></p><p>Clickjacking, also known as UI redress attack or user interface (UI) deception, is a security vulnerability that occurs when an attacker overlays a transparent layer, or “frame,” over a legitimate website or web application, deceiving users into clicking on elements they did not intend to interact with. This can lead to unintended actions being performed by the user without their knowledge or consent, such as making purchases, changing account settings, or revealing sensitive information.</p><p><strong>Impact:</strong></p><p>The impact of Clickjacking can be significant, as it can lead to various security risks and consequences. By tricking users into clicking on invisible or disguised elements overlaid on legitimate web pages, attackers can perform actions on behalf of the user without their consent. This could include transferring funds, submitting forms, or sharing sensitive information. Furthermore, Clickjacking attacks can be used to hijack user sessions, execute malicious scripts, or redirect users to phishing websites, leading to account compromise, data theft, or financial losses. Additionally, Clickjacking can undermine user trust in the affected website or application, resulting in reputational damage and loss of credibility.</p><p><strong>Mitigation:</strong></p><p>To mitigate Clickjacking attacks, organizations should implement security measures such as frame-busting scripts, X-Frame-Options headers, and Content Security Policy (CSP) directives. Frame-busting scripts prevent their web pages from being embedded within frames on other sites, thwarting Clickjacking attempts. X-Frame-Options headers allow website owners to control whether their site can be embedded within frames on other domains. CSP directives, particularly the frame-ancestors directive, specify which domains are allowed to embed the website in frames, further restricting Clickjacking attacks. Additionally, user education and awareness campaigns can help users recognize and avoid Clickjacking attempts, such as advising them to avoid clicking on suspicious or unexpected elements on web pages. Regular security testing, including vulnerability assessments and penetration testing, can also help identify and remediate Clickjacking vulnerabilities in web applications.</p><p><strong>Proof of Concept (PoC):</strong></p><p><strong>Step 1:</strong>Create a basic HTML page featuring an iframe element with the target website’s link embedded within it.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/959/0*nVk1zxgj446YF3QH" /></figure><p><strong>Step 2:</strong>Accessing the created HTML page and observing the target website loading within the iframe confirms that the website is vulnerable to clickjacking</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/918/0*daPccwBlnxRMRWYO" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ad50f9ca3f6f" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>