QCTF Starter 2018
19 challenges with 33 published solutions between them. No writeups were ever filed against this event's listing, so its solutions were found in public repositories instead. Each link is pinned to the commit it was read from.
The event listingBinary exploitation10
Turn a memory-safety bug in a native binary into control of execution. Usually a stack overflow, a format string, or a heap primitive.
Babystack
8 official solutionsAlso written up in: sajjadium/ctf-writeups, sajjadium/CTFium, gavz/ctf-writeups, sajjadium/ctf-writeups, sajjadium/PersianCatsCTF, sajjadium/ctf-writeups, 0ops/ctfs, sajjadium/CTFium
Also written up in: sajjadium/ctf-writeups, 0ops/ctfs, sajjadium/CTFium, gavz/ctf-writeups, sajjadium/ctf-writeups, sajjadium/PersianCatsCTF
Stackoverflow
2 official solutionsAlso written up in: 0ops/ctfs, shift-crops/CTFWriteups
Also written up in: 0ops/ctfs
Also written up in: r4b3rt/writeups
Also written up in: r4b3rt/writeups
Also written up in: 0ops/ctfs
Primepwn
1 official solutionAlso written up in: 0ops/ctfs
Also written up in: 0ops/ctfs
Also written up in: 0ops/ctfs
Uncategorised4
The upstream scoreboard did not say, so neither do we.
Also written up in: p4-team/ctf
Milktea
1 official solutionAlso written up in: p4-team/ctf
Primitive
1 official solutionAlso written up in: p4-team/ctf
Young Heap
1 official solutionAlso written up in: shift-crops/CTFWriteups
Reverse engineering3
Work out what a compiled program does without its source, then work backwards from the check to the input that passes it.
Source
2 official solutionsAlso written up in: r4b3rt/writeups, r4b3rt/writeups
Also written up in: 0ops/ctfs
Also written up in: 0ops/ctfs
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.
babyRSA
1 official solutionAlso written up in: r4b3rt/writeups
Xman RSA
1 official solutionAlso written up in: r4b3rt/writeups