MeePwn CTF 1st 2017
28 challenges with 74 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 CTFtimeUncategorised9
The upstream scoreboard did not say, so neither do we.
Setup
2 official solutionsAlso written up in: l4wio/CTF-challenges-by-me, l4wio/CTF-challenges-by-me
Br0kenMySQL 1 2 3
1 official solutionAlso written up in: babyphd.net
Bs (100pt)
1 official solutionAlso written up in: ctf.harrisongreen.me
C0ffee
1 official solutionAlso written up in: l4wio/CTF-challenges-by-me
Decrypt
1 official solutionAlso written up in: vxresearch/ctf-writeups
Also written up in: adm1nkyj/ctfwriteup
Also written up in: posgnu/ctfs
Also written up in: l4wio/CTF-challenges-by-me
TooManyCrypto
1 official solutionAlso written up in: vxresearch/ctf-writeups
Web6
Reach data or functionality the application meant to keep from you - through its inputs, its tokens, or its trust in the client.
Also written up in: sw1ss/ctf, vxresearch/ctf-writeups
- web
Same technique in picoCTF: Live Art, secure-email-service, No FA
Also written up in: laxa/write-ups, Laxa/write-ups
- web
Same technique in picoCTF: Live Art, secure-email-service, No FA
Also written up in: laxa/write-ups, Laxa/write-ups
- web
Same technique in picoCTF: Live Art, secure-email-service, No FA
Also written up in: vxresearch/ctf-writeups
- web
Same technique in picoCTF: Live Art, secure-email-service, No FA
- sqli
Same technique in picoCTF: Irish-Name-Repo 3, Startup Company, More SQLi
- web
Same technique in picoCTF: Live Art, secure-email-service, No FA
Cryptography4
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: simply-TOOBASED/ctf-writeups, DDOS-Attacks/ctf-writeups, ashutosh1206/Crypto-CTF-Writeups, simply-TOOBASED/ctf-writeups, DDOS-Attacks/ctf-writeups, znqt.github.io
Also written up in: ashutosh1206/Crypto-CTF-Writeups, simply-TOOBASED/ctf-writeups, DDOS-Attacks/ctf-writeups, ashutosh1206/Crypto-CTF-Writeups
- crypto
Same technique in picoCTF: It's Not My Fault 2, StegoRSA, john_pollard
- crypto
Same technique in picoCTF: It's Not My Fault 2, StegoRSA, AES-ABC
- crypto
Same technique in picoCTF: It's Not My Fault 2, StegoRSA, AES-ABC
Binary exploitation4
Turn a memory-safety bug in a native binary into control of execution. Usually a stack overflow, a format string, or a heap primitive.
Also written up in: briansp8210/CTF-writeup, willtuna/CTF-writeup, laxa/write-ups, briansp8210/CTF-writeup, 5unKn0wn/ctfs, Laxa/write-ups, willtuna/CTF-writeup
- exploit
Same technique in picoCTF: lockdown-horses, Guessing Game 1, Bizz Fuzz
Also written up in: l4wio/CTF-challenges-by-me, laxa/write-ups, Laxa/write-ups
- exploit
Same technique in picoCTF: lockdown-horses, Guessing Game 1, Bizz Fuzz
Also written up in: laxa/write-ups, Laxa/write-ups
- exploit
Same technique in picoCTF: lockdown-horses, Guessing Game 1, Bizz Fuzz
- pwnable
- exploitation
Same technique in picoCTF: lockdown-horses, Guessing Game 1, Bizz Fuzz
Reverse engineering3
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: 5unKn0wn/ctfs
- reversing
Same technique in picoCTF: Checkpass, WinAntiDbg0x100, WinAntiDbg0x200
Also written up in: 5unKn0wn/ctfs
- reverse
Same technique in picoCTF: Checkpass, WinAntiDbg0x100, WinAntiDbg0x200
Also written up in: 5unKn0wn/ctfs
- reverse
Same technique in picoCTF: Checkpass, WinAntiDbg0x100, WinAntiDbg0x200
Misc2
Everything that fits no other box: esolangs, puzzles, scripting exercises, and the jail escapes that have not yet earned their own category.
Also written up in: babyphd.net
Same technique in picoCTF: PW Crack 2, Permissions, Specialer
- misc
- captcha
Same technique in picoCTF: PW Crack 2, Permissions, Specialer