Trend Micro CTF 2017

Trend Micro CTF 2017 Online Qualifier: Format and Results

The Trend Micro CTF qualifier of June 2017 was a 24-hour online jeopardy that fed a Tokyo final. This guide covers the organizer, the format, the task types, the top of the board and what a team should expect.

Hexfield editorial

OrganizerTrend Micro
Dates24-25 Jun 2017
Format24 h online jeopardy
Teams294
Event
Trigram plot of an HTML document with a tight cluster of printable ASCII points and a few outliers from embedded scripts
Markup keeps a trigram cloud inside the printable ASCII region, and any outlier points to embedded binary or an unusual encoding.

Organizer and name

The Trend Micro CTF is run by Trend Micro, the Japanese security software company, and is known as the Raimund Genes Cup after the company’s late chief technology officer, who was well known in the European security community. The 2017 edition started with an online qualifier played on 24 and 25 June 2017, listed on CTFtime as event 475. The best teams of that round were invited to a final in Tokyo, held in the autumn.

CTFtime gives the qualifier a weight of 21 and shows 294 participating teams. A field of nearly 300 is large for a single-organizer contest, and the moderate weight tells that the strongest teams of the season were only partly present. For many mid-ranked teams the qualifier was an unusual chance to reach an international final.

Format

The qualifier is a 24-hour online jeopardy. Each task has a point value, a flag is submitted on solving it, and the table is ranked by points. A full day is a middle length: long enough to let a prepared team reach most of the board, short enough that sleep has to be planned. The online form means no travel, so teams from every continent compete in the same window, and the contest therefore starts at different local times for different teams.

The categories follow the security-industry flavor of the organizer. Tasks challenged teams to find flaws in applications, crack ciphers, gather information about fictional individuals and analyze network traffic. That is a recognizable mix: web and binary application bugs, cryptanalysis, open-source intelligence and packet capture forensics.

Task styles in this kind of contest

Application tasks supply either a binary or a reachable service. The usual flaws are memory-corruption bugs in a native program, logic errors in a web application and unsafe deserialization. Cipher tasks tend to give a ciphertext together with a hint about the algorithm, and the flaw lies in the way it is used: a reused key stream, a short key, a mode of operation applied wrongly. Open-source intelligence tasks give a persona and ask players to follow public traces, such as profiles, images with metadata or domain records, to a hidden answer; these tasks are scored on persistence and organization more than on technical depth.

Network traffic analysis is where raw data skills pay off. A capture file contains many streams, and the interesting one is often a transfer of a file in pieces, a base64 blob in an HTTP header or an encrypted channel with a weak key. Telling compressed data from encrypted data by looking at it is a skill with a direct payoff here, and the compression versus encryption guide explains how the byte histogram separates the two. For a general introduction to the view types, the binary visualization overview is the place to start.

The published top of the board

CyKOR took first place with 4,713 points. The team 217 followed with 4,604, PwnThyBytes had 4,010, and LC↯BC had 3,900. The team in fifth place scored 3,804, and BrentKawaii followed with 3,500.

The table splits into three layers. The top two are within 109 points of each other, the next two are a few hundred points behind, and then comes a gradual decline. Fifth place is only 96 points behind fourth, a margin below the value of a single typical task, so the position that decided the qualification for the final was settled by one small task or by timing. That is common in a contest where the number of finalists is fixed: the border between inside and outside is sharp, even though the points are close.

What it is like for a new team

For a team playing a 24-hour contest for the first time, the main risk is energy. A practical rule is to plan sleep in two-person shifts, so the board is never unattended, and to stop adding new tasks in the last three hours in favor of finishing those already started. Spend the first hour reading every task and recording its category, point value and number of solves, because the solve count shows which tasks are realistic.

OSINT tasks are the ones that often get neglected, but they pay well in a field of this size because strong teams do not always prioritize them. Keep a template of the places to search and a clean browser profile.

It also helps to know what comes after: teams that qualified for the final had to prepare for attack-defense, which requires a different toolkit, as described in the guide to the CTFZone qualifier, where the same transition applied. More background on how teams plan a season is on the team page, and related notes are collected on the blog.

Where the event went later

The Trend Micro CTF has returned in later years under the same sponsor, with an online qualifier followed by a final in Tokyo. The contest has been held as a recruiting and community occasion for the company, and each edition has its own CTFtime page listing the date, number of teams and standings.

Questions readers ask

What is the Raimund Genes Cup?

It is the name of the Trend Micro CTF, held in memory of Raimund Genes, the company's long-time chief technology officer. The 2017 contest started with an online qualifier on 24 and 25 June, and the top teams went on to a final in Tokyo in the autumn.

How many teams took part and how heavy was the event?

CTFtime lists 294 teams for the qualifier and a weight of 21. The size of the field is large, but the weight shows that few of the very top teams of the year were on the board, so the contest was open to strong regional teams.

What happens after the qualifier?

The best teams were invited to an on-site final in Tokyo, played in an attack-defense format. That means every team gets a server with services, patches its own copy and attacks those of the others. It is a different skill set from the jeopardy qualifier.

New to capture the flag? Formats, teams and a first-month plan in one place.

Read the CTF guide