VolgaCTF 2022 Qualifier
12 challenges with 16 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 CTFtimeWeb5
Reach data or functionality the application meant to keep from you - through its inputs, its tokens, or its trust in the client.
- js
- web
Same technique in picoCTF: Live Art, secure-email-service, No FA
Also written up in: BlackFan/ctfs
- web
Same technique in picoCTF: Live Art, secure-email-service, No FA
Also written up in: BlackFan/ctfs
- 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
Binary exploitation4
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
Same technique in picoCTF: lockdown-horses, Guessing Game 1, Bizz Fuzz
- pwn
- integer-overflow
- seccomp
Same technique in picoCTF: lockdown-horses, Guessing Game 1, Bizz Fuzz
- pwn
Same technique in picoCTF: lockdown-horses, Guessing Game 1, Bizz Fuzz
Also written up in: shellphish/writeups
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
Reverse engineering1
Work out what a compiled program does without its source, then work backwards from the check to the input that passes it.
- reverse
Same technique in picoCTF: Checkpass, WinAntiDbg0x100, WinAntiDbg0x200
Uncategorised1
The upstream scoreboard did not say, so neither do we.
Also written up in: BlackFan/ctfs, BlackFan/ctfs