Skip to content
ctfpal
Every CTF
2014no writeups on CTFtime

31C3 CTF

36 challenges with 41 published solutions between them. CTFtime lists this event but has no writeups filed against it, so it is absent from the index CTFtime feeds. These were found in public repositories instead. Each link is pinned to the commit it was read from.

The event on CTFtime

Binary exploitation13

Turn a memory-safety bug in a native binary into control of execution. Usually a stack overflow, a format string, or a heap primitive.

Solve it with:ROP gadget finderShellcode assembler and libraryCyclic pattern generator and offset finderFormat string exploit builderLearn: Binary exploitation

Uncategorised7

The upstream scoreboard did not say, so neither do we.

Solve it with:Cipher identifier and automatic decoderLearn: Recognising encodings

Reverse engineering7

Work out what a compiled program does without its source, then work backwards from the check to the input that passes it.

Solve it with:Strings extractor for binaries and blobsWebAssembly disassemblerJava .class disassemblerPython .pyc bytecode disassemblerLearn: Binary exploitation

Web5

Reach data or functionality the application meant to keep from you - through its inputs, its tokens, or its trust in the client.

Solve it with:JWT decoder and signature verifierJWT alg=none bypass generatorWeb attack payload catalogJWT secret brute forceLearn: Web attacks and session tokens

Cryptography4

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.

Solve it with:Cipher identifier and automatic decoderVigenere cipher solver with automatic key recoveryRSA decryption and attack runnerWiener’s attack on small RSA private exponentsIn-browser hash cracker with rule transformsLearn: Classical ciphers and frequency analysisLearn: RSA and the parameters that break it

Other 2014 events