BSidesSF 2020 CTF
40 challenges with 54 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. 32 of them also carry the solution BSidesSF 2020 CTF’s own organisers published, which is linked on the challenge itself.
Full task list on CTFtimeUncategorised18
The upstream scoreboard did not say, so neither do we.
Published by the organisers in BSidesSF/ctf-2020-release: solution/solution.txt, solution/bternary_to_file_pn.go, solution/bternary_to_file.go, solution/decode_stereo_diff.pl, solution/encode_mono_to_sterio.pl, solution/encode.pl, solution/file_to_bternary.go, solution/file_to_trinary.go
Published by the organisers in BSidesSF/ctf-2020-release: solution/solution.txt, solution/lcg_break.pl
Also written up in: datajerk/ctf-write-ups, datajerk/ctf-write-ups
Published by the organisers in BSidesSF/ctf-2020-release: solution/solution.txt
Also written up in: datajerk/ctf-write-ups, datajerk/ctf-write-ups
Published by the organisers in BSidesSF/ctf-2020-release: solution/solution.py
Published by the organisers in BSidesSF/ctf-2020-release: solution/README.md
Published by the organisers in BSidesSF/ctf-2020-release: solution/README.md
Published by the organisers in BSidesSF/ctf-2020-release: solution/solve.go
Published by the organisers in BSidesSF/ctf-2020-release: solution/solution.py
Published by the organisers in BSidesSF/ctf-2020-release: solution/solution.txt
Published by the organisers in BSidesSF/ctf-2020-release: solution/solution.py
Published by the organisers in BSidesSF/ctf-2020-release: solution/solution.txt
Published by the organisers in BSidesSF/ctf-2020-release: solution/solution.py
Published by the organisers in BSidesSF/ctf-2020-release: solution/README.md
Published by the organisers in BSidesSF/ctf-2020-release: solution/README.md
Published by the organisers in BSidesSF/ctf-2020-release: solution/README.md
Toast
1 official solutionAlso written up in: TFNS/writeups
ToastDynamicFlag
1 official solutionAlso written up in: TFNS/writeups
Published by the organisers in BSidesSF/ctf-2020-release: solution/solution.md
Web9
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 BSidesSF/ctf-2020-release: solution/solution.py
- csp-bypass
- web
- csp
Same technique in picoCTF: Live Art, secure-email-service, No FA
Published by the organisers in BSidesSF/ctf-2020-release: solution/solution.py
- csp-bypass
- web
- csp
Same technique in picoCTF: Live Art, secure-email-service, No FA
Published by the organisers in BSidesSF/ctf-2020-release: solution/README.md
- web
- websocket
Same technique in picoCTF: Live Art, secure-email-service, No FA
Published by the organisers in BSidesSF/ctf-2020-release: solution/readme.md
- web
Same technique in picoCTF: Live Art, secure-email-service, No FA
Published by the organisers in BSidesSF/ctf-2020-release: solution/payload.js, solution/solution.py
- csp-bypass
- web
- csp
Same technique in picoCTF: Live Art, secure-email-service, No FA
- cssinjection
- web
Same technique in picoCTF: Live Art, secure-email-service, No FA
- 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 BSidesSF/ctf-2020-release: solution/README.md
- web
Same technique in picoCTF: Live Art, secure-email-service, No FA
Cryptography5
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 BSidesSF/ctf-2020-release: solution/solution.txt, solution/rc4_state_to_key.pl, solution/shellcode.asm
Also written up in: TFNS/writeups
- crypto
- pwnable
Same technique in picoCTF: It's Not My Fault 2, StegoRSA, AES-ABC
Also written up in: TFNS/writeups, datajerk/ctf-write-ups, datajerk/ctf-write-ups
- crypto
Same technique in picoCTF: It's Not My Fault 2, StegoRSA, AES-ABC
Published by the organisers in BSidesSF/ctf-2020-release: solution/cracker.py
Also written up in: TFNS/writeups
- crypto
- reversing
- forensics
Same technique in picoCTF: It's Not My Fault 2, StegoRSA, AES-ABC
Also written up in: datajerk/ctf-write-ups
Same technique in picoCTF: It's Not My Fault 2, StegoRSA, AES-ABC
Published by the organisers in BSidesSF/ctf-2020-release: solution/solution.py
- engineering
- crypto
- reverse
Same technique in picoCTF: It's Not My Fault 2, StegoRSA, AES-ABC
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 BSidesSF/ctf-2020-release: solution/README.md, solution/keys-for-today.txt, solution/pstdint.h, solution/solve.cpp, solution/solve.rb
- rev
- mersenne
Same technique in picoCTF: Checkpass, WinAntiDbg0x100, WinAntiDbg0x200
Published by the organisers in BSidesSF/ctf-2020-release: solution/README.md
Also written up in: TFNS/writeups
- reversing
Same technique in picoCTF: Checkpass, WinAntiDbg0x100, WinAntiDbg0x200
Published by the organisers in BSidesSF/ctf-2020-release: solution/README.md
- reversing
- mobile
Same technique in picoCTF: Checkpass, WinAntiDbg0x100, WinAntiDbg0x200
Published by the organisers in BSidesSF/ctf-2020-release: solution/README.md
- reversing
- mobile
Same technique in picoCTF: Checkpass, WinAntiDbg0x100, WinAntiDbg0x200
Published by the organisers in BSidesSF/ctf-2020-release: solution/README.md
- reversing
- mobile
Same technique in picoCTF: Checkpass, WinAntiDbg0x100, WinAntiDbg0x200
Forensics3
Recover something from a file, a capture, or a disk image - often from a part of it the format says is unused.
Published by the organisers in BSidesSF/ctf-2020-release: solution/solve.rb
Also written up in: TFNS/writeups
- forensics
Same technique in picoCTF: investigation_encoded_2, FindAndOpen, Ph4nt0m 1ntrud3r
Published by the organisers in BSidesSF/ctf-2020-release: solution/solution.txt
Also written up in: TFNS/writeups
- forensics
Same technique in picoCTF: investigation_encoded_2, FindAndOpen, Ph4nt0m 1ntrud3r
Also written up in: TFNS/writeups
- forensics
Same technique in picoCTF: investigation_encoded_2, FindAndOpen, Ph4nt0m 1ntrud3r