[Dailydave] CGC Wrapup Video

[Jordan Wiens]

For what it's worth, the CTF-as-esport dream takes more work than I have
time these days unfortunately. I'm still convinced it will happen, just not
sure who will do it. That said, visualizations like this are going to be
key to pulling it off.

A really nice interface to the raw data is available from Lunge:
http://www.lungetech.com/cgc-corpus/

The modified Qemu and API to produce execution traces for visualization
(along with yet another web interface to pick through the raw data which is
what we used during the live event to try to make sense of the chaos) from
Rusty and I is online at: https://github.com/Vector35/trace-api

And most importantly, the software to visualize the traces is open sourced
here: https://github.com/voidALPHA/cgc_viz

Generating trace-files that are capable of visualization isn't hard. At
their simplest form you just need an instruction pointer trace over an
execution. Adding on disassembly, register contents, data flow, and memory
read/writes makes for a much more useful visualization, but there's a
pretty surprising amount of value just in instruction pointer "shapes".

Bonus related links:
Raw data: https://github.com/lungetech/cgc-corpus
https://github.com/lungetech/cgc-cfe-submission-corpus
https://github.com/lungetech/cgc-cqe-submission-corpus
Trail of Bits is maintaining a patched version of the binaries and build
configurations (https://github.com/trailofbits/cb-multios/) with the goal
of being able to be built across lots of platforms. In many ways, one of
the best legacies of CGC is the very convenient and large sample corpus
with included exploits, patches, and functionality polls

On Thu, Aug 17, 2017 at 11:51 AM, dave aitel <dave at immunityinc.com> wrote:

> So I wanted to type up some notes on the CGC Wrapup
> <https://www.youtube.com/watch?v=SYYZjTx92KU> video, which was excellent.
> I mean, a part of what you want to do, while you watch it, is strip out all
> the parts of the thing that are about "playing the game". I know Jordan
> loves CTFs as some sort of e-sport and also there's a whole community who
> for whatever reason plays CTFs instead of playing corewars on helpless
> Chinese networks like of yore, but that stuff is 100% distraction when it
> comes to the CGC.
>
>
> As you can see, the tiny red lines on the right are supposed to be some
> combination of "could hack and could secure a service". I can't find
> anywhere something that has a simple spreadsheet of which samples
> <http://www.lungetech.com/cgc-corpus/challenges/NRFIN_00080/>  (and even
> which vulns in which samples) were able to be attacked by which teams. So
> much of the game was weighted towards performance characteristics that it's
> hard to determine the information you really need from the scores, although
> the video goes over some anecdotal examples where RUBEUS and MECHAPHISH
> were able to attack particular historically interesting programs. It's
> telling that Mayhem won despite being basically off for half the contest. ;)
>
> Does anyone have better data on this?
>
> -dave
>
> P.S. Holy cow the visualizations on program execution are next gen! Worth
> a close watch just to see them.
>
> _______________________________________________
> Dailydave mailing list
> Dailydave at lists.immunityinc.com
> https://lists.immunityinc.com/mailman/listinfo/dailydave
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.immunityinc.com/pipermail/dailydave/attachments/20170817/dc5b67e3/attachment-0001.html>