Lingolol

0 posts0 participants0 posts today

danzinDo you maintain or contribute to a <a href="https://mastodon.social/tags/Python" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Python</a> package that includes a C extension? Would you like to run a fuzzer against it?If so, let me know and I will run it, or help you to get it running. The fuzzer is <a href="https://mastodon.social/tags/fusil" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#fusil</a>, which generates random code calling into your functions and methods. It's useful to check for crashes on invalid inputs or unexpected call patterns.It has found about 50 crashes in <a href="https://mastodon.social/tags/CPython" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#CPython</a>, 20 in <a href="https://mastodon.social/tags/PyPy" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#PyPy</a>, 6 in <a href="https://mastodon.social/tags/Numpy" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Numpy</a> etc.<a href="https://mastodon.social/tags/fuzzing" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#fuzzing</a> <a href="https://mastodon.social/tags/fuzzer" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#fuzzer</a> <a href="https://mastodon.social/tags/testing" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#testing</a> See here: <a href="https://github.com/devdanzin/fusil/issues/37" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://github.com/devdanzin/fusil/issues/37</a>

danzinWe're up to 30 <a href="https://mastodon.social/tags/CPython" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#CPython</a> crashers found using <a href="https://mastodon.social/tags/Fusil" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Fusil</a> this year, about 90% of them considered valid.In 2008, I had reported 5 cases using the same <a href="https://mastodon.social/tags/fuzzer" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#fuzzer</a>, 4 of which were release blockers.<a href="https://mamot.fr/@vstinner" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@vstinner</a>, Fusil's creator, also reported a bunch of issues with it.After running for a while (on free AWS and Oracle cloud tiers), crash hits are getting harder to find.We need new fuzzing inputs. Feel free to suggest improvements that could find new crashers.<a href="https://github.com/devdanzin/fusil" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://github.com/devdanzin/fusil</a> <a href="https://mastodon.social/tags/Python" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Python</a> <a href="https://mastodon.social/tags/Fuzzing" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Fuzzing</a>

Giovanni SquilleroWhoa 🍾, cited by 100! <a href="https://sigmoid.social/tags/GP" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#GP</a> <a href="https://sigmoid.social/tags/EA" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#EA</a> <a href="https://sigmoid.social/tags/Fuzzer" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Fuzzer</a> <a href="https://scholar.google.com/citations?view_op=view_citation&citation_for_view=99_kdAQAAAAJ:eQOLeE2rZwMC&hl=en&as_sdt=0,5&authuser=1" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://scholar.google.com/citations?view_op=view_citation&citation_for_view=99_kdAQAAAAJ:eQOLeE2rZwMC&hl=en&as_sdt=0,5&authuser=1</a>

Benjamin Carr, Ph.D. 👨🏻‍💻🧬Boffins from ETH Zurich have devised a novel <a href="https://hachyderm.io/tags/fuzzer" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#fuzzer</a> for finding bugs in <a href="https://hachyderm.io/tags/RISCV" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#RISCV</a> chips and have used it to find more than three dozen. When applied to six actual RISC-V <a href="https://hachyderm.io/tags/CPU" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#CPU</a> – <a href="https://hachyderm.io/tags/VexRiscv" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#VexRiscv</a>, <a href="https://hachyderm.io/tags/PicoRV32" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#PicoRV32</a>, <a href="https://hachyderm.io/tags/Kronos" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Kronos</a>, <a href="https://hachyderm.io/tags/CVA6" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#CVA6</a>, Rocket, and BOOM – Cascade found 37 new bugs (translating to 29 <a href="https://hachyderm.io/tags/CVE" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#CVE</a>) in five of these six designs. <a href="https://www.theregister.com/2023/10/24/cascade_fuzzer_zurich/" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://www.theregister.com/2023/10/24/cascade_fuzzer_zurich/</a>

Rob RicciOf all the super nuts things I have seen with <a href="https://discuss.systems/tags/ChatGPT" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#ChatGPT</a>, this is the most superly nuts-est, and I am seriously interested in what others think is going on here.ChatGPT claims to have run my student Luciano's <a href="https://discuss.systems/tags/distributed" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#distributed</a> <a href="https://discuss.systems/tags/fuzzer" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#fuzzer</a>. It claims to have *found a specific bug* in libpng, which we know is real. And it *suggested stuff to add to his README*.The crazy thing about the bug it claims to have found is that this is the *same* bug Luciano found by actually running the fuzzer. That bug *is* in a CVE, but there is not anything up on the web indicating that *this* fuzzer can find *this* bug. ChatGPT even produces a nice summary of the bug (probably taken from the CVE). So what's probably going on here? Did it actually run this fuzzer, interpret the crashes it found, and successfully connect them to a CVE? Seems amazing if true, but highly unlikely. Or did it find some other way to (correctly) guess what bug would be found? More plausible, but still pretty wild.And it clearly did actually go through the github repo, which has only been online a few weeks, since it suggested expanding the README with stuff that is only in the library.This is wild.<a href="https://twitter.com/cybergenik/status/1601868158297833473" rel="nofollow noopener noreferrer" target="_blank">https://twitter.com/cybergenik/status/1601868158297833473</a>

Recent searches

Search options

Administered by:

Server stats:

#fuzzer