Break In 2016
12 challenges with 19 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.
- 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
Forensics3
Recover something from a file, a capture, or a disk image - often from a part of it the format says is unused.
- password cracking
- forensics
- linux filesystem
Same technique in picoCTF: FindAndOpen, c0rrupt, extensions
- networking
Same technique in picoCTF: FindAndOpen, c0rrupt, extensions
- networking
Same technique in picoCTF: FindAndOpen, c0rrupt, extensions
Misc3
Everything that fits no other box: esolangs, puzzles, scripting exercises, and the jail escapes that have not yet earned their own category.
- stegno
Same technique in picoCTF: Permissions, Specialer, Codebook
- golang
- irc
Same technique in picoCTF: Permissions, Specialer, Codebook
- stegno
Same technique in picoCTF: Permissions, Specialer, Codebook
Steganography2
Find the payload hidden inside a carrier that looks ordinary. Bit planes, appended data, metadata, and audio spectrograms.
- steganography
Same technique in picoCTF: FindAndOpen, StegoRSA, Glory of the Garden
- steganography
- stego
Same technique in picoCTF: FindAndOpen, StegoRSA, Glory of the Garden
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.
- crypto
Same technique in picoCTF: StegoRSA, Timestamped Secrets, AES-ABC