Skip to content
Files for the "v9" challenge of 34C3 CTF. See the greeting message in server.go for more information about the challenge
JavaScript Go Dockerfile Other
Branch: master
Clone or download
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Type Name Latest commit message Commit time
Failed to load latest commit information.
dockerimage Initial commit Dec 30, 2017
exploit Initial commit Dec 30, 2017
.gitattributes Initial commit Dec 30, 2017
README.txt Initial commit Dec 30, 2017
server.go Initial commit Dec 30, 2017
v9.patch Initial commit Dec 30, 2017



The patch should apply cleanly to the latest (as of 12/26/2017 -- see release version of Chromium (63.0.3239.108) and v8 ( The v9_7.0.patch should apply cleanly to v8 version

To obtain a local copy of the v8 source code do the following:

    mkdir v9 && cd v9
    fetch v8 && cd v8           # see
    git checkout
    gclient sync
    patch -p1 < /path/to/v9.patch
    ./tools/dev/ x64.debug
    ninja -C

You can also build Chromium from souce, although it should not be required to solve the challenge. Use git tag 63.0.3239.108 for that and see

I used the following file:

    is_debug = false
    symbol_level = 2

The chrome binary in the release package has been stripped. However, you can download the fully symbolized (5.2GB) binary from

The dockerimage/ directory contains everything you need to reproduce the container setup that is used by the challenge server. The server will start chromium like this: `chromium-browser --headless --disable-gpu --no-sandbox --virtual-time-budget=60000 $URL`. The container is given 2 cores and 8GB of RAM.
You can’t perform that action at this time.