Breaking Ruby’s Unmarshal with AFL-Fuzz
David Moore

Thx for the reply. Yes I noticed in this case you were targeting ruby itself. Let’s say for instance I’d want to target a ruby gem with C extensions. The main idea would be to compile the extension manually with afl, and create a C fuzzer program that includes the library and target specific functions. The hard part in this case is that extensions are written in the ruby way, and unless a lot of modifications and head banging, it’s not a straight forward job. My question really is: if I compile ruby itself with afl and the C extension, if I create a ruby script that includes the .so extension shared object, and I invoke like this: ‘afl-fuzz -i in -i out ruby fuzz.rb’ , will I be targeting the actual C extension, or ruby alone? Does it make sense? Thanks for your time :)

One clap, two clap, three clap, forty?

By clapping more or less, you can signal to us which stories really stand out.