Space Heroes 2022
56 challenges with 179 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 exploitation13
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: HJMsan/CTF-writeups, msaw328/ctf_writeups, dishankgoel/CTF-Writeups, HJMsan/CTF-writeups, mito753/CTF, msaw328/ctf_writeups, zolutal/ctf-writeups
- pwn
Same technique in picoCTF: lockdown-horses, Guessing Game 1, Bizz Fuzz
Also written up in: dishankgoel/CTF-Writeups, mito753/CTF, mwales/security, cryptocat.me
- pwn
Same technique in picoCTF: lockdown-horses, Guessing Game 1, Bizz Fuzz
Also written up in: BrennenWright/CaptureTheFlag-Writeups, dishankgoel/CTF-Writeups
- pwn
Same technique in picoCTF: lockdown-horses, Guessing Game 1, Bizz Fuzz
Also written up in: HJMsan/CTF-writeups, HJMsan/CTF-writeups
- pwn
Same technique in picoCTF: lockdown-horses, Guessing Game 1, Bizz Fuzz
Also written up in: dishankgoel/CTF-Writeups, mito753/CTF, zolutal/ctf-writeups
- pwn
Same technique in picoCTF: lockdown-horses, Guessing Game 1, Bizz Fuzz
Also written up in: HJMsan/CTF-writeups, HJMsan/CTF-writeups, mito753/CTF
- pwn
Same technique in picoCTF: lockdown-horses, Guessing Game 1, Bizz Fuzz
Also written up in: HJMsan/CTF-writeups, HJMsan/CTF-writeups, mito753/CTF
- pwn
Same technique in picoCTF: lockdown-horses, Guessing Game 1, Bizz Fuzz
Also written up in: mito753/CTF
- pwn
Same technique in picoCTF: lockdown-horses, Guessing Game 1, vr-school
- pwn
Same technique in picoCTF: lockdown-horses, Guessing Game 1, Bizz Fuzz
Also written up in: mito753/CTF
- pwn
Same technique in picoCTF: lockdown-horses, Guessing Game 1, Bizz Fuzz
- pwn
Same technique in picoCTF: lockdown-horses, Guessing Game 1, Bizz Fuzz
Darkside
1 official solutionAlso written up in: GonTanaka/CTF-Writeups
Also written up in: dishankgoel/CTF-Writeups
Forensics11
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: TwentySick/CTF, BrennenWright/CaptureTheFlag-Writeups
- forensics
Same technique in picoCTF: investigation_encoded_2, FindAndOpen, Ph4nt0m 1ntrud3r
Also written up in: not1cyyy/CTF-Writeups, TwentySick/CTF
- forensics
Same technique in picoCTF: investigation_encoded_2, FindAndOpen, Ph4nt0m 1ntrud3r
Also written up in: TwentySick/CTF
- forensics
Same technique in picoCTF: investigation_encoded_2, FindAndOpen, Ph4nt0m 1ntrud3r
Also written up in: TwentySick/CTF
- forensics
Same technique in picoCTF: Glory of the Garden, Investigative Reversing 0, Investigative Reversing 1
Also written up in: TwentySick/CTF
- forensics
Same technique in picoCTF: FindAndOpen, Ph4nt0m 1ntrud3r, WebNet0
Also written up in: SovietBeast/CTF-writeups
- forensics
Same technique in picoCTF: investigation_encoded_2, FindAndOpen, Ph4nt0m 1ntrud3r
Also written up in: SovietBeast/CTF-writeups
- forensics
Same technique in picoCTF: investigation_encoded_2, FindAndOpen, Ph4nt0m 1ntrud3r
- forensics
Same technique in picoCTF: investigation_encoded_2, FindAndOpen, Ph4nt0m 1ntrud3r
- forensics
Same technique in picoCTF: investigation_encoded_2, FindAndOpen, Ph4nt0m 1ntrud3r
Also written up in: TwentySick/CTF
- forensics
Same technique in picoCTF: investigation_encoded_2, FindAndOpen, Ph4nt0m 1ntrud3r
- forensics
Same technique in picoCTF: investigation_encoded_2, FindAndOpen, Ph4nt0m 1ntrud3r
Cryptography9
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: not1cyyy/CTF-Writeups, 12flamingo/CTF-writeups, 12flamingoes/CTF-writeups
- crypto
Same technique in picoCTF: It's Not My Fault 2, StegoRSA, AES-ABC
Also written up in: 12flamingo/CTF-writeups, 12flamingoes/CTF-writeups
- crypto
Same technique in picoCTF: It's Not My Fault 2, StegoRSA, AES-ABC
Also written up in: not1cyyy/CTF-Writeups
- crypto
Same technique in picoCTF: It's Not My Fault 2, StegoRSA, AES-ABC
Also written up in: not1cyyy/CTF-Writeups
- crypto
Same technique in picoCTF: It's Not My Fault 2, StegoRSA, AES-ABC
Also written up in: not1cyyy/CTF-Writeups
- 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
- 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
- crypto
Same technique in picoCTF: It's Not My Fault 2, StegoRSA, AES-ABC
Uncategorised7
The upstream scoreboard did not say, so neither do we.
Also written up in: mito753/CTF, mito753/CTF, mito753/CTF, mito753/CTF, mito753/CTF, mito753/CTF, mito753/CTF, mito753/CTF
Memo01
7 official solutionsAlso written up in: mito753/CTF, mito753/CTF, mito753/CTF, mito753/CTF, mito753/CTF, mito753/CTF, mito753/CTF
Dreadful Battle
1 official solutionAlso written up in: clairelevin/ctf-writeups
Exploit2
1 official solutionAlso written up in: mwales/security
Force
1 official solutionAlso written up in: zolutal/ctf-writeups
Spaceflight
1 official solutionAlso written up in: clairelevin/ctf-writeups
to the Dark Side
1 official solutionAlso written up in: mito753/CTF
Web5
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: SovietBeast/CTF-writeups, BrennenWright/CaptureTheFlag-Writeups, cryptocat.me
- web
Same technique in picoCTF: Live Art, secure-email-service, No FA
Also written up in: TwentySick/CTF, SovietBeast/CTF-writeups, BrennenWright/CaptureTheFlag-Writeups
- web
Same technique in picoCTF: Live Art, secure-email-service, No FA
Also written up in: BrennenWright/CaptureTheFlag-Writeups, BrennenWright/CaptureTheFlag-Writeups
- web
Same technique in picoCTF: Live Art, secure-email-service, No FA
Also written up in: BrennenWright/CaptureTheFlag-Writeups, BrennenWright/CaptureTheFlag-Writeups
- web
Same technique in picoCTF: Live Art, secure-email-service, No FA
Also written up in: BrennenWright/CaptureTheFlag-Writeups
- web
Same technique in picoCTF: Live Art, secure-email-service, No FA
Reverse engineering5
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: BrennenWright/CaptureTheFlag-Writeups
- re
Same technique in picoCTF: Checkpass, WinAntiDbg0x100, WinAntiDbg0x200
Also written up in: msaw328/ctf_writeups, msaw328/ctf_writeups
- re
Same technique in picoCTF: Checkpass, WinAntiDbg0x100, WinAntiDbg0x200
Also written up in: dishankgoel/CTF-Writeups, clairelevin/ctf-writeups
- re
Same technique in picoCTF: Checkpass, WinAntiDbg0x100, WinAntiDbg0x200
- re
Same technique in picoCTF: Checkpass, WinAntiDbg0x100, WinAntiDbg0x200
- re
Same technique in picoCTF: Checkpass, WinAntiDbg0x100, WinAntiDbg0x200
Misc3
Everything that fits no other box: esolangs, puzzles, scripting exercises, and the jail escapes that have not yet earned their own category.
- sanity_check
Same technique in picoCTF: PW Crack 2, Permissions, Specialer
- sanity_check
Same technique in picoCTF: PW Crack 2, Permissions, Specialer
- programming
Same technique in picoCTF: PW Crack 2, Permissions, Specialer
OSINT3
Answer a question about the real world from public sources. The work is pivoting between identifiers, not exploiting anything.
Also written up in: BrennenWright/CaptureTheFlag-Writeups
- osint
Same technique in picoCTF: CVE-XXXX-XXXX
Also written up in: BrennenWright/CaptureTheFlag-Writeups
- osint
Same technique in picoCTF: CVE-XXXX-XXXX
Also written up in: BrennenWright/CaptureTheFlag-Writeups
- osint
Same technique in picoCTF: CVE-XXXX-XXXX