CyBRICS CTF 2020
23 challenges with 45 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 CTFtimeMisc7
Everything that fits no other box: esolangs, puzzles, scripting exercises, and the jail escapes that have not yet earned their own category.
- c
- c++
- bytecode
- python3.8
Same technique in picoCTF: PW Crack 1, PW Crack 2, PW Crack 3
- ez
Same technique in picoCTF: Permissions, Specialer, Codebook
- cyber
Same technique in picoCTF: Permissions, Specialer, Codebook
XCorp
2 writeupsSame technique in picoCTF: Permissions, Specialer, Codebook
- rebyc
Same technique in picoCTF: Permissions, Specialer, Codebook
- rc4
- cpython
Same technique in picoCTF: Permissions, Specialer, Codebook
- rebyc
Same technique in picoCTF: Permissions, Specialer, Codebook
Forensics5
Recover something from a file, a capture, or a disk image - often from a part of it the format says is unused.
- forensics
- networking
Same technique in picoCTF: FindAndOpen, c0rrupt, extensions
- forensics
Same technique in picoCTF: FindAndOpen, c0rrupt, extensions
- forensics
- network
Same technique in picoCTF: FindAndOpen, c0rrupt, extensions
- spoofing
- iscsi
- arp
- network
Same technique in picoCTF: FindAndOpen, c0rrupt, extensions
- network
- rev
- ssh
Same technique in picoCTF: FindAndOpen, c0rrupt, extensions
Reverse engineering4
Work out what a compiled program does without its source, then work backwards from the check to the input that passes it.
- rev
Same technique in picoCTF: WinAntiDbg0x100, WinAntiDbg0x200, WinAntiDbg0x300
Same technique in picoCTF: WinAntiDbg0x100, WinAntiDbg0x200, WinAntiDbg0x300
- reverse
- forensics
- sqli
Same technique in picoCTF: WinAntiDbg0x100, WinAntiDbg0x200, WinAntiDbg0x300
- rebyc
Same technique in picoCTF: WinAntiDbg0x100, WinAntiDbg0x200, WinAntiDbg0x300
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.
- rsa
- crypto
Same technique in picoCTF: StegoRSA, john_pollard, rsa_oracle
- signals
- crypto
- reverse
Same technique in picoCTF: StegoRSA, Timestamped Secrets, AES-ABC
Web2
Reach data or functionality the application meant to keep from you - through its inputs, its tokens, or its trust in the client.
- web
Same technique in picoCTF: Client-side-again, dont-use-client-side, Irish-Name-Repo 3
- web
Same technique in picoCTF: Client-side-again, dont-use-client-side, Irish-Name-Repo 3
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.
- pwn
- forensics
- reverse
Same technique in picoCTF: Guessing Game 1, x-sixty-what, format string 3
- linux
- pwn
Same technique in picoCTF: CVE-XXXX-XXXX, hijacking, VNE
OSINT1
Answer a question about the real world from public sources. The work is pivoting between identifiers, not exploiting anything.
Google Cloud
3 writeupsSame technique in picoCTF: Permissions, Specialer, Codebook