This is a collection for PeachPits for Peach Fuzzer to facilitate the fuzzing of EAP, IEEE 802.1x and RADIUS.
The PeachPits themselves are useful, however the real power is in the Fuzzer XMLs. They bind the DataModels into full sessions that can be directed towards the target of choice. That being said, they are complex and can be hackish at times, so be prepared to understand whats going on before you venture on :)
The DataModels are often linked together and are meant to be imported/combined by a fuzzer XML. These DataModels are essentially rolled up into two all-encompassing ones: Radius.xml and Ieee802.1x.xml. Radius.xml should be the only reference to a non-bridged Radius Fuzzer. Radius.xml imports Eap.xml only for Request/Response Identity, then Radius.xml relies on the individual EAP-Type data models to build its Access-Requests and Challenges.
This DataModel is used heavily by other EAP-Types.
Applicable RFC(s):
DataModel for EAP-FAST, which is mostly a wrapper around TLS. EAP-FAST Supports a specialized version of EAP-GTC, which is not included in this DataModel.
Applicable RFC(s):
DataModel for EAP-GTC. Note this is not the EAP-FAST version of EAP-GTC.
Applicable RFC(s):
Applicable RFC(s):
Applicable RFC(s):
DataModel for EAP-MSCHAPv2. This is mostly just the EAP Encapsulation around Mschapv2.xml
DataModel for PEAP. This is mostly just an encapsulation around EAP-TLS.
DataModel for EAP-TLS. This is mostly just the EAP Encapsulation around Tls.xml
Applicable RFC(s):
Applicable RFC(s):
This DataModel is meant to encapsulate the other EAP-Type and derivative DataModels to be used by a RawEthernetPublisher or Raw 802.11 Publisher
This is a supporting DataModel to EAP-MSCHAPv2, EAP-FAST, PEAP, and others.
Applicable RFC(s):
RADIUS Authentication DataModel and is meant to encapsulate the other EAP-Type and derivative DataModels to be used by a UDP Publisher.
Applicable RFC(s):
This is a supporting DataModel. Very basic TLS DataModel for all EAP-Types which support it (e.g. EAP-FAST, EAP-PEAP, EAP-TLS, EAP-TTLS).
Various utility Models such as the Domain/Username one and Cisco State. This is a supporting DataModel to the EAP DataModels.
Many RADIUS servers act slightly different from one another, so a Fuzzer XML was created for each RADIUS server. That being said, there is heavy overlap between them. You'll want to manually look at the fuzzers and the Configuration XML file to ensure the Fuzzer is set up appropriately with your set up.
Most fuzzers come with a bootstrap script that is meant to just show how to invoke the fuzzer using them. This are really hackish and should be used mostly as a reference.
React
Typescript
Django
Laravel
Facebook
Microsoft
Google
Alibaba
D3
Tencent