x3CTF 2025 (feat. mvm)
8 challenges with 12 published community solutions between them. Solution links go to CTFtime’s task page, which aggregates every writeup for a challenge - individual blog posts rot, the aggregator does not.
Full task list on CTFtimeWeb3
Reach data or functionality the application meant to keep from you - through its inputs, its tokens, or its trust in the client.
Kittyconvert
1 official solutionAlso written up in: rerrorctf/writeups
Mvmcheckers Inc
1 official solutionAlso written up in: siunam321/CTF-Writeups
Submission
1 official solutionAlso written up in: rerrorctf/writeups
Binary exploitation2
Turn a memory-safety bug in a native binary into control of execution. Usually a stack overflow, a format string, or a heap primitive.
Devnull As A Service
2 official solutionsAlso written up in: rerrorctf/writeups, ally-petitt/public-ctf-writeups
Same technique in picoCTF: vr-school, sice_cream, zero_to_hero
Misc2
Everything that fits no other box: esolangs, puzzles, scripting exercises, and the jail escapes that have not yet earned their own category.
Also written up in: rerrorctf/writeups
Same technique in picoCTF: PW Crack 2, Permissions, Specialer
Same technique in picoCTF: PW Crack 2, Permissions, Specialer
Cryptography1
Recover a plaintext or a key from something that was supposed to protect it. In practice: identify the scheme, find the parameter the author got wrong, exploit it.
Also written up in: rerrorctf/writeups, rerrorctf/writeups, rerrorctf/writeups