Pretty much it.  You often provide them with a corpus and they start mutating it and trying lots of random data based on it with the goal being to crash code.  Fuzzing actually catches a remarkable number of problems with code.<p>The one I&#x27;ve seen the most of recently in general, and probably the highest quality blogs about it, has been American Fuzzy Loop, AFL: <a href="http:&#x2F;&#x2F;lcamtuf.coredump.cx&#x2F;afl&#x2F;" rel="nofollow">http:&#x2F;&#x2F;lcamtuf.coredump.cx&#x2F;afl&#x2F;</a>  there are a number of programs in its treasure chest, I&#x27;d encourage looking at a few of the links if you&#x27;re even remotely curious about the bugs fuzzing can expose.<p>This one has been making a fair splash in the go community, take a look at the trophy list about a third of the way down the page: <a href="https:&#x2F;&#x2F;github.com&#x2F;dvyukov&#x2F;go-fuzz" rel="nofollow">https:&#x2F;&#x2F;github.com&#x2F;dvyukov&#x2F;go-fuzz</a>