ångstromCTF 2018
36 challenges with 113 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 CTFtimeCryptography8
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
- rsa
Same technique in picoCTF: StegoRSA, john_pollard, rsa_oracle
- crypto
- xor
Same technique in picoCTF: Custom encryption, triple-secure, XtraORdinary
- cryptography
Same technique in picoCTF: StegoRSA, Timestamped Secrets, AES-ABC
- crypto
Same technique in picoCTF: StegoRSA, Timestamped Secrets, AES-ABC
- crypto
- rsa
Same technique in picoCTF: StegoRSA, john_pollard, rsa_oracle
- cryptography
Same technique in picoCTF: StegoRSA, Timestamped Secrets, AES-ABC
- crypto
- guessing
Same technique in picoCTF: StegoRSA, Timestamped Secrets, AES-ABC
- crypto
Same technique in picoCTF: StegoRSA, Timestamped Secrets, AES-ABC
Web8
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
- web
Same technique in picoCTF: Client-side-again, dont-use-client-side, Irish-Name-Repo 3
Misc8
Everything that fits no other box: esolangs, puzzles, scripting exercises, and the jail escapes that have not yet earned their own category.
- misc
Same technique in picoCTF: Permissions, Specialer, Codebook
- misc
Same technique in picoCTF: Permissions, Specialer, Codebook
- misc
Same technique in picoCTF: Permissions, Specialer, Codebook
- misc
Same technique in picoCTF: Permissions, Specialer, Codebook
- misc
Same technique in picoCTF: Permissions, Specialer, Codebook
- misc
Same technique in picoCTF: Permissions, Specialer, Codebook
- misc
Same technique in picoCTF: Permissions, Specialer, Codebook
- misc
Same technique in picoCTF: Permissions, Specialer, Codebook
Binary exploitation7
Turn a memory-safety bug in a native binary into control of execution. Usually a stack overflow, a format string, or a heap primitive.
- binary
Same technique in picoCTF: Guessing Game 1, x-sixty-what, format string 3
- binary
Same technique in picoCTF: Guessing Game 1, x-sixty-what, Binary Gauntlet 3
- binary
Same technique in picoCTF: Guessing Game 1, x-sixty-what, format string 3
- binary
Same technique in picoCTF: Guessing Game 1, x-sixty-what, format string 3
- binary
Same technique in picoCTF: Guessing Game 1, x-sixty-what, format string 3
- pwn
- binary
Same technique in picoCTF: Guessing Game 1, x-sixty-what, format string 3
- uaf
- binaryexploitation
- pwn
Same technique in picoCTF: Guessing Game 1, x-sixty-what, tea-cash
Reverse engineering5
Work out what a compiled program does without its source, then work backwards from the check to the input that passes it.
- reversing
Same technique in picoCTF: WinAntiDbg0x100, WinAntiDbg0x200, WinAntiDbg0x300
- rev
Same technique in picoCTF: WinAntiDbg0x100, WinAntiDbg0x200, WinAntiDbg0x300
- reversing
Same technique in picoCTF: WinAntiDbg0x100, WinAntiDbg0x200, WinAntiDbg0x300
- reverse
- engineering
Same technique in picoCTF: WinAntiDbg0x100, WinAntiDbg0x200, WinAntiDbg0x300
- reverse
- engineering
Same technique in picoCTF: WinAntiDbg0x100, WinAntiDbg0x200, WinAntiDbg0x300