This is cool! If anybody is interested in looking at the bugs that were found, they can be found on Github: https://github.com/php/php-src/issues?q=author%3AYua

This is cool! If anybody is interested in looking at the bugs that were found, they can be found on Github: https://github.com/php/php-src/issues?q=author%3AYuanchengJiang+ https://github.com/php/php-src/issues?q=author%3AYuanchengJi... If you work with some interpreted language that is written in C or C++, it is actually quite easy to fuzz the interpreter using the scripting language natively. I outlined how to add fuzzing functions into the Pike scripting language to interact with the AFL++ fuzzer here: https://joshua.hu/aflplusplus-fuzzing-scripting-languages-natively https://joshua.hu/aflplusplus-fuzzing-scripting-languages-na... If you have a very large codebase in such a language, you can just replace whatever function introduces some data highest on the callstack with the (new, introduced) function that retrieves fuzzing data from AFL++, and effectively fuzz all of the internal functions that your codebase uses. PHP, Perl, Ruby, or some esoteric language, are all pretty good targets for this.