nullcon HackIM 2019
33 challenges with 86 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. 20 of them also carry the solution nullcon HackIM 2019’s own organisers published, which is linked on the challenge itself.
Full task list on CTFtimeBinary exploitation10
Turn a memory-safety bug in a native binary into control of execution. Usually a stack overflow, a format string, or a heap primitive.
Published by the organisers in nullcon/hackim-2019: README.MD
Also written up in: 5unKn0wn/ctfs, guyinatuxedo/ctf, guyinatuxedo/ctf
- pwn
Same technique in picoCTF: lockdown-horses, Guessing Game 1, Bizz Fuzz
Published by the organisers in nullcon/hackim-2019: README.md
Also written up in: anggerdeni/ctf-writeup-old, 5unKn0wn/ctfs, guyinatuxedo/ctf, anggerdeni/ctf-writeup-old, guyinatuxedo/ctf
- shellcode
- pwn
Same technique in picoCTF: handoff, Binary Gauntlet 2, Kit Engine
Published by the organisers in nullcon/hackim-2019: README.MD
Also written up in: shift-crops/CTFWriteups, shift-crops/CTFWriteups
- pwn
Same technique in picoCTF: lockdown-horses, Guessing Game 1, Bizz Fuzz
Published by the organisers in nullcon/hackim-2019: README.md
Also written up in: guyinatuxedo/ctf, guyinatuxedo/ctf
- shellcode
- pwn
Same technique in picoCTF: handoff, Binary Gauntlet 2, Kit Engine
Published by the organisers in nullcon/hackim-2019: README.MD
Also written up in: shift-crops/CTFWriteups
- pwn
Same technique in picoCTF: lockdown-horses, Guessing Game 1, Bizz Fuzz
Amd64 Alphanum Encoder
1 official solutionAlso written up in: anggerdeni/ctf-writeup-old
Analysis and Exploitation of Prototype Pollution attacks on NodeJs
1 official solutionAlso written up in: blog.0daylabs.com
Local Exploit
1 official solutionAlso written up in: guyinatuxedo/ctf
Remote Exploit
1 official solutionAlso written up in: guyinatuxedo/ctf
Also written up in: guyinatuxedo/ctf
Web8
Reach data or functionality the application meant to keep from you - through its inputs, its tokens, or its trust in the client.
Published by the organisers in nullcon/hackim-2019: README.MD, exploit/decode.py, exploit/img.php
Also written up in: ctf-solutions/ctf
- web
Same technique in picoCTF: Live Art, secure-email-service, No FA
Also written up in: ctf-solutions/ctf
- web
Same technique in picoCTF: Live Art, secure-email-service, No FA
Published by the organisers in nullcon/hackim-2019: README.MD, exploit/fps.js
- web
Same technique in picoCTF: Live Art, secure-email-service, No FA
Also written up in: aadityapurani.com
- web
Same technique in picoCTF: Live Art, secure-email-service, No FA
- web
Same technique in picoCTF: Live Art, secure-email-service, No FA
Published by the organisers in nullcon/hackim-2019: README.MD
Published by the organisers in nullcon/hackim-2019: README.MD
Published by the organisers in nullcon/hackim-2019: README.MD
Reverse engineering5
Work out what a compiled program does without its source, then work backwards from the check to the input that passes it.
Published by the organisers in nullcon/hackim-2019: solution/reveal.cpp, solution/sol.py
- reverse
Same technique in picoCTF: Checkpass, WinAntiDbg0x100, WinAntiDbg0x200
- reverse
- engineering
Same technique in picoCTF: Checkpass, WinAntiDbg0x100, WinAntiDbg0x200
Published by the organisers in nullcon/hackim-2019: solution/dis.sh
- reverse
Same technique in picoCTF: Checkpass, WinAntiDbg0x100, WinAntiDbg0x200
Published by the organisers in nullcon/hackim-2019: README.md
- reverse
Same technique in picoCTF: Checkpass, WinAntiDbg0x100, WinAntiDbg0x200
Published by the organisers in nullcon/hackim-2019: solution/time_machine.cpp
Cryptography4
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.
Published by the organisers in nullcon/hackim-2019: README.md
Also written up in: anggerdeni/ctf-writeup-old, nevivurn/writeups, nevivurn/writeups
- crypto
Same technique in picoCTF: It's Not My Fault 2, StegoRSA, AES-ABC
Published by the organisers in nullcon/hackim-2019: README.md
Also written up in: Ariana1729/CTF-Writeups, n0tsobad/ctf-writeups, Ariana1729/CTF-Writeups
- crytography
Same technique in picoCTF: It's Not My Fault 2, StegoRSA, AES-ABC
Published by the organisers in nullcon/hackim-2019: README.md, solve.py
Also written up in: Ariana1729/CTF-Writeups, Ariana1729/CTF-Writeups
- crypto
Same technique in picoCTF: It's Not My Fault 2, StegoRSA, AES-ABC
Server
2 official solutionsAlso written up in: anggerdeni/ctf-writeup-old, nevivurn/writeups
Misc4
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: aadityapurani/My-CTF-Solutions
- machine_learning
- misc
Same technique in picoCTF: PW Crack 2, Permissions, Specialer
Published by the organisers in nullcon/hackim-2019: README.MD
- captcha
- misc
Same technique in picoCTF: PW Crack 2, Permissions, Specialer
Published by the organisers in nullcon/hackim-2019: README.MD
- captcha
- misc
Same technique in picoCTF: PW Crack 2, Permissions, Specialer
Published by the organisers in nullcon/hackim-2019: README.md
- misc
- emoji
Same technique in picoCTF: PW Crack 2, Permissions, Specialer
Uncategorised2
The upstream scoreboard did not say, so neither do we.
Also written up in: nevivurn/writeups
Also written up in: ctf-solutions/ctf