KalmarCTF 2024
7 challenges with 7 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
- caddy
- ssti
Same technique in picoCTF: Bithug, Startup Company, SSTI2
- web
- pickle-deserialization
Same technique in picoCTF: Client-side-again, dont-use-client-side, Irish-Name-Repo 3
- web
- oracle
- signing
- ed25519
Same technique in picoCTF: Client-side-again, dont-use-client-side, Irish-Name-Repo 3
Cryptography2
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
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.
- pwn
Same technique in picoCTF: Guessing Game 1, x-sixty-what, format string 3
Reverse engineering1
Work out what a compiled program does without its source, then work backwards from the check to the input that passes it.
- rev
Same technique in picoCTF: WinAntiDbg0x100, WinAntiDbg0x200, WinAntiDbg0x300