3 ########################
4 Security Contest Archive
5 ########################
12 The Native Client team at Google has gone to exceptional measures to
13 make Native Client a secure system, including holding a public
14 security contest. This page archives information from that contest,
15 including the list of contest winners and the lineup of security
16 experts who served as judges.
18 Although the security contest has ended, the Native Client team
19 welcomes your continued involvement in the project. You can help by
20 submitting bugs and participating in the Native Client discussion
26 The Native Client team held a contest in 2009 to test the security of
27 Native Client and help make the system more secure. Participants were
28 invited to discover security bugs in Native Client technology in order
29 to compete for cash prizes.
31 Here was the challenge put forth by the Native Client team:
33 Do you think it is impossible to safely run untrusted x86 code on
34 the web? Do you want a chance to impress a panel of some of the top
35 security experts in the world? Then submit an exploit to the Native
36 Client Security contest and you could also win cash prizes, not to
37 mention bragging rights.
39 The contest judges evaluated exploits designed to defeat Native Client
40 security measures based on severity, scope, reliability, and
41 style. The winning teams and entries are listed below.
48 The Native Client team thanks everyone who participated in the contest
49 for their contributions to improving the quality and security of the
50 Native Client system. The judges reviewed the submitted exploits and
51 identified the following teams as winners:
55 * - .. image:: /images/medal-64_1st.png
56 :alt: First place medal
58 - **Team**: Beached As
60 **Members**: Mark Dowd, Ben Hawkes
62 **Submitted issues**: 50, 51, 52, 53, 55, 56, 57, 58, 59, 60, 62, 63
64 Mark Dowd and Ben Hawkes are application security specialists
65 hailing from Australia and New Zealand, respectively. Mark
66 works for IBM ISS X-Force R&D, whereas Ben currently performs
67 independent research while simultaneously pursuing a
68 mathematics and computing science degree. Both have uncovered
69 major security flaws in ubiquitous Internet software, in terms
70 of both exploitable bugs and weaknesses in system protection
71 mechanisms. Both have spoken at numerous security conferences
72 in recent years, including BlackHat, Ruxcon, KiwiCon, and
75 * - .. image:: /images/medal-64_2nd.png
76 :alt: Second place medal
80 **Members**: Jason Carpenter, Eric Monti, Chris Rohlf
82 **Submitted issues**: 42, 44, 49, 70
84 Team CJETM is comprised of security vulnerability researchers
85 Chris Rohlf, Jason Carpenter and Eric Monti. All three have
86 abused software professionally for a long time.
88 * - .. image:: /images/medal-64_3rd.png
89 :alt: Third place medal
93 **Members**: Gabriel Campana
95 **Submitted issues**: 45
97 Gabriel Campana is a security researcher working at Sogeti ESEC
98 R&D labs. His research interests are mainly focused on
99 vulnerability research, exploitation methods, and Linux kernel
100 security. Lately he has been working on automated vulnerability
101 research, especially fuzzing. In his spare time, he plays with
102 embedded network devices.
104 * - .. image:: /images/medal-64_4th.png
105 :alt: Fourth place medal
111 **Members**: Daiki Fukumori
113 **Submitted issues**: 66, 67
115 Daiki Fukumori is a web security researcher. He has given talks
116 at POC Korea and AVTokyo on Web 2.0 Hacking, and he introduced
117 Native Client security at Shibuya.pm. He currently has an
118 interest in cloud security.
120 * - .. image:: /images/medal-64_4th.png
121 :alt: Fourth place medal
127 **Members**: Alex Radocea
129 **Submitted issues**: 81
131 Alex Radocea is a 20-year old student at Rensselaer Polytechnic
132 Institute. In the realm of computer security he is really
133 excited about proactively designed technology which can help
134 wipe out entire bug classes. Currently he is helping improve
135 Native Client through Google Summer of Code.
142 Google recruited the following group of distinguished security experts
143 to serve as judges for the Native Client security contest:
148 +----------------------------------------+
150 +----------------------------------------+
151 | Princeton University |
152 +----------------------------------------+
153 | http://www.cs.princeton.edu/~felten/ |
154 +----------------------------------------+
165 * - University of Michigan
169 * - http://www.cse.umich.edu/~jhalderm/
170 - http://www.citi.umich.edu/u/provos/
171 - http://www.bennetyee.org/
177 * - University of College London
178 - University of California San Diego
181 * - http://www.cs.ucl.ac.uk/staff/B.Karp/
182 - http://www.cs.ucsd.edu/~savage
183 - http://people.csail.mit.edu/nickolai/
191 * - Harvard University
197 * - http://www.eecs.harvard.edu/~greg/
198 - http://www.cs.rice.edu/~dwallach/
204 Additional information
205 ======================
207 For additional information about the Native Client security contest,
209 :doc:`Contest Announcement <contest-announcement>`,
210 :doc:`FAQ <contest-faq>` and
211 :doc:`Terms & Conditions <contest-terms>`.
213 If you'd like to get involved with Native Client, you can:
215 * Use the `Native Client SDK </native-client/sdk/download>`_ to build Native
216 Client web applications.
217 * Submit `bugs <http://code.google.com/p/nativeclient/issues/list>`_
218 and participate in the Native Client
219 `discussion group <http://groups.google.com/group/native-client-discuss>`_.
221 `Native Client open-source project <http://code.google.com/p/nativeclient/>`_.