HITCON CTF 2016 Quals
24 challenges with 47 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 CTFtimeMisc21
Everything that fits no other box: esolangs, puzzles, scripting exercises, and the jail escapes that have not yet earned their own category.
Same technique in picoCTF: Permissions, Specialer, Codebook
Same technique in picoCTF: Permissions, Specialer, Codebook
Same technique in picoCTF: Permissions, Specialer, Codebook
Same technique in picoCTF: Permissions, Specialer, Codebook
Same technique in picoCTF: Permissions, Specialer, Codebook
Same technique in picoCTF: Permissions, Specialer, Codebook
Same technique in picoCTF: Permissions, Specialer, Codebook
Same technique in picoCTF: Permissions, Specialer, Codebook
Same technique in picoCTF: Permissions, Specialer, Codebook
Same technique in picoCTF: Permissions, Specialer, Codebook
Same technique in picoCTF: Permissions, Specialer, Codebook
Same technique in picoCTF: Permissions, Specialer, Codebook
Same technique in picoCTF: Permissions, Specialer, Codebook
Same technique in picoCTF: Permissions, Specialer, Codebook
Same technique in picoCTF: Permissions, Specialer, Codebook
Same technique in picoCTF: Permissions, Specialer, Codebook
Same technique in picoCTF: Permissions, Specialer, Codebook
Same technique in picoCTF: Permissions, Specialer, Codebook
Same technique in picoCTF: Permissions, Specialer, Codebook
Same technique in picoCTF: Permissions, Specialer, Codebook
Same technique in picoCTF: Permissions, Specialer, Codebook
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.
Same technique in picoCTF: Guessing Game 1, x-sixty-what, format string 3
Same technique in picoCTF: Guessing Game 1, x-sixty-what, Binary Gauntlet 3
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.
Same technique in picoCTF: StegoRSA, Timestamped Secrets, AES-ABC