GrabCON CTF 2021
35 challenges with 87 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 CTFtimeUncategorised8
The upstream scoreboard did not say, so neither do we.
Also written up in: mito753/CTF, mito753/CTF, mito753/CTF
Memo01
3 official solutionsAlso written up in: mito753/CTF, mito753/CTF, mito753/CTF
Unknown
2 official solutionsAlso written up in: KaligulaArmblessed/CTF-Writeups, KaligulaSec/CTF-Writeups
Also written up in: mito753/CTF
Easybin
1 official solutionAlso written up in: mito753/CTF
Phpinfo
1 official solutionAlso written up in: technical-ko/Writeups
Scandir
1 official solutionAlso written up in: technical-ko/Writeups
Show Source
1 official solutionAlso written up in: technical-ko/Writeups
OSINT6
Answer a question about the real world from public sources. The work is pivoting between identifiers, not exploiting anything.
Also written up in: vichhka-git/CTF-Writeup, vichhika/CTF-Writeup
- osint
Same technique in picoCTF: CVE-XXXX-XXXX
Also written up in: vichhka-git/CTF-Writeup, floatingbrij/ctf-writeups, vichhika/CTF-Writeup
- osint
Same technique in picoCTF: CVE-XXXX-XXXX
Also written up in: vichhka-git/CTF-Writeup, vichhika/CTF-Writeup
- osint
Same technique in picoCTF: CVE-XXXX-XXXX
- osint
Same technique in picoCTF: CVE-XXXX-XXXX
- osint
Same technique in picoCTF: CVE-XXXX-XXXX
- osint
Same technique in picoCTF: CVE-XXXX-XXXX
Binary 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: mito753/Kernel-Exploit-Dojo, mito753/Kernel-Exploit-Dojo, mito753/Kernel-Exploit-Dojo, mito753/Kernel-Exploit-Dojo, mito753/Kernel-Exploit-Dojo, mito753/Kernel-Exploit-Dojo, mito753/Kernel-Exploit-Dojo, mito753/Kernel-Exploit-Dojo
- format-string
- pwn
- kernel
Same technique in picoCTF: PIE TIME 2, Binary Gauntlet 2, Binary Gauntlet 3
Also written up in: mito753/CTF
- stack_overflow
- stack_canaries
- pwn
Same technique in picoCTF: lockdown-horses, Guessing Game 1, Bizz Fuzz
Cancancan Solve
1 official solutionAlso written up in: yl-ang/CTF
- pwn
Same technique in picoCTF: lockdown-horses, Guessing Game 1, Bizz Fuzz
Pwn2 Solve
1 official solutionAlso written up in: yl-ang/CTF
Forensics5
Recover something from a file, a capture, or a disk image - often from a part of it the format says is unused.
- autopsy
- forensic
- rdp
Same technique in picoCTF: investigation_encoded_2, FindAndOpen, Ph4nt0m 1ntrud3r
- forensics
Same technique in picoCTF: investigation_encoded_2, FindAndOpen, Ph4nt0m 1ntrud3r
- forensics
- forensic
- android-forensics
Same technique in picoCTF: Mob psycho, investigation_encoded_2, FindAndOpen
- forensics
Same technique in picoCTF: investigation_encoded_2, FindAndOpen, Ph4nt0m 1ntrud3r
- autopsy
- forensic
Same technique in picoCTF: investigation_encoded_2, FindAndOpen, Ph4nt0m 1ntrud3r
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: vichhka-git/CTF-Writeup, technical-ko/Writeups, vichhika/CTF-Writeup
- web
Same technique in picoCTF: Live Art, secure-email-service, No FA
Also written up in: vichhka-git/CTF-Writeup, vichhika/CTF-Writeup
- web
Same technique in picoCTF: Live Art, secure-email-service, No FA
- web
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: KaligulaArmblessed/CTF-Writeups, vichhka-git/CTF-Writeup, KaligulaSec/CTF-Writeups, vichhika/CTF-Writeup
- revesing
Same technique in picoCTF: Checkpass, WinAntiDbg0x100, WinAntiDbg0x200
Easyrev
4 official solutionsAlso written up in: KaligulaArmblessed/CTF-Writeups, vichhka-git/CTF-Writeup, KaligulaSec/CTF-Writeups, vichhika/CTF-Writeup
- reverse
- engineering
Same technique in picoCTF: Checkpass, WinAntiDbg0x100, WinAntiDbg0x200
- rev
Same technique in picoCTF: Checkpass, WinAntiDbg0x100, WinAntiDbg0x200
Cryptography2
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
- crypto
Same technique in picoCTF: It's Not My Fault 2, StegoRSA, AES-ABC
Misc1
Everything that fits no other box: esolangs, puzzles, scripting exercises, and the jail escapes that have not yet earned their own category.
Find me
2 official solutionsAlso written up in: vichhka-git/CTF-Writeup, vichhika/CTF-Writeup