Prior to heading down for Blackhat/Defcon I wanted to post a public preview of the next version of Peach.  Consider this an alpha/development release with limited documentation, missing features, and no doubt many bugs.

Over the next days/weeks I’ll be posting up looks at different features in Peach 2.0.  For now this will be the only tutorial/docs for the 2.0 series until we are closer to a full release.

Download Peach 2.0 Technology Preview

Here is what’s new in Peach 2.0:

• Separation between data generation/mutation and data modeling
• Data modeling performed in XML creating lower bar of entry
• Ability to create fuzzers w/o writing Python.
• Built ontop of existing framework, can fully reuse any custom written Generators, Transformers, and Publishers
• Assisted Data Modeling easier with XML specification
• Convert WireShark packet captures to XML data models
• Cracking of data based on data models

To come in Peach 2.0 as we approach release:

• Inclusion of several simple state models
• Expansion of Agent abilities
• More complex data generation based on data modeling
• Expose new features through language bindings (Peach.NET, .C, .J, etc)

What hasn’t changed?

• Fuzzers based on Peach 1.0 will continue to work with Peach 2.0
• Instrumentation of clients to hook for fuzzing still very easy
• Still customizable and extendable, built on-top of existing framework and interfaces so you can re-use existing code

Peach has been stable for quite some time, but I finally feel it’s time to label a release as the 1.0.  I have forked the code as development on Peach 2.0 is in full swing.  Several Generators have been updated and a few bugs fixed since the last release.

From here on out, only fix releases in the 1.0 branch will occur, new features will end up in the 2.0 series.

Download Peach Fuzzing Framework 1.0

New and notable in 1.0:

• PeachShark — Convert WireShark captures into Peach Fuzzers!
• StringTokenFuzzer — Tokenizes input string and performs string mutations and fuzzing of each token in the string.
• BadDerEncodedOctetString and BadBerEncodedOctetString — For testing ASN.1 based data
• Flags2 — Better handling/fuzzing of bit flags