Syskron Security CTF 2020
30 challenges with 149 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 CTFtimeMisc10
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: CTF-STeam/ctf-writeups, ajh11g/CTF, gg0h/CTF, h0ffayyy/CTF, holypower777/ctf_writeups
- image-analysis
Same technique in picoCTF: PW Crack 2, Permissions, Specialer
Also written up in: satoki/ctf_writeups, klassiker/ctf-writeups, holypower777/ctf_writeups
- best-practices
Same technique in picoCTF: PW Crack 2, Permissions, Specialer
Also written up in: satoki/ctf_writeups, klassiker/ctf-writeups, holypower777/ctf_writeups
- plc-programming
Same technique in picoCTF: PW Crack 2, Permissions, Specialer
- welcome
- reading
Same technique in picoCTF: PW Crack 2, Permissions, Specialer
Also written up in: gg0h/CTF
- standard
Same technique in picoCTF: PW Crack 2, Permissions, Specialer
Also written up in: satoki/ctf_writeups
- malware
Same technique in picoCTF: PW Crack 2, Permissions, Specialer
Also written up in: satoki/ctf_writeups
- standard
- framework
Same technique in picoCTF: PW Crack 2, Permissions, Specialer
- vulnerability
Same technique in picoCTF: PW Crack 2, Permissions, Specialer
- malware
Same technique in picoCTF: PW Crack 2, Permissions, Specialer
- webcam
Same technique in picoCTF: PW Crack 2, Permissions, Specialer
Uncategorised5
The upstream scoreboard did not say, so neither do we.
Letter
1 official solutionAlso written up in: lightningsarp/CTF-Players
Monday
1 official solutionAlso written up in: QzSG/CTF-Write-Ups
Thursday
1 official solutionAlso written up in: QzSG/CTF-Write-Ups
Tuesday
1 official solutionAlso written up in: QzSG/CTF-Write-Ups
Wednesday
1 official solutionAlso written up in: QzSG/CTF-Write-Ups
Forensics4
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: satoki/ctf_writeups, klassiker/ctf-writeups, B34nB01z/writeups, gg0h/CTF, lightningsarp/CTF-Players
- packet-analysis
Same technique in picoCTF: investigation_encoded_2, FindAndOpen, Ph4nt0m 1ntrud3r
Also written up in: klassiker/ctf-writeups, lightningsarp/CTF-Players
- forensics
Same technique in picoCTF: investigation_encoded_2, FindAndOpen, Ph4nt0m 1ntrud3r
Also written up in: satoki/ctf_writeups, klassiker/ctf-writeups, B34nB01z/writeups, lightningsarp/CTF-Players
- forensics
Same technique in picoCTF: investigation_encoded_2, FindAndOpen, Ph4nt0m 1ntrud3r
Also written up in: klassiker/ctf-writeups
- forensics
Same technique in picoCTF: investigation_encoded_2, FindAndOpen, Ph4nt0m 1ntrud3r
Web3
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: satoki/ctf_writeups, klassiker/ctf-writeups, ajh11g/CTF, B34nB01z/writeups, h0ffayyy/CTF, lightningsarp/CTF-Players
- sql
Same technique in picoCTF: Irish-Name-Repo 3, Startup Company, More SQLi
Also written up in: klassiker/ctf-writeups, B34nB01z/writeups, lightningsarp/CTF-Players
- web
Same technique in picoCTF: Live Art, secure-email-service, No FA
- web
- crypto
Same technique in picoCTF: Live Art, secure-email-service, No FA
Reverse engineering3
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: klassiker/ctf-writeups, B34nB01z/writeups, holypower777/ctf_writeups, lightningsarp/CTF-Players
- reverse-engineering
Same technique in picoCTF: Checkpass, WinAntiDbg0x100, WinAntiDbg0x200
Also written up in: B34nB01z/writeups, gg0h/CTF
- reverse-engineering
- crypto
Same technique in picoCTF: Checkpass, WinAntiDbg0x100, WinAntiDbg0x200
Also written up in: satoki/ctf_writeups, holypower777/ctf_writeups
- ocr
- checksum
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.
- standard
- 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
OSINT2
Answer a question about the real world from public sources. The work is pivoting between identifiers, not exploiting anything.
Also written up in: gg0h/CTF
- osint
Same technique in picoCTF: CVE-XXXX-XXXX
- social-engineering
- osint
Same technique in picoCTF: CVE-XXXX-XXXX
Binary exploitation1
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: klassiker/ctf-writeups, holypower777/ctf_writeups
- binary-analysis
Same technique in picoCTF: lockdown-horses, Guessing Game 1, Bizz Fuzz