Digital Overdose 2021 Autumn CTF
38 challenges with 76 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 CTFtimeMisc11
Everything that fits no other box: esolangs, puzzles, scripting exercises, and the jail escapes that have not yet earned their own category.
git commit -m whatever
3 writeupsSame technique in picoCTF: Blame Game, Collaborative Development, Commitment Issues
Hash1
3 writeupsSame technique in picoCTF: PW Crack 3, PW Crack 4, PW Crack 5
- logs
Same technique in picoCTF: PW Crack 2, Permissions, Specialer
- logs
Same technique in picoCTF: PW Crack 2, Permissions, Specialer
- logs
Same technique in picoCTF: PW Crack 2, Permissions, Specialer
Hash4
2 writeupsSame technique in picoCTF: PW Crack 3, PW Crack 4, PW Crack 5
Not exactly Nestene's Autons
2 writeupsSame technique in picoCTF: PW Crack 2, Permissions, Specialer
Phreak File
2 writeupsSame technique in picoCTF: PW Crack 2, Permissions, Specialer
- misc
Same technique in picoCTF: PW Crack 2, Permissions, Specialer
Hash2
1 writeupSame technique in picoCTF: PW Crack 3, PW Crack 4, PW Crack 5
Hash3
1 writeupSame technique in picoCTF: PW Crack 3, PW Crack 4, PW Crack 5
OSINT11
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
Same technique in picoCTF: CVE-XXXX-XXXX
- osint
Same technique in picoCTF: CVE-XXXX-XXXX
- osint
Same technique in picoCTF: CVE-XXXX-XXXX
- osint
Same technique in picoCTF: CVE-XXXX-XXXX
- misc
- osint
Same technique in picoCTF: CVE-XXXX-XXXX
- osint
Same technique in picoCTF: CVE-XXXX-XXXX
- osint
Same technique in picoCTF: CVE-XXXX-XXXX
- osint
Same technique in picoCTF: CVE-XXXX-XXXX
- osint
Same technique in picoCTF: CVE-XXXX-XXXX
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.
Also written up in: nobodyisnobody/write-ups
- libc-2.31
- pwn
- heap
- doublefree
- tcache-poisoning
Same technique in picoCTF: vr-school, sice_cream, zero_to_hero
- bufferoverflow
- pwn
- srop
Same technique in picoCTF: lockdown-horses, Guessing Game 1, vr-school
- bufferoverflow
- pwn
- srop
Same technique in picoCTF: lockdown-horses, Guessing Game 1, vr-school
Also written up in: nobodyisnobody/write-ups
- forma
- pwn
Same technique in picoCTF: lockdown-horses, Guessing Game 1, Bizz Fuzz
- source
- seccomp
- sourcecodeanalysis
- shellcode
Same technique in picoCTF: handoff, Binary Gauntlet 2, Kit Engine
Working.Exploit
1 official solutionAlso written up in: nobodyisnobody/write-ups
Uncategorised3
The upstream scoreboard did not say, so neither do we.
Flavour Public
3 official solutionsAlso written up in: vital-information-resource-under-siege/PWN-Challenges, vital-information-resource-under-siege/PWN-Challenges, vital-information-resource-under-siege/PWN-Challenges
Also written up in: vital-information-resource-under-siege/PWN-Challenges, vital-information-resource-under-siege/PWN-Challenges
Also written up in: vital-information-resource-under-siege/PWN-Challenges, vital-information-resource-under-siege/PWN-Challenges
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.
Cryptography: All around the word
1 writeupSame technique in picoCTF: It's Not My Fault 2, StegoRSA, AES-ABC
Cryptography: Simply Cipher
1 writeupSame technique in picoCTF: It's Not My Fault 2, StegoRSA, AES-ABC
Web2
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: anhchangmutrang/CTF
- web
Same technique in picoCTF: Live Art, secure-email-service, No FA
- web
Same technique in picoCTF: Live Art, secure-email-service, No FA
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: acdwas/ctf
- reversing
Same technique in picoCTF: Checkpass, WinAntiDbg0x100, WinAntiDbg0x200
- reversing
Same technique in picoCTF: Checkpass, WinAntiDbg0x100, WinAntiDbg0x200
Steganography1
Find the payload hidden inside a carrier that looks ordinary. Bit planes, appended data, metadata, and audio spectrograms.
- steganography
Same technique in picoCTF: StegoRSA, Glory of the Garden, Investigative Reversing 0