zaproxy: Scan report does not have enough details on the alerts

Is your feature request related to a problem? Please describe.

The Parameter in the instance details are always empty, sometimes Evidence is missing, and sometimes Attack is missing in the report. Please see below screenshot. image

FYI. I ran the scan using below command:

docker run --network=zap-network --name zap \
	-v ${WORKSPACE}:/zap/wrk/:rw -t owasp/zap2docker-weekly \
	zap-api-scan.py -f openapi -z "-addoninstall pscanrulesBeta -config formhandler.fields.field(0).fieldId=status -config formhandler.fields.field(0).value=sold -config formhandler.fields.field(0).enabled=true" -r api-scan-report-zap.html -J api-scan-report-zap.json -t 'https://petstore3.swagger.io/api/v3/openapi.json'

Describe the solution you’d like

We want all the details displayed in the report, what request being made and what parameters/body being used.

Actually I can’t even find the request details (request header, parameter, body) in the ZAP log, is this by design and why?

Describe alternatives you’ve considered

No.

Screenshots

No response

Additional context

No response

Would you like to help fix this issue?

  • Yes

About this issue

  • Original URL
  • State: closed
  • Created 3 years ago
  • Comments: 16 (8 by maintainers)

Most upvoted comments

@YanFangJi ooops - that was nearly a year ago 😮 The User Group is the right place, but we are a small team and sometimes questions slip through the cracks. The best thing to do is to post to that thread saying that you still want to know 😁

zap_pre_shutdown should be fine.

https://github.com/zaproxy/zaproxy/issues/8254#issuecomment-1865364147

The scan hooks give you access to the ZAP API (zap parameter), which can be used to call the API of the add-ons, e.g.: https://www.zaproxy.org/docs/desktop/addons/report-generation/api/