nullcom HackIM 2018
25 challenges with 55 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 CTFtimeWeb8
Reach data or functionality the application meant to keep from you - through its inputs, its tokens, or its trust in the client.
- web
Same technique in picoCTF: Live Art, secure-email-service, No FA
Tax Aversion 500
2 official solutionsAlso written up in: rkmylo/ctf-write-ups, rkmylo/ctf-write-ups
- web
- python
Same technique in picoCTF: Live Art, secure-email-service, No FA
- web
- bruteforce
- jwt
- json
Same technique in picoCTF: Java Code Analysis!?!, JaWT Scratchpad, JAuth
- web
- aws
- lambda
Same technique in picoCTF: Live Art, secure-email-service, No FA
- jwt
- sqlinjection
- web
Same technique in picoCTF: Irish-Name-Repo 3, Startup Company, Java Code Analysis!?!
- web
Same technique in picoCTF: Live Art, secure-email-service, No FA
- web
Same technique in picoCTF: Live Art, secure-email-service, No FA
OSINT4
Answer a question about the real world from public sources. The work is pivoting between identifiers, not exploiting anything.
- osint
Same technique in picoCTF: CVE-XXXX-XXXX
- osint
Same technique in picoCTF: CVE-XXXX-XXXX
- osint
- forensics
Same technique in picoCTF: CVE-XXXX-XXXX
- osint
- malware
- vt
Same technique in picoCTF: CVE-XXXX-XXXX
Uncategorised4
The upstream scoreboard did not say, so neither do we.
Orangefarmer
2 official solutionsAlso written up in: HMPerson1/ctf-writeups, HMPerson1/ctf-writeups
Also written up in: abeaumont/ctfs, abeaumont/ctfs
Also written up in: AnisBoss/CTFs
Decomp
1 official solutionAlso written up in: HMPerson1/ctf-writeups
Cryptography3
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.
- blockchain
- mining
- crypto
Same technique in picoCTF: It's Not My Fault 2, StegoRSA, AES-ABC
- crypto
Same technique in picoCTF: It's Not My Fault 2, StegoRSA, AES-ABC
- crypto
- iv
- aes-128-cbc
Same technique in picoCTF: AES-ABC, Compress and Attack, cryptomaze
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.
- pwn
Same technique in picoCTF: lockdown-horses, Guessing Game 1, Bizz Fuzz
- exploiting
Same technique in picoCTF: lockdown-horses, Guessing Game 1, Bizz Fuzz
Reverse engineering1
Work out what a compiled program does without its source, then work backwards from the check to the input that passes it.
- reversing
- arm
Same technique in picoCTF: ARMssembly 0, ARMssembly 1, ARMssembly 2
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: ambalabanov/writeups, ambalabanov/writeups
- pcapng
- wireshark
- forensics
Same technique in picoCTF: FindAndOpen, Ph4nt0m 1ntrud3r, WebNet0
Steganography1
Find the payload hidden inside a carrier that looks ordinary. Bit planes, appended data, metadata, and audio spectrograms.
- stego
Same technique in picoCTF: StegoRSA, Glory of the Garden, Investigative Reversing 0
Misc1
Everything that fits no other box: esolangs, puzzles, scripting exercises, and the jail escapes that have not yet earned their own category.
Also written up in: pzyc0k/ctf-write-ups