This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author Guido
Recipients Devin Jeanpierre, Guido, alex, brett.cannon, christian.heimes, gregory.p.smith, miss-islington, r.david.murray, terry.reedy
Date 2019-07-08.14:11:58
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>

I've built a generic Python fuzzer and submitted it to OSS-Fuzz.

It works by implementing a "def FuzzerRunOne(FuzzerInput):" function in Python in which some arbitrary code is run based on FuzzerInput, which is a bytes object.

This is a more versatile solution than the current re, json, csv fuzzers as it requires no custom C code and adding more fuzzing targets is as easy as writing a new harness in Python and adding a build rule.

Code coverage is measured at both the CPython level (*.c) and the Python level (*.py). CPython is compiled with AddressSanitizer. What this means is that both CPython memory bugs and Python library bugs (excessive memory consumption, hangs, slowdowns, unexpected exceptions) are expected to transpire.

You can see my current set of fuzzers here:

The PR to OSS-Fuzz is

Currently, the only Python maintainer who will be receiving automated bug reports is gpshead. Are there any other developers who normally process Python security bug reports and would like to receive notifications?

Feel free to respond directly in the OSS-Fuzz PR thread.
Date User Action Args
2019-07-08 14:11:58Guidosetrecipients: + Guido, brett.cannon, terry.reedy, gregory.p.smith, christian.heimes, Devin Jeanpierre, alex, r.david.murray, miss-islington
2019-07-08 14:11:58Guidosetmessageid: <>
2019-07-08 14:11:58Guidolinkissue29505 messages
2019-07-08 14:11:58Guidocreate