LA CTF 2023
52 challenges with 191 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. 24 of them also carry the solution LA CTF 2023’s own organisers published, which is linked on the challenge itself.
Full task list on CTFtimeMisc12
Everything that fits no other box: esolangs, puzzles, scripting exercises, and the jail escapes that have not yet earned their own category.
Published by the organisers in uclaacm/lactf-archive: solve/README.md, solve/solution.sh, solve/Solution.sol
Also written up in: MeilingLiu1997/CTF-Writeups, m1dm4n/CTF-WriteUp, m1dm4n/CTF-WriteUp, MeilingLiu1997/CTF-Writeups, MeilingLiu1997/CTF-Writeups
- blockchain
- evm
Same technique in picoCTF: Reentrance, Smart_Overflow, Access_Control
Published by the organisers in uclaacm/lactf-archive: solve.py
Also written up in: qhdwight/ctf-writeups, MeilingLiu1997/CTF-Writeups, vital-information-resource-under-siege/PWN-Challenges
- cpp
Same technique in picoCTF: PW Crack 2, Permissions, Specialer
Also written up in: siunam321/CTF-Writeups, solocshaw/yet-another-ctf-writeups
- misc
Same technique in picoCTF: PW Crack 2, Permissions, Specialer
Also written up in: siunam321/CTF-Writeups, solocshaw/yet-another-ctf-writeups
- misc
Same technique in picoCTF: PW Crack 2, Permissions, Specialer
Also written up in: daffainfo/ctf-writeup
- misc
Same technique in picoCTF: PW Crack 2, Permissions, Specialer
Published by the organisers in uclaacm/lactf-archive: solve.sage
Also written up in: 5t0n3/ctf-writeups, MeilingLiu1997/CTF-Writeups
Same technique in picoCTF: PW Crack 2, Permissions, Specialer
Also written up in: sambrow/ctf-writeups, lu513n.com
Same technique in picoCTF: PW Crack 2, Permissions, Specialer
Decrypt
2 official solutionsAlso written up in: daffainfo/ctf-writeup, 5t0n3/ctf-writeups
Published by the organisers in uclaacm/lactf-archive: solve/solution.sh
Also written up in: MeilingLiu1997/CTF-Writeups
discord
1 writeupSame technique in picoCTF: PW Crack 2, Permissions, Specialer
Published by the organisers in uclaacm/lactf-archive: src/README.md
Private Bin
1 official solutionAlso written up in: 5t0n3/ctf-writeups
Cryptography10
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 uclaacm/lactf-archive: solve.py
Also written up in: LeonGurin/My-CTF-Writeups, kalyancheerla/writeups, 5t0n3/ctf-writeups, LeonGurin/My-CTF-Writeups, MeilingLiu1997/CTF-Writeups
- crypto
Same technique in picoCTF: It's Not My Fault 2, StegoRSA, AES-ABC
Published by the organisers in uclaacm/lactf-archive: solve.py
Also written up in: LeonGurin/My-CTF-Writeups, kalyancheerla/writeups, 5t0n3/ctf-writeups, MeilingLiu1997/CTF-Writeups
- crypto
Same technique in picoCTF: It's Not My Fault 2, StegoRSA, AES-ABC
Also written up in: daffainfo/ctf-writeup, LeonGurin/My-CTF-Writeups, solocshaw/yet-another-ctf-writeups, LeonGurin/My-CTF-Writeups
- crypto
Same technique in picoCTF: It's Not My Fault 2, StegoRSA, AES-ABC
Also written up in: daffainfo/ctf-writeup, LeonGurin/My-CTF-Writeups, kalyancheerla/writeups, solocshaw/yet-another-ctf-writeups
- crypto
Same technique in picoCTF: It's Not My Fault 2, StegoRSA, AES-ABC
Published by the organisers in uclaacm/lactf-archive: solve.py
Also written up in: kalyancheerla/writeups, 5t0n3/ctf-writeups, MeilingLiu1997/CTF-Writeups
- crypto
Same technique in picoCTF: It's Not My Fault 2, StegoRSA, AES-ABC
Published by the organisers in uclaacm/lactf-archive: README.md, solve.sage
Also written up in: 5t0n3/ctf-writeups, MeilingLiu1997/CTF-Writeups, MeilingLiu1997/CTF-Writeups
Published by the organisers in uclaacm/lactf-archive: solve.py
Also written up in: 5t0n3/ctf-writeups, solocshaw/yet-another-ctf-writeups, MeilingLiu1997/CTF-Writeups
Also written up in: KernelKrise/CTF
- math
- reverse
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
Hard Rock
1 official solutionAlso written up in: 5t0n3/ctf-writeups
Web10
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 uclaacm/lactf-archive: solve.py
Also written up in: daffainfo/ctf-writeup, siunam321/CTF-Writeups, MeilingLiu1997/CTF-Writeups
- web
- scm
- mercurial
Same technique in picoCTF: Live Art, secure-email-service, No FA
Also written up in: daffainfo/ctf-writeup, siunam321/CTF-Writeups, LeonGurin/My-CTF-Writeups
- web
Same technique in picoCTF: Live Art, secure-email-service, No FA
Also written up in: siunam321/CTF-Writeups, r2dev2/CTF
- web
- csrf
- xss
Same technique in picoCTF: Live Art, secure-email-service, msfroggenerator2
Published by the organisers in uclaacm/lactf-archive: solve.py
Also written up in: siunam321/CTF-Writeups, MeilingLiu1997/CTF-Writeups, lu513n.com
- web
- uuid
Same technique in picoCTF: Live Art, secure-email-service, No FA
Published by the organisers in uclaacm/lactf-archive: solve.py
Also written up in: 5t0n3/ctf-writeups, omerAF/CTFs, MeilingLiu1997/CTF-Writeups, omerAF/CTFs
- web
- crypto
Same technique in picoCTF: Live Art, secure-email-service, No FA
Also written up in: siunam321/CTF-Writeups, sambrow/ctf-writeups, r2dev2/CTF
- web
- csp
- xss
Same technique in picoCTF: Live Art, secure-email-service, msfroggenerator2
Published by the organisers in uclaacm/lactf-archive: solve.py
Also written up in: sambrow/ctf-writeups, MeilingLiu1997/CTF-Writeups, lu513n.com
Published by the organisers in uclaacm/lactf-archive: solve.py
Also written up in: r2dev2/CTF, MeilingLiu1997/CTF-Writeups
Forge
1 official solutionAlso written up in: 5t0n3/ctf-writeups
- web
Same technique in picoCTF: Live Art, secure-email-service, No FA
Binary exploitation8
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 uclaacm/lactf-archive: solve.py
Also written up in: asdiml/ctf-public, asdiml/ctf-public, KernelKrise/CTF, MeilingLiu1997/CTF-Writeups, vital-information-resource-under-siege/PWN-Challenges
- pwn
Same technique in picoCTF: lockdown-horses, Guessing Game 1, Bizz Fuzz
Published by the organisers in uclaacm/lactf-archive: solve.py
Also written up in: qhdwight/ctf-writeups, UnoArroefy/CTF-Writeups, MeilingLiu1997/CTF-Writeups
- format-strings
- pwn
- stack_overflow
Same technique in picoCTF: PIE TIME 2, Binary Gauntlet 2, Binary Gauntlet 3
Published by the organisers in uclaacm/lactf-archive: solve/solution.sh, solve/Solution.sol
Also written up in: m1dm4n/CTF-WriteUp, MeilingLiu1997/CTF-Writeups, MeilingLiu1997/CTF-Writeups
Published by the organisers in uclaacm/lactf-archive: solve.py
Also written up in: qhdwight/ctf-writeups, MeilingLiu1997/CTF-Writeups, vital-information-resource-under-siege/PWN-Challenges
- format-strings
- pwn
Same technique in picoCTF: PIE TIME 2, Binary Gauntlet 2, Binary Gauntlet 3
Also written up in: siunam321/CTF-Writeups, kalyancheerla/writeups
- pwn
Same technique in picoCTF: lockdown-horses, Guessing Game 1, Bizz Fuzz
Published by the organisers in uclaacm/lactf-archive: solve.py, solve/src/lib.rs
Also written up in: MeilingLiu1997/CTF-Writeups, MeilingLiu1997/CTF-Writeups
Working.Exploit
4 official solutionsAlso written up in: nobodyisnobody/write-ups, nobodyisnobody/write-ups, nobodyisnobody/write-ups, nobodyisnobody/write-ups
Published by the organisers in uclaacm/lactf-archive: solve.py
Also written up in: MeilingLiu1997/CTF-Writeups
- rop
- pwn
Same technique in picoCTF: lockdown-horses, Guessing Game 1, vr-school
Reverse engineering7
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: siunam321/CTF-Writeups, siunam321/CTF-Writeups, LeonGurin/My-CTF-Writeups, LeonGurin/My-CTF-Writeups, Magnus1990P/writeups, solocshaw/yet-another-ctf-writeups, solocshaw/yet-another-ctf-writeups, KernelKrise/CTF
- rev
Same technique in picoCTF: Checkpass, WinAntiDbg0x100, WinAntiDbg0x200
Also written up in: asdiml/ctf-public, KernelKrise/CTF
- reverse
- engineering
Same technique in picoCTF: Checkpass, WinAntiDbg0x100, WinAntiDbg0x200
Also written up in: siunam321/CTF-Writeups, LeonGurin/My-CTF-Writeups
- rev
Same technique in picoCTF: Checkpass, WinAntiDbg0x100, WinAntiDbg0x200
Published by the organisers in uclaacm/lactf-archive: solve.py
Also written up in: MeilingLiu1997/CTF-Writeups, sekai.team
Also written up in: KernelKrise/CTF
- rev
- reverse
Same technique in picoCTF: Checkpass, WinAntiDbg0x100, WinAntiDbg0x200
Also written up in: kalyancheerla/writeups, KernelKrise/CTF
- rev
Same technique in picoCTF: Checkpass, WinAntiDbg0x100, WinAntiDbg0x200
Published by the organisers in uclaacm/lactf-archive: solve/src/main.rs
Also written up in: MeilingLiu1997/CTF-Writeups
Uncategorised4
The upstream scoreboard did not say, so neither do we.
Finals Simulator Text
1 official solutionAlso written up in: PointerPioneers/CTFs
Hidden In The Plain Sheets
1 official solutionAlso written up in: kalyancheerla/writeups
Also written up in: Magnus1990P/writeups
Pycjail
1 official solutionAlso written up in: sekai.team
OSINT1
Answer a question about the real world from public sources. The work is pivoting between identifiers, not exploiting anything.
Published by the organisers in uclaacm/lactf-archive: Solution.md
Also written up in: daffainfo/ctf-writeup, MeilingLiu1997/CTF-Writeups, solocshaw/yet-another-ctf-writeups
- osint
- misc
Same technique in picoCTF: CVE-XXXX-XXXX