BackdoorCTF 2015
18 challenges with 99 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 CTFtimeBinary exploitation5
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: ctfs/write-ups-2015, VulnHub/ctf-writeups, vulnhub/ctf-writeups, smokeleeteveryday/CTF_WRITEUPS, AntiRootkit1/write-ups-2015, hcs0/ctf-writeups, TycoRyco/write-ups-2015, smokeleeteveryday/CTF_WRITEUPS, geeksspeak.github.io
- pwnable
Same technique in picoCTF: lockdown-horses, Guessing Game 1, Bizz Fuzz
Also written up in: ctfs/write-ups-2015, VulnHub/ctf-writeups, vulnhub/ctf-writeups, smokeleeteveryday/CTF_WRITEUPS, AntiRootkit1/write-ups-2015, hcs0/ctf-writeups, TycoRyco/write-ups-2015, smokeleeteveryday/CTF_WRITEUPS, geeksspeak.github.io
- pwnable
Same technique in picoCTF: lockdown-horses, Guessing Game 1, Bizz Fuzz
Also written up in: VulnHub/ctf-writeups, vulnhub/ctf-writeups, smokeleeteveryday/CTF_WRITEUPS, hcs0/ctf-writeups, smokeleeteveryday/CTF_WRITEUPS, geeksspeak.github.io
- pwnable
Same technique in picoCTF: lockdown-horses, Guessing Game 1, Bizz Fuzz
Also written up in: geeksspeak.github.io
- exploit
Same technique in picoCTF: lockdown-horses, Guessing Game 1, Bizz Fuzz
- exploit
- js
- clojure
Same technique in picoCTF: lockdown-horses, Guessing Game 1, Bizz Fuzz
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: ctfs/write-ups-2015, smokeleeteveryday/CTF_WRITEUPS, AntiRootkit1/write-ups-2015, TycoRyco/write-ups-2015, smokeleeteveryday/CTF_WRITEUPS
- crypto
Same technique in picoCTF: It's Not My Fault 2, StegoRSA, john_pollard
Also written up in: ctfs/write-ups-2015, smokeleeteveryday/CTF_WRITEUPS, AntiRootkit1/write-ups-2015, TycoRyco/write-ups-2015, smokeleeteveryday/CTF_WRITEUPS
- crypto
Same technique in picoCTF: It's Not My Fault 2, StegoRSA, john_pollard
Also written up in: ctfs/write-ups-2015, AntiRootkit1/write-ups-2015, TycoRyco/write-ups-2015
Also written up in: ctfs/write-ups-2015, AntiRootkit1/write-ups-2015, TycoRyco/write-ups-2015
Web4
Reach data or functionality the application meant to keep from you - through its inputs, its tokens, or its trust in the client.
Follow
6 official solutionsAlso written up in: ctfs/write-ups-2015, VulnHub/ctf-writeups, vulnhub/ctf-writeups, AntiRootkit1/write-ups-2015, hcs0/ctf-writeups, TycoRyco/write-ups-2015
Judge
6 official solutionsAlso written up in: ctfs/write-ups-2015, VulnHub/ctf-writeups, vulnhub/ctf-writeups, AntiRootkit1/write-ups-2015, hcs0/ctf-writeups, TycoRyco/write-ups-2015
Also written up in: ctfs/write-ups-2015, AntiRootkit1/write-ups-2015, TycoRyco/write-ups-2015, geeksspeak.github.io
- web
- redirect
Same technique in picoCTF: Live Art, secure-email-service, No FA
Jshunt
3 official solutionsAlso written up in: ctfs/write-ups-2015, AntiRootkit1/write-ups-2015, TycoRyco/write-ups-2015
Misc3
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: ctfs/write-ups-2015, VulnHub/ctf-writeups, vulnhub/ctf-writeups, smokeleeteveryday/CTF_WRITEUPS, AntiRootkit1/write-ups-2015, hcs0/ctf-writeups, TycoRyco/write-ups-2015, smokeleeteveryday/CTF_WRITEUPS
Also written up in: ctfs/write-ups-2015, VulnHub/ctf-writeups, vulnhub/ctf-writeups, AntiRootkit1/write-ups-2015, hcs0/ctf-writeups, TycoRyco/write-ups-2015
- codes
- qr
Same technique in picoCTF: PW Crack 2, Permissions, Specialer
Rapidfire
3 official solutionsAlso written up in: ctfs/write-ups-2015, AntiRootkit1/write-ups-2015, TycoRyco/write-ups-2015
Forensics1
Recover something from a file, a capture, or a disk image - often from a part of it the format says is unused.
Uncategorised1
The upstream scoreboard did not say, so neither do we.
qr Response
2 official solutionsAlso written up in: capturetheswag.blogspot.com.au, capturetheswag.blogspot.com