Bharath Vemula 0cf2f6db07 Fix REST API multi-target scans returning only the last target's results (#2503) (#6146) ...

A scan covering multiple targets inside a single API task (crawl,
'-m' bulk file, forms) ran every target through one StdDbOut keyed by
the single taskid, so _storeData()'s COMPLETE branch deleted each
earlier target's TARGET/TECHNIQUES rows - /scan/<id>/data returned
only the last target's results.

Mirror the --report-json fix for #6123: controller.start() now sets
kb.reportTaskId per target for API scans too, StdDbOut.write() keys
data rows '<taskid>-<n>' per target, and scan_data() folds the
per-target rows back into the task's flat result in target order.
Single-target scans keep the exact same response shape.

Regression tests in tests/test_api.py (TestStdDbOutMultiTarget,
TestScanDataMultiTarget).

2026-10-17 13:02:34 +02:00

..

__init__.py

Year bump

2026-01-01 19:12:07 +01:00

action.py

Adding more WAF friendly fingerprinting payloads

2026-08-17 14:25:46 +02:00

checks.py

Update regarding #6145

2026-10-16 12:15:59 +02:00

controller.py

Fix REST API multi-target scans returning only the last target's results (#2503) (#6146)

2026-10-17 13:02:34 +02:00

handler.py

Adding Esperanto DBMS agnostic engine

2026-07-16 18:13:32 +02:00