Our next bug-finding rode0 will kick off in just under 30 minutes! To get started and prove how many bugs you can find, visit rode0day.mit.edu
After a longer-than-expected hiatus for a server migration Rode0day is back! Our February competition will start as scheduled tomorrow with some new buggy programs, made just for your enjoyment. Good luck, bug-finders!
Rode0Day retweeted
We (@moyix, @DynaWhat, and Tim Leek) wrote an article for @securityprivacy on "The @Rode0day to Less-Buggy Programs." Check it out here - ieeexplore.ieee.org/document…
We just pushed an update to the info.yaml file for October's bug-finding competition fixing incorrect paths to the jpegS4 and jqB3 challenges. Be sure to download the updated version of the corpus if you're competing!
Rode0Day retweeted
Brendan @moyix just talked about Rode0day #fuzzing competition @shonanmtg. The challenge set includes many interesting targets and i think it could be a good benchmark for fuzzing evaluation.
During the 19.07 Rode0day, @DynaWhat rediscovered CVE-2019-8905 as a part of his 1.9 billion executions of file with AFL!
In the 19.07 Rode0day we tried something a bit different. Instead of only injecting bugs that we had answers to, we injected trivial bugs in functions we were unable to get coverage of. Using the inputs teams sent us, we can now inject bugs into new parts of these targets!
Our latest bug-finding rode0 has begun! Good luck bug-finders rode0day.mit.edu/results
Rode0Day retweeted
It's been one year since we launched our continuous bug-finding competition, @Rode0day! We've spent the past year learning all we can about bugs and bug-finding and tomorrow morning, I'll be presenting some of what we've found at #woot19 usenix.org/conference/woot19…
There are still many undiscovered bugs in this month's bug-finding rodeo so we've pushed back the end date. Good luck bug-finders!
Our July Rode0day featuring buggy versions of sqlite, libjpeg, file, jq, and tinyexpr has begun! Our bugs this month are a bit different from usual. Think you can find them? Join the competition at rode0day.mit.edu
Our July Rode0day featuring buggy versions of sqlite, libjpeg, file, jq, and tinyexpr has begun! Our bugs this month are a bit different from usual. Think you can find them? Join the competition at rode0day.mit.edu
It's time to dust off your bug-finding systems- July's rode0day will launch tomorrow at 1700 UTC! The competition will feature some high quality bugs made just for your enjoyment.
Interested in joining our next bug-finding rodeo but don't know where to start? Check out this excellent video series from @MurmusCTF showing how to compete using AFL! youtube.com/watch?v=-uCnP64i…
And @MurmusCTF is now running a competition to triage some of his libjpeg crashes and write exploits for them. We're pretty sure many of these bugs are exploitable, so give it a try- github.com/murmus/Rode0Triag…. There are even prizes!
Our July Rode0day will begin about a week later than usual. We’ll announce the start date via twitter at least 24 hours in advance.
Rode0Day retweeted
Lots of big news: Tommorow at 3PM we'll be kicking off my next 5-part Youtube series, with recordings from the May @Rode0day. I also hit 10k Youtube subscribers over the weekend, included my face in the first video, and I'll be running a competition! youtu.be/-uCnP64it-8
The full datasets from our first 10 bug-finding competitions are now all available from rode0day.mit.edu/archive. We've finally automated the process so future datasets will be released much faster.
Congratulations to NU-AFL-QSYM for winning May's bug-finding rodeo after finding 80 of the 146 injected bugs! In total, the 8 competing teams found 104 (71%) of the injected bugs. We'll be releasing our full dataset for the competition soon.
Our latest bug-finding rodeo has just begun featuring buggy versions of tcpdump and sfconvert that are sure to give your bug-finding systems a challenge! The competition will run for 4 weeks and then we'll declare a winner and release the answers. Good luck!








