L3akCTF 2025
11 challenges with 12 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 CTFtimeWeb4
Reach data or functionality the application meant to keep from you - through its inputs, its tokens, or its trust in the client.
- web
Same technique in picoCTF: Client-side-again, dont-use-client-side, Irish-Name-Repo 3
- web
Same technique in picoCTF: Client-side-again, dont-use-client-side, Irish-Name-Repo 3
- web
Same technique in picoCTF: Client-side-again, dont-use-client-side, Irish-Name-Repo 3
- web
Same technique in picoCTF: Client-side-again, dont-use-client-side, Irish-Name-Repo 3
Cryptography3
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-rsa
- crypto
Same technique in picoCTF: StegoRSA, john_pollard, rsa_oracle
- crypto
- lattice
Same technique in picoCTF: MSS_ADVANCE Revenge, Not TRUe, StegoRSA
- crypto
Same technique in picoCTF: StegoRSA, Timestamped Secrets, AES-ABC
Misc3
Everything that fits no other box: esolangs, puzzles, scripting exercises, and the jail escapes that have not yet earned their own category.
Same technique in picoCTF: Permissions, Specialer, Codebook
Same technique in picoCTF: Permissions, Specialer, Codebook
Same technique in picoCTF: Permissions, Specialer, Codebook
OSINT1
Answer a question about the real world from public sources. The work is pivoting between identifiers, not exploiting anything.
Same technique in picoCTF: Permissions, Specialer, Codebook