PwnMe Qualifications : "8 bits"
25 challenges with 41 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 CTFtimeWeb6
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: siunam321/CTF-Writeups, blog.hitc.at
- web
Same technique in picoCTF: Live Art, secure-email-service, No FA
Also written up in: siunam321/CTF-Writeups, blog.hitc.at
- web
Same technique in picoCTF: Live Art, secure-email-service, No FA
Also written up in: siunam321/CTF-Writeups
- web
Same technique in picoCTF: Live Art, secure-email-service, No FA
QRDoor Code
2 official solutionsAlso written up in: siunam321/CTF-Writeups, blog.hitc.at
Anozer
1 official solutionAlso written up in: blog.hitc.at
Nestapp
1 official solutionAlso written up in: siunam321/CTF-Writeups
Binary exploitation6
Turn a memory-safety bug in a native binary into control of execution. Usually a stack overflow, a format string, or a heap primitive.
Heap-hop
1 writeupAlso written up in: 5kuuk/CTF-writeups
Same technique in picoCTF: vr-school, sice_cream, zero_to_hero
Me If You Kern
2 official solutionsAlso written up in: ret2school/ctf, ret2school/ctf
Cpython101
1 official solutionAlso written up in: ret2school/ctf
Also written up in: ret2school/ctf
Also written up in: ret2school/ctf
VIP at libc
1 writeupSame technique in picoCTF: lockdown-horses, Guessing Game 1, Bizz Fuzz
OSINT6
Answer a question about the real world from public sources. The work is pivoting between identifiers, not exploiting anything.
Also written up in: blog.hitc.at
- osint
Same technique in picoCTF: CVE-XXXX-XXXX
Also written up in: blog.hitc.at
- osint
Same technique in picoCTF: CVE-XXXX-XXXX
Also written up in: blog.hitc.at
- osint
Same technique in picoCTF: CVE-XXXX-XXXX
Also written up in: blog.hitc.at
- osint
Same technique in picoCTF: CVE-XXXX-XXXX
- osint
Same technique in picoCTF: CVE-XXXX-XXXX
John Droper
1 official solutionAlso written up in: ByAziX/CTF
Reverse engineering2
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: siunam321/CTF-Writeups
- reverse
Same technique in picoCTF: Checkpass, WinAntiDbg0x100, WinAntiDbg0x200
Also written up in: siunam321/CTF-Writeups
- reverse
Same technique in picoCTF: Checkpass, WinAntiDbg0x100, WinAntiDbg0x200
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.
Chall1 Intro Crypto
1 official solutionAlso written up in: ByAziX/CTF
Scream Like Viking
1 official solutionAlso written up in: ret2school/ctf
Forensics1
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: siunam321/CTF-Writeups
- forensics
Same technique in picoCTF: investigation_encoded_2, FindAndOpen, Ph4nt0m 1ntrud3r
Misc1
Everything that fits no other box: esolangs, puzzles, scripting exercises, and the jail escapes that have not yet earned their own category.
chip8
1 writeupAlso written up in: ret2school/ctf
Same technique in picoCTF: PW Crack 2, Permissions, Specialer
Uncategorised1
The upstream scoreboard did not say, so neither do we.
Expop
1 official solutionAlso written up in: 5kuuk/CTF-writeups