TUCTF 2019
32 challenges with 96 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 CTFtimeMisc12
Everything that fits no other box: esolangs, puzzles, scripting exercises, and the jail escapes that have not yet earned their own category.
3step
5 writeupsSame technique in picoCTF: Permissions, Specialer, Codebook
pancakes
5 writeupsSame technique in picoCTF: Permissions, Specialer, Codebook
- misc
Same technique in picoCTF: Permissions, Specialer, Codebook
vulnmath
4 writeupsSame technique in picoCTF: Permissions, Specialer, Codebook
ctftp
3 writeupsSame technique in picoCTF: Permissions, Specialer, Codebook
- misc
Same technique in picoCTF: Permissions, Specialer, Codebook
printfun
3 writeupsSame technique in picoCTF: Permissions, Specialer, Codebook
- misc
Same technique in picoCTF: Permissions, Specialer, Codebook
- mega
Same technique in picoCTF: Permissions, Specialer, Codebook
- mega
Same technique in picoCTF: Permissions, Specialer, Codebook
leakalicious
2 writeupsSame technique in picoCTF: Permissions, Specialer, Codebook
- misc
Same technique in picoCTF: Permissions, Specialer, Codebook
Web7
Reach data or functionality the application meant to keep from you - through its inputs, its tokens, or its trust in the client.
- web
Same technique in picoCTF: Client-side-again, dont-use-client-side, Irish-Name-Repo 3
- web
Same technique in picoCTF: Client-side-again, dont-use-client-side, Irish-Name-Repo 3
- web
Same technique in picoCTF: Client-side-again, dont-use-client-side, Irish-Name-Repo 3
- web
Same technique in picoCTF: Client-side-again, dont-use-client-side, Irish-Name-Repo 3
- web
Same technique in picoCTF: Client-side-again, dont-use-client-side, Irish-Name-Repo 3
- web
Same technique in picoCTF: Client-side-again, dont-use-client-side, Irish-Name-Repo 3
- web
Same technique in picoCTF: Client-side-again, dont-use-client-side, Irish-Name-Repo 3
Binary exploitation5
Turn a memory-safety bug in a native binary into control of execution. Usually a stack overflow, a format string, or a heap primitive.
- pwn
Same technique in picoCTF: Guessing Game 1, x-sixty-what, format string 3
- pwn
Same technique in picoCTF: Guessing Game 1, x-sixty-what, format string 3
- pwn
Same technique in picoCTF: Guessing Game 1, x-sixty-what, format string 3
- mega
Same technique in picoCTF: Guessing Game 1, x-sixty-what, Binary Gauntlet 3
- pwn
Same technique in picoCTF: Guessing Game 1, x-sixty-what, format string 3
Cryptography4
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.
- crypto
Same technique in picoCTF: StegoRSA, Timestamped Secrets, AES-ABC
- crypto
Same technique in picoCTF: StegoRSA, Timestamped Secrets, AES-ABC
Crypto Infinite
2 writeups- crypto
Same technique in picoCTF: StegoRSA, Timestamped Secrets, AES-ABC
- crypto
Same technique in picoCTF: StegoRSA, Timestamped Secrets, AES-ABC
Reverse engineering3
Work out what a compiled program does without its source, then work backwards from the check to the input that passes it.
- reverse
- engineering
Same technique in picoCTF: WinAntiDbg0x100, WinAntiDbg0x200, WinAntiDbg0x300
core
4 writeups- reverse
- engineering
Same technique in picoCTF: WinAntiDbg0x100, WinAntiDbg0x200, WinAntiDbg0x300
object
2 writeups- reverse
Same technique in picoCTF: WinAntiDbg0x100, WinAntiDbg0x200, WinAntiDbg0x300
OSINT1
Answer a question about the real world from public sources. The work is pivoting between identifiers, not exploiting anything.
- misc
- osint
Same technique in picoCTF: Permissions, Specialer, Codebook