Square CTF 2023
32 challenges with 61 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 CTFtimeMisc8
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: AVDestroyer/CTF-Writeups, asmhole/writeups, asmhole/writeups, pwnpope/Writeups
- oracle
- password
Same technique in picoCTF: PW Crack 2, Permissions, Specialer
Also written up in: hurbdbbb/ctf-writeups
- escape
Same technique in picoCTF: PW Crack 2, Permissions, Specialer
Also written up in: asmhole/writeups
- misc
Same technique in picoCTF: PW Crack 2, Permissions, Specialer
- misc
Same technique in picoCTF: PW Crack 2, Permissions, Specialer
- misc
Same technique in picoCTF: PW Crack 2, Permissions, Specialer
- misc
Same technique in picoCTF: PW Crack 2, Permissions, Specialer
- misc
Same technique in picoCTF: PW Crack 2, Permissions, Specialer
- misc
Same technique in picoCTF: PW Crack 2, Permissions, Specialer
Uncategorised8
The upstream scoreboard did not say, so neither do we.
Exploit
2 official solutionsAlso written up in: sinamhdv/ctf-writeups, sinamhdv/ctf-writeups
Also written up in: AvavaAYA/ctf-writeup-collection
Failed Exploit
1 official solutionAlso written up in: sinamhdv/ctf-writeups
Final
1 official solutionAlso written up in: a-p-n/CTF-solutions
Roplon Challenge
1 official solutionAlso written up in: pwnpope/Writeups
Slide Quest
1 official solutionAlso written up in: a-p-n/CTF-solutions
Tank Attack
1 official solutionAlso written up in: mowteam/CTFWriteUps
Tank Bonus Attack
1 official solutionAlso written up in: mowteam/CTFWriteUps
Binary exploitation6
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: mowteam/CTFWriteUps, 0ur4n05/ctf
- exploitation
Same technique in picoCTF: lockdown-horses, Guessing Game 1, Bizz Fuzz
Also written up in: 0ur4n05/ctf
- exploitation
Same technique in picoCTF: lockdown-horses, Guessing Game 1, vr-school
- exploitation
Same technique in picoCTF: lockdown-horses, Guessing Game 1, Bizz Fuzz
Also written up in: 0ur4n05/ctf, 0ur4n05/ctf
- exploitation
Same technique in picoCTF: lockdown-horses, Guessing Game 1, Bizz Fuzz
- exploitation
Same technique in picoCTF: lockdown-horses, Guessing Game 1, Bizz Fuzz
Web4
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: UchaCTF/WriteUps, hurbdbbb/ctf-writeups, kauedg/CTF-Writeups
- web
Same technique in picoCTF: Live Art, secure-email-service, No FA
Also written up in: jiaaaarui/writeups, a-p-n/CTF-solutions, a-p-n/CTF-solutions
- web
- crypto
Same technique in picoCTF: Live Art, secure-email-service, No FA
Also written up in: a-p-n/CTF-solutions
- web
- crypto
Same technique in picoCTF: Live Art, secure-email-service, No FA
- web
Same technique in picoCTF: Live Art, secure-email-service, No FA
Reverse engineering4
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: asmhole/writeups, asmhole/writeups
- reversing
Same technique in picoCTF: Checkpass, WinAntiDbg0x100, WinAntiDbg0x200
Also written up in: asmhole/writeups
- reversing
- exploitation
Same technique in picoCTF: Checkpass, WinAntiDbg0x100, WinAntiDbg0x200
- reversing
Same technique in picoCTF: Checkpass, WinAntiDbg0x100, WinAntiDbg0x200
- reversing
Same technique in picoCTF: Checkpass, WinAntiDbg0x100, WinAntiDbg0x200
Cryptography1
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.
- crypto
Same technique in picoCTF: It's Not My Fault 2, StegoRSA, AES-ABC
Forensics1
Recover something from a file, a capture, or a disk image - often from a part of it the format says is unused.
Also written up in: asmhole/writeups
- forensics
Same technique in picoCTF: investigation_encoded_2, FindAndOpen, Ph4nt0m 1ntrud3r