Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Repeated TypeError in Burp Scanner Plugin using InQL Extension #139

Open
ShanoojM opened this issue Nov 5, 2024 · 0 comments
Open

Repeated TypeError in Burp Scanner Plugin using InQL Extension #139

ShanoojM opened this issue Nov 5, 2024 · 0 comments

Comments

@ShanoojM
Copy link

ShanoojM commented Nov 5, 2024

Dear Support Team,

I am encountering a recurring error within our Burp Scanner plugin, specifically in the inql.traffic_scan.scan_handler.py module. Below is the full error log for reference:

Error Log:
Traceback (most recent call last):
File "pyclasspath/inql/traffic_scan/scan_handler.py", line 236, in doActiveScan
File "pyclasspath/inql/traffic_scan/scan_handler.py", line 134, in _get_matches
TypeError: object of type 'NoneType' has no len()

at org.python.core.Py.TypeError(Py.java:234)
at org.python.core.PyObject.__len__(PyObject.java:637)
at org.python.core.__builtin__.len(__builtin__.java:729)
...
at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:317)
at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1144)
at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:642)
at java.base/java.lang.Thread.run(Thread.java:1570)

This error appears to originate in the _get_matches function within scan_handler.py, where a NoneType object is unexpectedly being passed to len(). This is likely due to an uninitialized or failed variable, which is expected to hold a list or string.

The error repeatedly occurs during the execution of the doActiveScan function, which is part of the BurpScannerCheck class, and it impacts multiple threads, as shown in the multi-threaded context (ThreadPoolExecutor). This affects the consistency of the scan results and leads to multiple interruptions in the scan process.

Could you please advise on any potential solutions? Specifically, any insights into the _get_matches function’s handling of NoneType values or guidance on ensuring proper initialization of variables would be very helpful.

Regards,
Shanooj

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant