Upgrade to Pro
— share decks privately, control downloads, hide ads and more …
Speaker Deck
Features
Speaker Deck
PRO
Sign in
Sign up for free
Search
Search
What I've Learned Writing CTF Challenges
Search
vito
February 11, 2017
Programming
0
150
What I've Learned Writing CTF Challenges
BSides Tampa, 2/11/2017
vito
February 11, 2017
Tweet
Share
More Decks by vito
See All by vito
Modernizing SQL Injection CTF Challenges
vito
0
120
Raw Water: Quenching Your Thirst for SQL Injection
vito
0
71
Lessons Learned from Five Years of Building Capture the Flag
vito
0
490
Capture the Flag: An Owner's Manual
vito
0
90
Building DEF CON CTF with Ruby
vito
0
600
Other Decks in Programming
See All in Programming
来たるべき 8.0 に備えて React 19 新機能と React Router 固有機能の取捨選択とすり合わせを考える
oukayuka
2
840
「ElixirでIoT!!」のこれまでとこれから
takasehideki
0
370
第9回 情シス転職ミートアップ 株式会社IVRy(アイブリー)の紹介
ivry_presentationmaterials
1
230
PHP 8.4の新機能「プロパティフック」から学ぶオブジェクト指向設計とリスコフの置換原則
kentaroutakeda
2
470
Claude Codeの使い方
ttnyt8701
1
130
データの民主化を支える、透明性のあるデータ利活用への挑戦 2025-06-25 Database Engineering Meetup#7
y_ken
0
310
技術同人誌をMCP Serverにしてみた
74th
0
270
VS Code Update for GitHub Copilot
74th
1
300
Team topologies and the microservice architecture: a synergistic relationship
cer
PRO
0
1k
Result型で“失敗”を型にするPHPコードの書き方
kajitack
4
260
Enterprise Web App. Development (2): Version Control Tool Training Ver. 5.1
knakagawa
1
120
ruby.wasmで多人数リアルタイム通信ゲームを作ろう
lnit
2
230
Featured
See All Featured
The Success of Rails: Ensuring Growth for the Next 100 Years
eileencodes
45
7.4k
Statistics for Hackers
jakevdp
799
220k
RailsConf & Balkan Ruby 2019: The Past, Present, and Future of Rails at GitHub
eileencodes
138
34k
Imperfection Machines: The Place of Print at Facebook
scottboms
267
13k
Producing Creativity
orderedlist
PRO
346
40k
Improving Core Web Vitals using Speculation Rules API
sergeychernyshev
16
940
The Illustrated Children's Guide to Kubernetes
chrisshort
48
50k
Connecting the Dots Between Site Speed, User Experience & Your Business [WebExpo 2025]
tammyeverts
5
210
VelocityConf: Rendering Performance Case Studies
addyosmani
330
24k
Visualizing Your Data: Incorporating Mongo into Loggly Infrastructure
mongodb
46
9.6k
GitHub's CSS Performance
jonrohan
1031
460k
Side Projects
sachag
455
42k
Transcript
What I’ve Learned Writing CTF Challenges Vito Genovese BSides Tampa
February 11, 2017
What is CTF?
What is CTF?
Jeopardy Style
Attack-Defense
None
None
None
None
None
None
None
None
None
None
None
None
None
None
None
CGC Jargon • Cyber Reasoning System • Proof of Vulnerability
• Replacement Binary • Challenge Binary
BSTies http://bsties.notmalware.ru
CTF Challenges Teams attack it
CTF Challenges Protects something of in-game value
CTF Challenges Ideally: known solvable
CTF Challenges Also ideally: appropriately tricky
None
None
Solving 'em • Correct side of an if statement •
Cracking a code • Using SQL injection to trick a database • Stealing the garbage file from the Gibson
Actually Building One
None
Original Goal
Original Goal
• Given same STDIN • Same STDOUT • Same clock
cycles • Same syscalls
https://xkcd.com/1319/
Why Automate?
None
Thousand Cuts
Thousand Cuts
Thousand Cuts
Actually Building It
Start the First One 1. Set up CGC service-template 2.
Test not-crashing 3. Make binary that doesn’t crash 4. Test crashing 5. Make binary that crashes
First One's Done • Ruby script to spit out 334
binaries • Vary buffer sizes • Vary stack cookie • Python script running game flow
First Set's Done Figure out how to make second and
third sets
Second Set Python script to add stuff to source code
Third Set Python script to rearrange source code
All Sets Done Test the difficulty
Integration Testing With Gyno • Finds a bug in like
30s • Fixing the bug took 30m • (fixing the bug a week prior would've taken 5m)
More Integration Testing kind of weird
easy-prasky • single binary • Baby’s First category • Separate
CRS work from first stab at CGCEF • Hacked to be first in 334 cuts
Deployment • Determine ops requirements • CGC kernel • Python
installed • Open port
Deployment Puppetize it!
Deployment
Running it just kinda worked (once teams Got It)
CTF Challenge Process 1.Idea 2.Build 3.Test
CTF Challenge Framework • Configuration • Build • Testing •
Deployment
CTF Challenge Framework CGC service-template
CTF Challenge Deployment put it on a server lol
It's Just Software
Software Goals Useful Usable Reliable
Useful for Competition Separate teams that solve it from teams
that don't Prefer strong correlation with finals ranking
Useful for Education Teach new players something Get players over
a hang-up
Usable Intended difficulty only Minimize corner cases Unintended vulnerabilities?
Reliable Remain vulnerable
Reliability is Hard Players like to attack Players like to
brute Players like to complain
Reliability is Hard
Reliability is Demanding
Reliability is Expensive If you want it to be
Reliability is Cheap Build software that can be run reliably
Twelve Factor App • VIII. Concurrency • Scale out via
the process model • IX. Disposability • Maximize robustness with fast startup and graceful shutdown
Twelve Factor Challenges • Limit global state • Process per
connection • xinetd ftw • Make adding resources cheap
Adding Resources Automate!
Operations Automation Puppet or Chef for server provisioning
Operations Automation Docker is slow to spin up RunC is
fast
Shared State • Process per connection not always feasible •
Sandwich challenges in 2014 • JRuby & Celluloid slow to start • State still per connection
Shared State • Global state and web challenges • Persisted
XSS • Tricking a global database
Waiting For Your Touch • 2015 web challenge • /r/thebutton
knockoff • JRuby, Rails, websockets, postgres
Waiting For Your Touch
Waiting For The Challenge Slow when not slow 500s Thankfully
during the day
Waiting For Your Touch 1. Took it down 2. Opened
replacement challenge 3. Debugged for an hour
Debugging For Your Touch 4. Leaked and exhausted postgres connections
5. Fixed leak 6. Allocated more connections
Waiting For My Fix 7. Took an hour 8. Gyno
forced a fifteen minute cool-down between "is it fixed" and "it is fixed" 9. Reopened
Most Important Part People are the most important
Respect People • Respect for yourself • Respect for your
team • Respect for players
Respect for Yourself
Respect for Your Team
Respect for Your Team
Respect for Your team Make services easy to keep running
Document!
Respect for Your Team Provide easy to run smoke tests
"Is this exploitable?" should be a one-liner that spits out the flag
Respect for Players
Respect for Players
Respect for Players
Respect for Players
Building Challenges is Software Development Useful Usable Reliable
Reliability Imposes Constraints Limit state Limit dependencies Automate
Respect Is Fundamental Self Team Players
Thanks! Vito Genovese
[email protected]
@vito_lbs GPG B07D616143CAA77B https://legitbs.net @legitbs_ctf