<?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 Boar on Medium]]></title>
        <description><![CDATA[Stories by Boar on Medium]]></description>
        <link>https://medium.com/@cyberboar?source=rss-2be916b3341c------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*P22fbFTVcQylpkAuiARTsQ.jpeg</url>
            <title>Stories by Boar on Medium</title>
            <link>https://medium.com/@cyberboar?source=rss-2be916b3341c------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sun, 22 Nov 2026 10:53:17 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@cyberboar/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[TryHackMe | The Greenholt Phish Write-up]]></title>
            <link>https://medium.com/@cyberboar/tryhackme-the-greenholt-phish-write-up-9c3bdb407a03?source=rss-2be916b3341c------2</link>
            <guid isPermaLink="false">https://medium.com/p/9c3bdb407a03</guid>
            <dc:creator><![CDATA[Boar]]></dc:creator>
            <pubDate>Mon, 17 Mar 2025 00:57:21 GMT</pubDate>
            <atom:updated>2025-03-17T01:03:35.589Z</atom:updated>
            <content:encoded><![CDATA[<p>An easy rated room to learn those new-found phishing skills!</p><p>Once you have started the machine, we are ready to begin.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/891/1*NQTOlakb-q1wpX7QGVxLqA.png" /></figure><p>Begin by taking the challenge.eml file and rightclick &gt; Open With Other Application &gt; Thunderbird Mail.</p><h4>What is the <strong>Transfer Reference Number</strong> listed in the email’s <strong>Subject</strong>?</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/862/1*7UwKledINYdpHEU4nYbAZQ.png" /></figure><p>This can be found by inspecting the email’s subject in Thunderbird.</p><blockquote>Answer: 09674321</blockquote><h4>What is his email address?</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/862/1*TcZSYKUJYiyXF5SGLA7E7g.png" /></figure><p>Again, found in Thunderbird when opening the email.</p><blockquote>Answer: Mr. James Jackson</blockquote><h4>What email address will receive a reply to this email?</h4><p>Now we want to inspect the email’s headers to find more information about it. We can do this by:</p><blockquote>Answer: info.mutawamarine@mail.com</blockquote><h4>What is the Originating IP?</h4><blockquote>Answer: 192.119.71.157</blockquote><h4>Who is the owner of the Originating IP? (Do not include the “.” in your answer.)</h4><p>We can plug our IP found in the last question into who.is to lookup the owner.</p><h4>What is the SPF record for the Return-Path domain?</h4><p>Looking for the Return-Path domain in the header, we can plug that into a usful tool like <a href="https://mxtoolbox.com/SuperTool.aspx?action=spf%3amutawamarine.com&amp;run=toolpage">this</a></p><h4>What is the DMARC record for the Return-Path domain?</h4><p>Using the same site as <a href="https://mxtoolbox.com/dmarc.aspx">before</a>, we can add our domain to see all the DMARC information.</p><h4>What is the name of the attachment?</h4><p>This can be found in the email’s source, by pressing CTRL + F and searching for attachment .</p><h4>What is the SHA256 hash of the file attachment?</h4><p>Save the file somewhere accessible like the desktop (in a real analysis, we would have a dedicated space for assets).</p><p>Open a terminal here by right clicking on your desktop (or cd to your Desktop.</p><p>By using the command sha256sum *YOUR FILE* we can quickly generate the hash for our file — giving us the answer.</p><h4>What is the attachments file size? (Don’t forget to add “KB” to your answer, <strong>NUM KB</strong>)</h4><p>To be honest, I used `ls -lh to list the files with their file sizes in “human readable format” A.K.A with KB/MB.</p><p>However THM didn’t like my answer and the hint recommended plugging the hash into an online resource so thats what I did.</p><p>I pasted the hash into VirusTotal and got an answer that worked.</p><h4>What is the actual file extension of the attachment?</h4><p>In the same terminal, we can check a file’s extension using the handy command file --extension *file*</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=9c3bdb407a03" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[TryHackMe | Disgruntled Write-up]]></title>
            <link>https://medium.com/@cyberboar/tryhackme-disgruntled-4c0ec35e3e3e?source=rss-2be916b3341c------2</link>
            <guid isPermaLink="false">https://medium.com/p/4c0ec35e3e3e</guid>
            <dc:creator><![CDATA[Boar]]></dc:creator>
            <pubDate>Sun, 26 Jan 2025 01:16:41 GMT</pubDate>
            <atom:updated>2025-03-10T13:42:19.098Z</atom:updated>
            <content:encoded><![CDATA[<p>An easy room where we test your Linux forensic skills!</p><p>You can connect into the machine via the virtual machine in split-screen mode, or connect via SSH (like me!)</p><h3>Task 1</h3><p>We can just click to continue :)</p><h3>Task 2</h3><p>We can just click to continue :)</p><h3>Task 3:</h3><h4>The user installed a package on the machine using elevated privileges. According to the logs, what is the full COMMAND?</h4><p>To view these logs, we can check the auth.log file. This sits in var/log/auth.log .</p><p>To find the log that contains the install command, we can use grep to search for this phrase within the var/log/auth.log file.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*n65yWMG4ZlR-O04hGNfDZw.png" /></figure><h4>What was the present working directory (PWD) when the previous command was run?</h4><p>This can be seen in the same log from our previous search.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*4NlyWBGQTMzU4fqWlBPyLA.png" /></figure><h3>Task 4:</h3><h4>Which user was created after the package from the previous task was installed?</h4><p>sudo grep &#39;useradd&#39; /var/log/auth.log We can run this command to search for &#39;useradd&#39; within the authentiatiton log file.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/888/1*ZmvlaExB7i05ovU5i3rEIg.png" /></figure><h4>A user was then later given sudo priveleges. When was the sudoers file updated? (Format: Month Day HH:MM:SS)</h4><p>By using the command: sudo grep &#39;visudo&#39; /var/log/auth.log we get returned any logs that contain the phrase visudo . This is used to edit the /etc/sudoers file, allowing us to see when the file was updated.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/506/1*w0dFCb0hosaZIlYn4mUihQ.png" /></figure><h4>A script file was opened using the “vi” text editor. What is the name of this file?</h4><p>Again I searched the auth.log file using grep to see what commands contained “Vi”.</p><p>sudo grep &#39;vi&#39; /var/log/auth.log</p><p>We can see the answer here.</p><h3>Task 5:</h3><h4>What is the command used that created the file bomb.sh?</h4><p>As we know from task 4, the user it-admin was given sudo privileges.</p><p>We will begin our search there.</p><p>We can check the command history for this user to see what they have run by runninng cat /home/it-admin/.bash_history .</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/490/1*oXf98VWA84sACl1kTJc9kA.png" /></figure><h4>The file was renamed and moved to a different directory. What is the full path of this file now?</h4><p>The previous command revealed that sudo vi bomb.sh was called.</p><p>vi being the Vim editor. Thankfully, we can check the .viminfo file for any traces of the bomb.sh being edited (or renamed in our case).</p><p>We get a hit and see what the file has been renamed to.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/444/1*Pwh8eHPDciFnogNxPSd8Vg.png" /></figure><h4>When was the file from the previous question last modified? (Format: Month Day HH:MM)</h4><p>Now we know where this new file is, we can cd /bin to head to where it is now located to figure this out.</p><p>By running stat os-update.sh we can see when the file was last modified and get our answer.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/621/1*-BLp9ylbJo1hEc6VKg_6Zg.png" /></figure><h4>What is the name of the file that will get created when the file from the first question executes?</h4><p>By investigating the file os-update.sh with the cat command, we can get the answer.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/866/1*AaP_9SWiHCsDnTjfacYBRQ.png" /></figure><h3>Task 6:</h3><h4>At what time will the malicious file trigger? (Format: HH:MM AM/PM)</h4><p>We can check for any scheduled tasks for our os-update.sh file for searching for any reference of within any cron related directories by using the wildcard: /etc/cron*</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/522/1*lAhCCTQ735ba52ZeKMrong.png" /></figure><p>We can check something like <a href="https://crontab.guru/">https://crontab.guru/</a> to help us understand the cron sytax.</p><p>We get our answer there! :)</p><h3>Task 7:</h3><h4>I’m kidding, of course! But you did good, kid.</h4><p>Click to complete!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4c0ec35e3e3e" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Try Hack Me — Brains Write-up]]></title>
            <link>https://medium.com/@cyberboar/try-hack-me-brains-write-up-9a32e6b4d5d1?source=rss-2be916b3341c------2</link>
            <guid isPermaLink="false">https://medium.com/p/9a32e6b4d5d1</guid>
            <category><![CDATA[tryhackme]]></category>
            <category><![CDATA[ctf]]></category>
            <category><![CDATA[splunk]]></category>
            <dc:creator><![CDATA[Boar]]></dc:creator>
            <pubDate>Fri, 10 Jan 2025 23:48:57 GMT</pubDate>
            <atom:updated>2025-01-10T23:48:57.956Z</atom:updated>
            <content:encoded><![CDATA[<h3>Try Hack Me — Brains Write-up</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/336/1*btG3oJiMOem_cavOj3ORrA.png" /></figure><p>This is an easy classified CTF that covers both blue/red teaming.</p><p>Begin by starting the Machine:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/222/1*EG7xEx3VRwazTy3UBA5-UA.png" /></figure><p>Once you’ve laucnehd your AttackBox/ connected to VPN, we’re ready to begin.</p><h3>Task 1 — Red: Exploit the Server!</h3><h4>Ping</h4><p>I send a ping command to the IP address provided to check the target is reachable.</p><p>We use the command ping $TARGET</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/599/1*tpUVCZI1UdhQw38abSjLNA.png" /></figure><p>Success!</p><p>No let’s use <strong>nmap </strong>to see if we can find any open ports.</p><p>A basic command will suffice for this task ( nmap $TARGET ).</p><p>The -v flag in nmap stands for <strong>verbose mode</strong>. It provides more detailed output about the scanning process as it runs.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/732/1*ZqiElcrwvJ7joRIFv-N4nA.png" /></figure><p>We have 3 open ports on our target.</p><p><strong>Port 22:</strong> SSH (Secure Shell)</p><p><strong>Port 80</strong>: HTTP (HyperText Transfer Protocol)</p><p><strong>Port 50000:</strong> Not assigned to anything in particular by the Internet Assigned Numbers Authority (IANA). These ports are often used by applications or systems for ephemeral purposes, such as dynamically assigned client-side communication in networked applications.</p><p>When visiting the $TARGET in the browser we get a maintainence page.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*lBul_3On5OPOzca2FkIAWQ.png" /></figure><p>As we have a webserver running on port 80 let’s use directory scan to see if we can find any potential unlinked/hidden directories.</p><p><strong>Gobuster </strong>brute-forces potential directories using a wordlist of common names — sending HTTP requests and checking if the server responds.</p><ul><li><strong>dir:</strong> Mode to scan for directories and files.</li><li><strong>-u:</strong> Target URL.</li><li><strong>-w:</strong> Path to the wordlist.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/731/1*4rRfMwlU6Ig2Zvw5kqFwVA.png" /></figure><p>Nothing of particular interest here.</p><p>Let’s checkout the other open port we found — 50000.</p><p>If we head to to $TARGET:50000 we get taken to a login page.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*5RwUNUQfGxTRd-JTtvbaDw.png" /></figure><p>After a quick Google search for TeamCity 2023.11.3 we get some promising results!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*RhhsS45vSm4Cl9HtKncFfA.png" /></figure><p>This brilliant write up on <a href="https://www.vicarius.io/vsociety/posts/teamcity-auth-bypass-to-rce-cve-2024-27198-and-cve-2024-27199">Vicarius</a> informs us that this particular version is vulnerable to authentication bypass and RCE.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/599/1*CBwUra0wqAs3P9DOSCdcyg.png" /></figure><p>We find a script that W01fh4cker has created allowing us to easily execute a webshell.</p><pre><br># Clone the repo<br>git clone https://github.com/W01fh4cker/CVE-2024-27198-RCE.git<br><br># Get into its folder<br>cd CVE-2024-27198-RCE<br><br># Install requirements<br>pip install requests urllib3 faker<br><br># Run the exploit<br>python CVE-2024-27198-RCE.py -t http://$TARGET<br></pre><p>When we run the script, it sets us up admin credentials, uploads a malicious plugin to TeamCity and lets us RCE.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/878/1*wgI-NkX6voGb8YcC4eROfQ.png" /></figure><p>Now we just poke around and find the flag.txt in the user’s home folder.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/480/1*fanhr3IaHrGNQNdwNMUimA.png" /></figure><p>Congratulations, that’s the red teaming done!</p><h3>Task 2 — Blue: Let’s Investigate!</h3><p>Spin up the next machine and access Splunk.</p><p>Here we’re on the admin panel.</p><figure><img alt="splunk admin panel" src="https://cdn-images-1.medium.com/max/1024/1*moAXF7P8R6xmWOw1Ad2djg.png" /></figure><p>To check what data we have access to, lets go to Settings &gt; Data Inputs &gt; Files &amp; Directories, we can see what Splunk has been set up to monitor.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/782/1*GM2dyOXrxE8wzD8TYSjFHA.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*VGLafBhqE2l6mA_9I_uejQ.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*3tf_JKUB5N6sYCY6Rwl-ww.png" /></figure><p>We see some interesting sourcesthat we can uses as a valuable starting point.</p><p>Apps &gt; Search &amp; Reporting to start hunting.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/538/1*cNVyhr-Cj7_9onF2QfPWnw.png" /></figure><h4>Question 1: What is the name of the backdoor user which was created on the server after exploitation?</h4><p>Ensuring we set the search parameter to “All time”, we can search through the logs in /var/log/auth.log and search for “new” to see if we anything of relevance.</p><p>The /var/log/auth.log file logs authentication events, including logins, privilege escalations, authentication failures, and account management.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/937/1*eabehyhQjqSeT0dMId4Wpg.png" /></figure><p>Searching through those logs finds us the answer to Q1.</p><h4>Question 2: What is the name of the malicious-looking package installed on the server?</h4><p>We can now search for installation logs by changing the source to /var/log/dpkg.log and appending the term installed to filter the logs that include it.</p><p>Setting the time-frame to when the backdoor user was created in Question 1, shows us something suspicious was installed.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*LOBSnESDsWYP41KhMWgzog.png" /></figure><h4>Question 3: What is the name of the plugin installed on the server after successful exploitation?</h4><p>I literally just searched plugin during the timeframe of the attack and there was one response.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Y7oJx9dHh5ibH1eTcqGQSg.png" /></figure><p>Congratulations, we’re done! :)</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=9a32e6b4d5d1" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>