Pragyan CTF 2019
41 challenges with 122 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 CTFtimeUncategorised20
The upstream scoreboard did not say, so neither do we.
Also written up in: yuawn/CTF, yuawn/CTF, yuawn/CTF, ssspeedgit00/CTF, ssspeedgit00/CTF, ssspeedgit00/CTF
Cookie
2 official solutionsAlso written up in: wani-hackase/wani-writeup, posgnu/ctfs
Cry Decode
2 official solutionsAlso written up in: wani-hackase/wani-writeup, wani-hackase/wani-writeup
Bin Feed
1 official solutionAlso written up in: jt00000/ctf.writeup
Bin Feed Me
1 official solutionAlso written up in: wani-hackase/wani-writeup
Cry Add Them
1 official solutionAlso written up in: wani-hackase/wani-writeup
Cry Easyrsa
1 official solutionAlso written up in: wani-hackase/wani-writeup
Cry Help
1 official solutionAlso written up in: wani-hackase/wani-writeup
Cry Phoenix
1 official solutionAlso written up in: wani-hackase/wani-writeup
For Magic Pngs
1 official solutionAlso written up in: wani-hackase/wani-writeup
For Welcome
1 official solutionAlso written up in: wani-hackase/wani-writeup
Foren Magic Pngs
1 official solutionAlso written up in: netonehc/write-ups
Foren Welcome
1 official solutionAlso written up in: netonehc/write-ups
Mandatory
1 official solutionAlso written up in: wani-hackase/wani-writeup
Mis Exorcism
1 official solutionAlso written up in: wani-hackase/wani-writeup
RSAfracCont
1 official solutionAlso written up in: zst-ctf/pragyanctf-2019-writeups
Solve Sympy
1 official solutionAlso written up in: zst-ctf/pragyanctf-2019-writeups
Also written up in: zst-ctf/pragyanctf-2019-writeups
Also written up in: FlagaDoS/WriteUp
Also written up in: FlagaDoS/WriteUp
Cryptography8
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: rsa-ctf/write-ups, rsa-ctf/write-ups, ctf.0xff.re
- crypto
Same technique in picoCTF: It's Not My Fault 2, StegoRSA, AES-ABC
- misc
- crypto
Same technique in picoCTF: It's Not My Fault 2, StegoRSA, AES-ABC
Also written up in: zst-ctf/pragyanctf-2019-writeups
- crypto
Same technique in picoCTF: It's Not My Fault 2, StegoRSA, AES-ABC
Also written up in: rsa-ctf/write-ups
- crypto
- xor
Same technique in picoCTF: Custom encryption, XtraORdinary, It's Not My Fault 2
- crypto
Same technique in picoCTF: It's Not My Fault 2, StegoRSA, john_pollard
Also written up in: rsa-ctf/write-ups
- crypto
Same technique in picoCTF: It's Not My Fault 2, StegoRSA, AES-ABC
Also written up in: zst-ctf/pragyanctf-2019-writeups, rsa-ctf/write-ups
- crypto
Same technique in picoCTF: It's Not My Fault 2, StegoRSA, AES-ABC
Forensics6
Recover something from a file, a capture, or a disk image - often from a part of it the format says is unused.
- forensic
Same technique in picoCTF: investigation_encoded_2, FindAndOpen, Ph4nt0m 1ntrud3r
Also written up in: zst-ctf/pragyanctf-2019-writeups, theflagisnothere.github.io
- forensics
Same technique in picoCTF: investigation_encoded_2, FindAndOpen, Ph4nt0m 1ntrud3r
Also written up in: face0xff/ctf, zst-ctf/pragyanctf-2019-writeups, zst-ctf/pragyanctf-2019-writeups, ctf.0xff.re
- usb
- pcap
- forensics
Same technique in picoCTF: FindAndOpen, Ph4nt0m 1ntrud3r, WebNet0
- forensics
Same technique in picoCTF: investigation_encoded_2, FindAndOpen, Ph4nt0m 1ntrud3r
- forensics
Same technique in picoCTF: investigation_encoded_2, FindAndOpen, Ph4nt0m 1ntrud3r
- forensic
Same technique in picoCTF: investigation_encoded_2, FindAndOpen, Ph4nt0m 1ntrud3r
Web3
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: fyxme/writeups, netonehc/write-ups, theflagisnothere.github.io
- web
Same technique in picoCTF: logon, More Cookies, Cookie Monster Secret Recipe
- web
Same technique in picoCTF: Live Art, secure-email-service, No FA
- web
- guessing
Same technique in picoCTF: Live Art, secure-email-service, No FA
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.
Also written up in: zst-ctf/pragyanctf-2019-writeups, posgnu/ctfs
- exploitation
Same technique in picoCTF: lockdown-horses, Guessing Game 1, Bizz Fuzz
Also written up in: face0xff/ctf, zst-ctf/pragyanctf-2019-writeups, ctf.0xff.re
- binary
- linux
- crackme
Same technique in picoCTF: hijacking, VNE, lockdown-horses
Misc2
Everything that fits no other box: esolangs, puzzles, scripting exercises, and the jail escapes that have not yet earned their own category.
- exploiting
Same technique in picoCTF: PW Crack 2, Permissions, Specialer
- binaryexploitation
Same technique in picoCTF: PW Crack 2, Permissions, Specialer