This bug is depending on bug #6714 end behavior if zaproxy should run within user privileges then this bug im reporting now is not a bug but 6714 must be fixed, If zaproxy should be running in root ...
i am using python with owasp-zap-v2.4 module to automate scans, since started to use docker with 2.9.0 i am seeing errors like this: [ZAP-SpiderThreadPool-0-thread-2 ...
一部の結果でアクセス不可の可能性があるため、非表示になっています。
アクセス不可の結果を表示する