Releases: zaproxy/zap-extensions
Releases · zaproxy/zap-extensions
Active scanner rules version 53
Changed
- Maintenance changes.
- The SQL Injection Scan Rule filters reflected payload containing escaped characters like '&' and '"' before response content comparison to reduce false negatives.
Automation Framework version 0.25.0
Added
- Support for dynamically added header based session management method.
Fixed
- Active scan would fail if threadsPerHost set to zero.
Changed
- Maintenance changes.
Common Library version 1.14.0
Fixed
- Comparable Response functionality is now more robust and doesn't fail when processing types other than JSON Object (Issue 7736).
Ajax Spider version 23.12.0
Added
- Automation Framework - inScopeOnly option
Changed
- Add default Allowed Resources if none present in existing home directory when updating the add-on (Issue 7719).
Spider version 0.3.0
Changed
- Maintenance changes.
- Default number of threads to 2 * processor count.
Added
- Support for parsing .DS_Store files to find paths to try (Issue 30).
Fixed
- Spurious error message on setting user in AF job.
SOAP Support version 17
Added
- Support for relative file paths and ones including vars in the Automation Framework job.
Changed
- Maintenance changes.
Script Console version 35
Added
- Help explaining how to interact with Automation Framework plans.
- Support for relative file paths and ones including vars in the Automation Framework job.
Changed
- Maintenance changes.
Report Generation version 0.19.0
Added
- A description of riskdesc fields in the relevant report templates' help (Issue 7445).
- Support for relative report file and directory names in the Automation Framework job.
Changed
- Maintenance changes.
OpenAPI Support version 32
Added
- Support for relative file paths and ones including vars in the Automation Framework job.
Changed
- Maintenance changes.
GraphQL Support version 0.13.0
Added
- Support for relative file paths in the Automation Framework job.
Changed
- Dependency updates and maintenance changes.
Fixed
- Fixed exception in the variant when POST message has empty body and no content-type (Issue 7689).