Aarhus Ctf Writeups 2019
15 challenges with 16 published solutions between them. The writeups for this event were found in public repositories. Each link is pinned to the commit it was read from.
Where these writeups liveCryptography7
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.
Also written up in: eskildsen/aarhus-ctf-2019-writeups
Also written up in: eskildsen/aarhus-ctf-2019-writeups
Arguably Rsa
1 official solutionAlso written up in: eskildsen/aarhus-ctf-2019-writeups
Indistinguishable
1 official solutionAlso written up in: eskildsen/aarhus-ctf-2019-writeups
Pierre
1 official solutionAlso written up in: eskildsen/aarhus-ctf-2019-writeups
Repeated XOR 2 Electric Boogaloo
1 official solutionAlso written up in: Berry-95/CTF-Writeups
Xorfiles
1 official solutionAlso written up in: eskildsen/aarhus-ctf-2019-writeups
Web5
Reach data or functionality the application meant to keep from you - through its inputs, its tokens, or its trust in the client.
Leak Db
2 official solutionsAlso written up in: eskildsen/aarhus-ctf-2019-writeups, Berry-95/CTF-Writeups
Awesome Calculator
1 official solutionAlso written up in: eskildsen/aarhus-ctf-2019-writeups
Navitas
1 official solutionAlso written up in: Berry-95/CTF-Writeups
Registration
1 official solutionAlso written up in: eskildsen/aarhus-ctf-2019-writeups
Writeup2
1 official solutionAlso written up in: eskildsen/aarhus-ctf-2019-writeups
Reverse engineering2
Work out what a compiled program does without its source, then work backwards from the check to the input that passes it.
Also written up in: eskildsen/aarhus-ctf-2019-writeups
Pwcheck
1 official solutionAlso written up in: eskildsen/aarhus-ctf-2019-writeups
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.
Bookmanager
1 official solutionAlso written up in: eskildsen/aarhus-ctf-2019-writeups