<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Anuko on kanyo's blog</title><link>https://chaelsoo.me/tags/anuko/</link><description>Recent content in Anuko on kanyo's blog</description><generator>Hugo -- gohugo.io</generator><language>en-gb</language><lastBuildDate>Tue, 26 May 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://chaelsoo.me/tags/anuko/index.xml" rel="self" type="application/rss+xml"/><item><title>HackINI 2026: Legacy</title><link>https://chaelsoo.me/writeups/hackini-legacy/</link><pubDate>Tue, 26 May 2026 00:00:00 +0000</pubDate><guid>https://chaelsoo.me/writeups/hackini-legacy/</guid><description>&lt;p&gt;The fourth machine in the chain. A Linux server running two web services on non-standard ports. One was an older Anuko Time Tracker instance with a known SQL injection CVE, the other was a Webmin panel that opened up once you had the right credentials. The interesting part here was that this machine didn&amp;rsquo;t require brute-forcing or clever guessing: the credentials came from earlier in the chain, and the exploit path came from recognizing the software version and knowing where to look.&lt;/p&gt;</description></item></channel></rss>