This tab is used to configure one or more payload sets. The number of payload
sets depends on the attack type defined in the
Positions tab. For many common
tasks, such as fuzzing parameters, brute force guessing a user's password, or
cycling through page identifiers, only a single payload set is needed.
The configuration steps needed to configure a payload set are as follows:
- Select the payload set that you wish to configure from the drop-down
- Select the payload type to use from the drop-down
list. A large number of payload types are available, and these are
highly configurable, allowing you to quickly automate the generation of
payloads for virtually any situation:
- Configure the payload options
for the selected payload type.
- Configure any required
payload processing rules, to manipulate the
generated payloads in various ways.
- Configure the required payload
encoding, to ensure that the correct characters are
URL-encoded for safe transmission over HTTP.
Thursday, March 12, 2015
This release contains various bugfixes and minor enhancements, including:
- In the site map table, the "Method" column previously always showed GET for requests without a body, and POST for requests with a body, even if the actual method was different. This bug has now been fixed and the table shows the correct method.
- A bug which prevented client SSL certificates from being used when an upstream proxy is configured has been fixed.
- A bug which caused Decoder to fail to decode hex number HTML entities containing an upper-case X has been fixed.
See all release notes ›