Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Reduce passive scanner logging for messages that were deleted

See original GitHub issue

I deleted a bunch of stuff from the Sites Tree while there was still a passive scan queue.

The passive scanner probably doesn’t need to log the full trace on these.
Could the queue be modified when things are deleted from the Sites Tree?

Versions: Java: 11.0.13 ZAP: Dev

68347 [ZAP-PassiveScan-4] ERROR org.zaproxy.zap.extension.pscan.PassiveScanTask - Parser failed on record 387 from History table
org.parosproxy.paros.network.HttpMalformedHeaderException: No history reference for id 387 type=2
	at org.parosproxy.paros.model.HistoryReference.getHttpMessage(HistoryReference.java:454) ~[main/:?]
	at org.zaproxy.zap.extension.pscan.PassiveScanTask.run(PassiveScanTask.java:101) ~[main/:?]
	at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:515) ~[?:?]
	at java.util.concurrent.FutureTask.run(FutureTask.java:264) ~[?:?]
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128) ~[?:?]
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628) ~[?:?]
	at java.lang.Thread.run(Thread.java:829) ~[?:?]
68348 [ZAP-PassiveScan-1] ERROR org.zaproxy.zap.extension.pscan.PassiveScanTask - Parser failed on record 388 from History table
org.parosproxy.paros.network.HttpMalformedHeaderException: No history reference for id 388 type=2
	at org.parosproxy.paros.model.HistoryReference.getHttpMessage(HistoryReference.java:454) ~[main/:?]
	at org.zaproxy.zap.extension.pscan.PassiveScanTask.run(PassiveScanTask.java:101) ~[main/:?]
	at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:515) ~[?:?]
	at java.util.concurrent.FutureTask.run(FutureTask.java:264) ~[?:?]
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128) ~[?:?]
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628) ~[?:?]
	at java.lang.Thread.run(Thread.java:829) ~[?:?]
68348 [ZAP-PassiveScan-4] ERROR org.zaproxy.zap.extension.pscan.PassiveScanTask - Parser failed on record 389 from History table
org.parosproxy.paros.network.HttpMalformedHeaderException: No history reference for id 389 type=2
	at org.parosproxy.paros.model.HistoryReference.getHttpMessage(HistoryReference.java:454) ~[main/:?]
	at org.zaproxy.zap.extension.pscan.PassiveScanTask.run(PassiveScanTask.java:101) ~[main/:?]
	at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:515) ~[?:?]
	at java.util.concurrent.FutureTask.run(FutureTask.java:264) ~[?:?]
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128) ~[?:?]
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628) ~[?:?]
	at java.lang.Thread.run(Thread.java:829) ~[?:?]
68348 [ZAP-PassiveScan-1] ERROR org.zaproxy.zap.extension.pscan.PassiveScanTask - Parser failed on record 390 from History table
org.parosproxy.paros.network.HttpMalformedHeaderException: No history reference for id 390 type=2
	at org.parosproxy.paros.model.HistoryReference.getHttpMessage(HistoryReference.java:454) ~[main/:?]
	at org.zaproxy.zap.extension.pscan.PassiveScanTask.run(PassiveScanTask.java:101) ~[main/:?]
	at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:515) ~[?:?]
	at java.util.concurrent.FutureTask.run(FutureTask.java:264) ~[?:?]
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128) ~[?:?]
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628) ~[?:?]
	at java.lang.Thread.run(Thread.java:829) ~[?:?]

Issue Analytics

State:
Created a year ago
Reactions:1
Comments:5 (4 by maintainers)

Top GitHub Comments

1reaction

thc202commented, Jun 22, 2022

The passive scanner does not have a queue as such, it’s just a counter for the history ID.

IMO it could just log as debug. If the user deleted the message it’s safe to assume that the message will no longer be scanned.

1reaction

psiinoncommented, Jun 21, 2022

Agreed. We could always log the trace just on debug level or similar

Top Results From Across the Web

Nessus disk space usage - Tenable Community

How to clear some space in Nessus and what files can be deleted. ... Check the main log file within Nessus which is...

How to Recover Deleted Text Messages: Your Complete Guide

Method 2: Recover deleted texts messages from iCloud website · Step 1: Log in to iCloud.com using your Apple ID · Step 2:...

Take response actions on a device in Microsoft Defender for ...

Take response actions on a device such as isolating devices, collecting an investigation package, managing tags, running an av scan, ...

Passive Reconnaissance - an overview | ScienceDirect Topics

During passive reconnaissance, an attacker may unintentionally expose information to a target from the nodes that are active in these tasks. In this...

FAQ - Passive BLE Monitor integration - GitHub Pages

Passively monitors BLE messages from Xiaomi Mijia BLE MiBeacon, Qingping, ATC, ... To get a log with the available MAC addresses, enable logger...