<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>CTF on the fidelyafr experience</title><link>https://fidelyafr.fyi/ctfs/</link><description>Recent content in CTF on the fidelyafr experience</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Thu, 14 Aug 2025 00:00:00 +0000</lastBuildDate><atom:link href="https://fidelyafr.fyi/ctfs/index.xml" rel="self" type="application/rss+xml"/><item><title>SMT Program 2025: Various Write Up</title><link>https://fidelyafr.fyi/ctfs/smt_2025/</link><pubDate>Thu, 14 Aug 2025 00:00:00 +0000</pubDate><guid>https://fidelyafr.fyi/ctfs/smt_2025/</guid><description>&lt;h2 id="malware"&gt;Malware&lt;/h2&gt;&#10;&lt;h3 id="static"&gt;Static&lt;/h3&gt;&#10;&lt;p&gt;Description&lt;/p&gt;&#10;&lt;pre tabindex="0"&gt;&lt;code&gt;Before you start analyzing a malware file, it is generally a good practice to take its hash and search it on VirusTotal to see if others have analyzed the same file before. For this challenge, we give you this SHA256 hash: `556700ac50ffa845e5de853498242ee5abb288eb5b8ae1ae12bfdb5746e3b7b1`.&#10;&#10;Answer the questions at `nc 52.77.77.117 10031`&#10;&lt;/code&gt;&lt;/pre&gt;&lt;p&gt;This is an easy/baby challenge to introduce you about how to use VirusTotal as a first stop for malware analysis. Visiting VirusTotal to look for the hash of the file will return the ILOVEYOU worm report.&lt;/p&gt;</description></item><item><title>HackTheBox Business CTF Cyber Skills Benchmart 2025: Operation Blackout Write Up</title><link>https://fidelyafr.fyi/ctfs/htb_business_2025/</link><pubDate>Sat, 24 May 2025 00:00:00 +0000</pubDate><guid>https://fidelyafr.fyi/ctfs/htb_business_2025/</guid><description>&lt;h2 id="cloud"&gt;Cloud&lt;/h2&gt;&#10;&lt;h3 id="easy-vault"&gt;[Easy] Vault&lt;/h3&gt;&#10;&lt;p&gt;Vault is a vulnerable S3 bucket challenge with a twist. We&amp;rsquo;re given a static website hosted on S3 with a few public files that can be downloaded.&lt;/p&gt;&#10;&lt;p&gt;&lt;img src="./cyber-benchmark-images/image-1.png" alt="image"&gt;&lt;/p&gt;&#10;&lt;p&gt;If we try to download one of the files, we can see that it gives or responds to us a link to another S3 bucket specifically used to store files.&lt;/p&gt;&#10;&lt;p&gt;&lt;img src="./cyber-benchmark-images/image-2.png" alt="image"&gt;&lt;/p&gt;&#10;&lt;p&gt;Upon further inspection using the &lt;code&gt;aws cli&lt;/code&gt; client, we&amp;rsquo;ve found the complete directory of this &lt;code&gt;volnaya-vault&lt;/code&gt; bucket. It has public and private subfolders.&lt;/p&gt;</description></item><item><title>HackTheBox Cyber Apocalypse 2025: Tales From Eldoria Write Up</title><link>https://fidelyafr.fyi/ctfs/htb_cyber_apocalypse_2025/</link><pubDate>Sun, 30 Mar 2025 00:00:00 +0000</pubDate><guid>https://fidelyafr.fyi/ctfs/htb_cyber_apocalypse_2025/</guid><description>&lt;h2 id="web-exploitation"&gt;Web Exploitation&lt;/h2&gt;&#10;&lt;h3 id="solvedvery-easy-trial-by-fire"&gt;[SOLVED][very easy] Trial by Fire&lt;/h3&gt;&#10;&lt;p&gt;Trial by Fire is a classic SSTI challenge. For those who are completely new to this, SSTI or Server-side Template Injection is a vulnerability in templating engine of a website that allows for arbitrary code execution. Like almost other web vulnerabilities, this is possible because user&amp;rsquo;s input is not sanitized.&lt;/p&gt;&#10;&lt;p&gt;Template engines are used to have consistent UI for the frontend side of the web. It combines &lt;strong&gt;dynamic input&lt;/strong&gt; and the template to achieve that. For example, in this challenge, the website first ask for a name that will be rendered on the next page:&lt;/p&gt;</description></item></channel></rss>