corCTF 2022
28 challenges with 39 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 CTFtimeCryptography9
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
- lattice
- elliptic
- curves
Same technique in picoCTF: MSS_ADVANCE Revenge, Not TRUe, StegoRSA
- rsa
- crypto
Same technique in picoCTF: StegoRSA, john_pollard, rsa_oracle
- crypto
- modular-arithmetic
Same technique in picoCTF: StegoRSA, Timestamped Secrets, AES-ABC
- dlp
- lcg
- diffie-hellman
- crypto
Same technique in picoCTF: StegoRSA, Timestamped Secrets, AES-ABC
- oracle
- crypto
- okamoto-uchiyama
Same technique in picoCTF: StegoRSA, Timestamped Secrets, AES-ABC
- lcg
- crypto
Same technique in picoCTF: StegoRSA, Timestamped Secrets, AES-ABC
- crypto
- modular-arithmetic
- lcg
Same technique in picoCTF: StegoRSA, Timestamped Secrets, AES-ABC
- crypto
- lfsr
Same technique in picoCTF: StegoRSA, Timestamped Secrets, AES-ABC
- coppersmith
- crypto
- ecc
- rsa
Same technique in picoCTF: StegoRSA, john_pollard, rsa_oracle
Reverse engineering6
Work out what a compiled program does without its source, then work backwards from the check to the input that passes it.
- elf
- msdos
- rev
- polyglot
Same technique in picoCTF: file-run2, WinAntiDbg0x100, WinAntiDbg0x200
- avx256
- rev
Same technique in picoCTF: WinAntiDbg0x100, WinAntiDbg0x200, WinAntiDbg0x300
- rev
- rockyou
- windows
Same technique in picoCTF: WinAntiDbg0x100, WinAntiDbg0x200, WinAntiDbg0x300
- obfuscation
- rev
- antidecompile
Same technique in picoCTF: WinAntiDbg0x100, WinAntiDbg0x200, WinAntiDbg0x300
- jit
- rev
- vm
- rust
Same technique in picoCTF: WinAntiDbg0x100, WinAntiDbg0x200, WinAntiDbg0x300
- llil
- riscv
- rev
- vm
- linalg
Same technique in picoCTF: WinAntiDbg0x100, WinAntiDbg0x200, WinAntiDbg0x300
Web5
Reach data or functionality the application meant to keep from you - through its inputs, its tokens, or its trust in the client.
- web
- quiz
- json
- post
Same technique in picoCTF: Client-side-again, dont-use-client-side, Irish-Name-Repo 3
- dom-clobbering
- web
- react
Same technique in picoCTF: Client-side-again, dont-use-client-side, Irish-Name-Repo 3
- command
- injection
- blackbox
- web
Same technique in picoCTF: Client-side-again, dont-use-client-side, Irish-Name-Repo 3
- deserialization
- web
- rust
Same technique in picoCTF: Client-side-again, dont-use-client-side, Irish-Name-Repo 3
- nodejs
- express
- readfilesync
- web
Same technique in picoCTF: Client-side-again, dont-use-client-side, Irish-Name-Repo 3
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.
- ret2libc
- pwn
- rust
Same technique in picoCTF: Guessing Game 1, x-sixty-what, format string 3
- largebin
- pwn
- tcache-poisoning
- heap-overflow
Same technique in picoCTF: Guessing Game 1, x-sixty-what, PIE TIME 2
- pwn
- kernel
- cross-cache
Same technique in picoCTF: Guessing Game 1, x-sixty-what, format string 3
- kernel
- pwn
- docker-escape
Same technique in picoCTF: Guessing Game 1, x-sixty-what, format string 3
- zig
- pwn
- heap
Same technique in picoCTF: tea-cash, sice_cream, zero_to_hero
Misc2
Everything that fits no other box: esolangs, puzzles, scripting exercises, and the jail escapes that have not yet earned their own category.
- javascript
- sandbox
- misc
Same technique in picoCTF: Permissions, Specialer, Codebook
- solana
Same technique in picoCTF: Permissions, Specialer, Codebook
Forensics1
Recover something from a file, a capture, or a disk image - often from a part of it the format says is unused.
- forensics
- wireshark
- drm
Same technique in picoCTF: FindAndOpen, WebNet0, WebNet1