<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Web on Blaž Škufca</title><link>https://blazskufca.com/tags/web/</link><description>Recent content in Web on Blaž Škufca</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Sat, 28 Mar 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://blazskufca.com/tags/web/index.xml" rel="self" type="application/rss+xml"/><item><title>Hacking UUIDv1 (DCTF 2026)</title><link>https://blazskufca.com/projects/dctf_2026/</link><pubDate>Sat, 28 Mar 2026 00:00:00 +0000</pubDate><guid>https://blazskufca.com/projects/dctf_2026/</guid><description>&lt;h1 id="intro"&gt;Intro&lt;/h1&gt;
&lt;p&gt;&lt;a href="https://dctf.si/challenges#Nom%20Nom-15"&gt;Nom Nom (DCTF 2026)&lt;/a&gt; looks like a small Flask login app with a standard password-reset feature, but the reset token logic is fundamentally broken.&lt;/p&gt;
&lt;p&gt;Our goal is to take over &lt;code&gt;blackhole@dragonsec.si&lt;/code&gt;, the only account that reveals the flag on &lt;code&gt;/dashboard&lt;/code&gt;. The app generates reset tokens using a custom UUIDv1-style function where most fields remain constant across requests, leaving only a timestamp-derived portion that varies.&lt;/p&gt;
&lt;p&gt;In this writeup we will reverse the token structure, recover the fixed portion from a reset token we control, brute-force the short timestamp window for the victim&amp;rsquo;s token, and use it to reset the victim&amp;rsquo;s password and capture the flag.&lt;/p&gt;</description></item></channel></rss>