JerseyCTF IV
22 challenges with 32 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 CTFtimeReverse engineering7
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: InfoSecIITR/write-ups
- rev
- bin
- easy
Same technique in picoCTF: Checkpass, WinAntiDbg0x100, WinAntiDbg0x200
- rev
- hard
- bin
Same technique in picoCTF: Checkpass, WinAntiDbg0x100, WinAntiDbg0x200
Also written up in: cyberghost13337.github.io
- rev
- bin
- easy
Same technique in picoCTF: Checkpass, WinAntiDbg0x100, WinAntiDbg0x200
- rev
- hard
- bin
Same technique in picoCTF: Checkpass, WinAntiDbg0x100, WinAntiDbg0x200
- rev
- hard
- bin
Same technique in picoCTF: Checkpass, WinAntiDbg0x100, WinAntiDbg0x200
- rev
- bin
- medium
Same technique in picoCTF: Checkpass, WinAntiDbg0x100, WinAntiDbg0x200
Cryptography5
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: nightxade/ctf-writeups
- hard
- crypto
Same technique in picoCTF: AES-ABC, Compress and Attack, cryptomaze
Also written up in: nightxade/ctf-writeups
- crypto
- medium
Same technique in picoCTF: It's Not My Fault 2, StegoRSA, AES-ABC
Also written up in: nightxade/ctf-writeups
- easy
- crypto
Same technique in picoCTF: It's Not My Fault 2, StegoRSA, AES-ABC
Also written up in: nightxade/ctf-writeups
- hard
- crypto
Same technique in picoCTF: It's Not My Fault 2, StegoRSA, AES-ABC
- easy
- crypto
Same technique in picoCTF: It's Not My Fault 2, StegoRSA, AES-ABC
Forensics3
Recover something from a file, a capture, or a disk image - often from a part of it the format says is unused.
Also written up in: nightxade/ctf-writeups
- forensics
- hard
Same technique in picoCTF: investigation_encoded_2, FindAndOpen, Ph4nt0m 1ntrud3r
- hard
- forensics
Same technique in picoCTF: investigation_encoded_2, FindAndOpen, Ph4nt0m 1ntrud3r
- easy
- forensics
Same technique in picoCTF: investigation_encoded_2, FindAndOpen, Ph4nt0m 1ntrud3r
Web2
Reach data or functionality the application meant to keep from you - through its inputs, its tokens, or its trust in the client.
- web
- easy
Same technique in picoCTF: Live Art, secure-email-service, No FA
- medium
- web
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.
- easy
- bin
- rev
Same technique in picoCTF: lockdown-horses, Guessing Game 1, Bizz Fuzz
- easy
- bin
- rev
Same technique in picoCTF: lockdown-horses, Guessing Game 1, Bizz Fuzz
OSINT2
Answer a question about the real world from public sources. The work is pivoting between identifiers, not exploiting anything.
Also written up in: nightxade/ctf-writeups
- medium
- osint
Same technique in picoCTF: CVE-XXXX-XXXX
Also written up in: nightxade/ctf-writeups
- hard
- osint
Same technique in picoCTF: CVE-XXXX-XXXX
Misc1
Everything that fits no other box: esolangs, puzzles, scripting exercises, and the jail escapes that have not yet earned their own category.
- misc
- medium
Same technique in picoCTF: PW Crack 2, Permissions, Specialer