Andrew Davis, Patrick Hulin, Tim Leek
Enrollment: Limited: Advance sign-up required
Sign-up by 01/02
Limited to 25 participants
Attendance: Participants must attend all sessions
Prereq: None
Does it annoy you that programs have bugs in them? Bad programs! Would you like to try to correct this situation? Good you!
This IAP activity will be a several weeks long competition during which you and your team members will look for bugs in programs by running them against large amounts of randomized input. This kind of testing is called ‘fuzzing’, because the inputs you hand to the program range from slightly out-of-focus versions of normal inputs, to quite hairy unrecognizable ones. Fuzzing is a rather effective means of finding bugs, as programs are typically written under the assumption that they will encounter only mostly normal inputs.
This activity will meet Wednesdays from 1-3pm throughout IAP. Location TBD. Teams will be running their ‘fuzzing campaigns’ over the course of IAP and for the most part meetings will be largely for check-ins, strategizing, assistance, and problem solving. Think of it as fuzzing office hours.
The team that wins the Derby by finding the most bugs that impress the judges will be pronounced the winner and receive an amazing prize worth 10s of dollars!
Contact: Timothy Leek, LL-A-207F, 781 981-2975, TLEEK@LL.MIT.EDU
| Jan/11 | Wed | 01:00PM-03:00PM | BeaverWorks NE45-201 |
Introduction. Fuzzers explained (mutation, grammar based, etc). Instrumentation explained (bounds checking, crash binning, etc). Team forming. Choice of target programs. Resource Allocation.
| Jan/18 | Wed | 01:00PM-03:00PM | BeaverWorks NE45-201 |
Status report. Fuzzing office hours.
| Jan/25 | Wed | 01:00PM-03:00PM | BeaverWorks NE45-201 |
Status report. Fuzzing office hours.
| Feb/01 | Wed | 01:00PM-03:00PM | BeaverWorks NE45-201 |
Winner declared. Postmortem write-ups.