So I'm doing a docker full scan, and my scan seems to be stuck at active scan 18%.
I'm worrying that the Wappalyzer might be the issue because in the logs, I can only see Wapplyzer logs.
So I was thinking about disabling it in the scan with the config file. But I can't find the plugin ID for it.
Here are a part of the logs in zap.log.
2024-01-22 07:22:19,182 [ZAP-PassiveScan-1] WARN PassiveScanTask - Passive Scan rule Wappalyzer Scanner (Tech Detection) took 150 seconds to scan text/html; charset=utf-8 95343
2024-01-22 07:23:30,550 [ZAP-PassiveScan-2] WARN PassiveScanTask - Passive Scan rule Wappalyzer Scanner (Tech Detection) took 140 seconds to scan loki%%26ol; charset=utf-8 95764
2024-01-22 07:24:50,199 [ZAP-PassiveScan-1] WARN PassiveScanTask - Passive Scan rule Wappalyzer Scanner (Tech Detection) took 143 seconds to scan pdate_email&original_lead_update_phone&project=DM227730&update_scancode text/html; charset=utf-8 95623
2024-01-22 07:26:02,982 [ZAP-PassiveScan-2] WARN PassiveScanTask - Passive Scan rule Wappalyzer Scanner (Tech Detection) took 148 seconds to scan 95505
2024-01-22 07:27:22,338 [ZAP-PassiveScan-1] WARN PassiveScanTask - Passive Scan rule Wappalyzer Scanner (Tech Detection) took 147 seconds to scan eria=b%27project%3DDM227730%27&search_criteria_name=ZAP text/html; charset=utf-8 95607
2024-01-22 07:28:41,983 [ZAP-PassiveScan-2] WARN PassiveScanTask - Passive Scan rule Wappalyzer Scanner (Tech Detection) took 149 seconds to scan me=ZAP text/html; charset=utf-8 95558
2024-01-22 07:29:57,138 [ZAP-PassiveScan-1] WARN PassiveScanTask - Passive Scan rule Wappalyzer Scanner (Tech Detection) took 150 seconds to scan ; charset=utf-8 95542
2024-01-22 07:31:08,555 [ZAP-PassiveScan-2] WARN PassiveScanTask - Passive Scan rule Wappalyzer Scanner (Tech Detection) took 142 seconds to scan charset=utf-8 95440
2024-01-22 07:31:24,931 [ZAP-IO-Server-1-123] INFO ZapHttpRequestRetryExec - Recoverable I/O exception (org.apache.hc.core5.http.NoHttpResponseException) caught when processing request to {s}->
2024-01-22 07:32:20,185 [ZAP-PassiveScan-1] WARN PassiveScanTask - Passive Scan rule Wappalyzer Scanner (Tech Detection) took 139 seconds to scan 62-5862B2A32069%26issue_org%3DZAP%26issue_scancode%3DZAP%26lead_requestor_id%3D9E664D5C-DAE8-44FA-901A-A1DBA4E4FC06%26loki%3DNvJYQNqxfAs4VamYSfbUBMxHgTKFBE3aREOqJ9UgoNoC1opS64ZQLGOeceCGsPmC%26notes%26project%3DDM227730%27&search_criteria_name=ZAP text/html; charset=utf-8 95798
2024-01-22 07:33:34,817 [ZAP-PassiveScan-2] WARN PassiveScanTask - Passive Scan rule Wappalyzer Scanner (Tech Detection) took 142 seconds to scan
2024-01-22 07:35:02,878 [ZAP-PassiveScan-1] WARN PassiveScanTask - Passive Scan rule Wappalyzer Scanner (Tech Detection) took 150 seconds to scan ext/html; charset=utf-8 95550
2024-01-22 07:35:51,398 [ZAP-PassiveScan-2] WARN PassiveScanTask - Passive Scan rule Wappalyzer Scanner (Tech Detection) took 132 seconds to scan eria=b%27project%3DDM224400%27&search_criteria_name=ZAP text/html; charset=utf-8 90603
The zap.log file is flooded with messages like that. Does this look like the Wappalyzer is causing the scan to run indefinitely?