boot2root 2020
30 challenges with 65 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 CTFtimeUncategorised12
The upstream scoreboard did not say, so neither do we.
Roppy ropper
3 official solutionsAlso written up in: datajerk/ctf-write-ups, Red-Knights-CTF/writeups, datajerk/ctf-write-ups
To Pwn
3 official solutionsAlso written up in: datajerk/ctf-write-ups, Red-Knights-CTF/writeups, datajerk/ctf-write-ups
Bobby Boi
2 official solutionsAlso written up in: datajerk/ctf-write-ups, datajerk/ctf-write-ups
Canned
2 official solutionsAlso written up in: datajerk/ctf-write-ups, datajerk/ctf-write-ups
Shellcode Loooong
2 official solutionsAlso written up in: datajerk/ctf-write-ups, datajerk/ctf-write-ups
Active directory
1 official solutionAlso written up in: Red-Knights-CTF/writeups
Count the door
1 official solutionAlso written up in: Red-Knights-CTF/writeups
Immortal
1 official solutionAlso written up in: Red-Knights-CTF/writeups
Open gl
1 official solutionAlso written up in: Red-Knights-CTF/writeups
Staple
1 official solutionAlso written up in: Red-Knights-CTF/writeups
String
1 official solutionAlso written up in: Pynard/writeups
Target 3
1 official solutionAlso written up in: Red-Knights-CTF/writeups
Cryptography7
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: Red-Knights-CTF/writeups, r3yc0n1c/CTF-Writeups, Re-Adventures/CTF-Writeups, DaBaddest/CTF-Writeups
- python
- crypto
Same technique in picoCTF: Sequences, C3, It's Not My Fault 2
Also written up in: r3yc0n1c/CTF-Writeups, r3yc0n1c/CTF-Writeups
- rot
- crypto
- xor
Same technique in picoCTF: Custom encryption, XtraORdinary, It's Not My Fault 2
Chall
3 official solutionsAlso written up in: Red-Knights-CTF/writeups, r3yc0n1c/CTF-Writeups, r3yc0n1c/CTF-Writeups
Also written up in: r3yc0n1c/CTF-Writeups, r3yc0n1c/CTF-Writeups
Also written up in: Red-Knights-CTF/writeups
- programming
- crypto
Same technique in picoCTF: It's Not My Fault 2, StegoRSA, AES-ABC
Also written up in: r3yc0n1c/CTF-Writeups
- aes-cbc
Same technique in picoCTF: AES-ABC, Compress and Attack, cryptomaze
- legendre-symbol
- rsa
Same technique in picoCTF: It's Not My Fault 2, StegoRSA, john_pollard
Web3
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: Red-Knights-CTF/writeups
- web
Same technique in picoCTF: Live Art, secure-email-service, No FA
Also written up in: Red-Knights-CTF/writeups
- web
- http-smuggling
Same technique in picoCTF: Live Art, secure-email-service, No FA
Also written up in: Red-Knights-CTF/writeups
- overwriting
- web
- uploading
- htaccess
Same technique in picoCTF: Live Art, secure-email-service, No FA
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: Re-Adventures/CTF-Writeups, DaBaddest/CTF-Writeups
- game
- misc
- socket
Same technique in picoCTF: PW Crack 2, Permissions, Specialer
Also written up in: r3yc0n1c/CTF-Writeups
- euler
Same technique in picoCTF: PW Crack 2, Permissions, Specialer
- game
- misc
- socket
Same technique in picoCTF: PW Crack 2, Permissions, Specialer
Binary exploitation2
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: datajerk/ctf-write-ups, Pynard/writeups, datajerk/ctf-write-ups, Pynard/writeups
- shellcode
Same technique in picoCTF: handoff, Binary Gauntlet 2, Kit Engine
- pwn
Same technique in picoCTF: lockdown-horses, Guessing Game 1, Bizz Fuzz
OSINT2
Answer a question about the real world from public sources. The work is pivoting between identifiers, not exploiting anything.
Also written up in: Red-Knights-CTF/writeups, Pynard/writeups
- ctf
- osint
- challenges
- b00t2root
- ctfcomp
- discord
Same technique in picoCTF: CVE-XXXX-XXXX
Also written up in: Pynard/writeups
- challenges
- ctf
- osint
- target-2
- boot2root
Same technique in picoCTF: CVE-XXXX-XXXX
Reverse engineering1
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: Re-Adventures/CTF-Writeups, DaBaddest/CTF-Writeups
- reverse-engineering
Same technique in picoCTF: Checkpass, WinAntiDbg0x100, WinAntiDbg0x200