<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>Roo CTF 2025 on tuxops</title><link>https://tuxops.org/writeups/rooctf2025/</link><description>Recent content in Roo CTF 2025 on tuxops</description><generator>Hugo</generator><language>en-us</language><atom:link href="https://tuxops.org/writeups/rooctf2025/index.xml" rel="self" type="application/rss+xml"/><item><title/><link>https://tuxops.org/writeups/rooctf2025/roo-ctf-2025_-include/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://tuxops.org/writeups/rooctf2025/roo-ctf-2025_-include/</guid><description>&lt;h1 id="roo-ctf-2025-include-tuxops"&gt;&lt;code&gt;Roo CTF 2025: Include (tuxops)&lt;/code&gt;&lt;/h1&gt;
&lt;hr&gt;
&lt;h2 id="description-imported"&gt;title: &amp;ldquo;include&amp;rdquo;
date: &amp;ldquo;2025-10-25&amp;rdquo;
author: &amp;ldquo;TechnoDot (technodot)&amp;rdquo;
description: &amp;ldquo;imported&amp;rdquo;&lt;/h2&gt;
&lt;h3 id="technodot-mrnullone"&gt;&lt;code&gt;TechnoDot, mrnullone&lt;/code&gt;&lt;/h3&gt;
&lt;p&gt;&lt;code&gt;Given the URL https://include.cyberroos.org, find the flag.&lt;/code&gt;&lt;/p&gt;
&lt;p&gt;&lt;code&gt;Navigating to the URL, we are greeted with a simple page that switches themes. We see that the theme is conveyed by a get parameter in the URL, between the themes light and dark. Opening up DevTools, we see that the X-Powered-By header is PHP/8.0.30, shining a light onto how we proceed. Attempting to set a non-existent theme (such as ?theme=flag) results in no styling at all. Examining the page source, we see that the style has a PHP error in it.&lt;/code&gt;&lt;/p&gt;</description></item><item><title/><link>https://tuxops.org/writeups/rooctf2025/roo-ctf-2025_-paddington/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://tuxops.org/writeups/rooctf2025/roo-ctf-2025_-paddington/</guid><description>&lt;h1 id="roo-ctf-2025-paddington-tuxops"&gt;&lt;code&gt;Roo CTF 2025: Paddington (tuxops)&lt;/code&gt;&lt;/h1&gt;
&lt;hr&gt;
&lt;h2 id="description-"&gt;title: &amp;ldquo;Paddington&amp;rdquo;
date: &amp;ldquo;2025-10-25&amp;rdquo;
author: &amp;ldquo;TechnoDot (technodot)&amp;rdquo;
description: &amp;quot;&amp;quot;&lt;/h2&gt;
&lt;h3 id="mrnullone-technodot"&gt;&lt;code&gt;mrnullone, TechnoDot&lt;/code&gt;&lt;/h3&gt;
&lt;p&gt;&lt;code&gt;Given the capture file chall.pcap, find the flag. chall.pcap was modified to hide the flag.&lt;/code&gt;&lt;/p&gt;
&lt;p&gt;&lt;code&gt;Opening the file, we see that almost every packet is the Modbus protocol. Putting not modbus into the filter bar yields a few TCP packets, which seem unimportant. Looking through the packets, we notice that in the ascii contents section, there are some jumbled ascii characters as well. There seems to be no rhyme nor reason to these characters, and it can reasonably be inferred that we’ll have to do deeper digging. There’s also a lot of malformed packets, but I can’t seem to make anything of them. Sorting through packets, one value that seems to change consistently is the Register Value.&lt;/code&gt;&lt;/p&gt;</description></item><item><title/><link>https://tuxops.org/writeups/rooctf2025/roo-ctf-2025_-split-screen/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://tuxops.org/writeups/rooctf2025/roo-ctf-2025_-split-screen/</guid><description>&lt;h1 id="roo-ctf-2025-split-screen-tuxops"&gt;&lt;code&gt;Roo CTF 2025: Split-Screen (tuxops)&lt;/code&gt;&lt;/h1&gt;
&lt;hr&gt;
&lt;h2 id="description-"&gt;title: &amp;ldquo;split-screen&amp;rdquo;
date: &amp;ldquo;2025-10-25&amp;rdquo;
author: &amp;ldquo;TechnoDot (technodot)&amp;rdquo;
description: &amp;quot;&amp;quot;&lt;/h2&gt;
&lt;h3 id="technodot-httpsgithubcomtechdudie"&gt;&lt;code&gt;TechnoDot (https://github.com/TechDudie)&lt;/code&gt;&lt;/h3&gt;
&lt;p&gt;&lt;code&gt;Provided with the split-screen executable, find the flag.&lt;/code&gt;&lt;/p&gt;
&lt;p&gt;&lt;code&gt;REQUIREMENTS: Ghidra, WSL (for Windows); we don’t talk about Mac&lt;/code&gt;&lt;/p&gt;
&lt;p&gt;&lt;code&gt;Try running the executable. On Windows, run it in WSL.&lt;/code&gt;&lt;/p&gt;
&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th style="text-align: left"&gt;&lt;code&gt;┏━(Message from Kali developers) ┃ ┃ This is a minimal installation of Kali Linux, you likely ┃ want to install supplementary tools. Learn how: ┃ ⇒ https://www.kali.org/docs/troubleshooting/common-minimum-setup/ ┃ ┗━(Run: “touch ~/.hushlogin” to hide this message) (base) ┌──(technodot㉿VIVOBOOK)-[~] └─$ cd /mnt/c/Users/technodot/Downloads/ (base) ┌──(technodot㉿VIVOBOOK)-[/mnt/c/Users/technodot/Downloads] └─$ chmod +x ./split-screen (base) ┌──(technodot㉿VIVOBOOK)-[/mnt/c/Users/technodot/Downloads] └─$ ./split-screen [timeline] expectation and reality drift apart. press enter to sync&amp;gt; you keep rewinding but nothing changes. try again later. (base) ┌──(technodot㉿VIVOBOOK)-[/mnt/c/Users/technodot/Downloads] └─$&lt;/code&gt;&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;/tbody&gt;
&lt;/table&gt;
&lt;p&gt;&lt;code&gt;Loading the executable into the dogbolt decompiler, we can see different decompilations to varying detail. Hex-Rays offers the clearest code, with all of the print statements verbatim in the code.&lt;/code&gt;&lt;/p&gt;</description></item></channel></rss>