Hackover CTF 2018
16 challenges with 49 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 CTFtimeWeb4
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
- robots
- cookies
Same technique in picoCTF: logon, Cookie Monster Secret Recipe, Old Sessions
- robots
- http
- headers
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
Misc4
Everything that fits no other box: esolangs, puzzles, scripting exercises, and the jail escapes that have not yet earned their own category.
- lisp
- clojure
Same technique in picoCTF: Permissions, Specialer, Codebook
- morse
- misc
Same technique in picoCTF: Permissions, Specialer, Codebook
- pwning
Same technique in picoCTF: Permissions, Specialer, Codebook
- paillier
Same technique in picoCTF: Permissions, Specialer, Codebook
Cryptography3
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.
- bash
- gpg
Same technique in picoCTF: StegoRSA, Timestamped Secrets, AES-ABC
- hash
Same technique in picoCTF: hashcrack, It is my Birthday 2, StegoRSA
- hash-collision
- dos
Same technique in picoCTF: hashcrack, It is my Birthday 2, StegoRSA
Reverse engineering2
Work out what a compiled program does without its source, then work backwards from the check to the input that passes it.
- movfuscated
- re
Same technique in picoCTF: WinAntiDbg0x100, WinAntiDbg0x200, WinAntiDbg0x300
- rev
Same technique in picoCTF: WinAntiDbg0x100, WinAntiDbg0x200, WinAntiDbg0x300
Forensics2
Recover something from a file, a capture, or a disk image - often from a part of it the format says is unused.
- forensics
Same technique in picoCTF: FindAndOpen, c0rrupt, extensions
- forensics
- recovery
Same technique in picoCTF: FindAndOpen, c0rrupt, extensions
Binary exploitation1
Turn a memory-safety bug in a native binary into control of execution. Usually a stack overflow, a format string, or a heap primitive.
- ruby
- pwning
- shell
Same technique in picoCTF: Guessing Game 1, x-sixty-what, format string 3