11151 commits

This branch

This branch

All branches

Author	SHA1	Message	Date
Miroslav Štampar	9fa2abb5dd	Fix for --sql-query dropping duplicate rows and query's ordering	2026-11-12 11:50:32 +01:00
Miroslav Štampar	d55d163352	Fix for -p matching inside other parameter names (e.g. id in x-id)	2026-11-12 11:50:32 +01:00
Miroslav Štampar	54c5a6582b	Fix for declined forcing of --dbms still restricting fingerprinting	2026-11-12 11:50:32 +01:00
Miroslav Štampar	a7a9d7a8fe	Fix for --eval dropping parameters after an empty one	2026-11-12 11:50:32 +01:00
Miroslav Štampar	f9e53443ed	Fix for anti-CSRF tokens containing '+' (and GET token not found with -p)	2026-11-12 11:50:32 +01:00
Miroslav Štampar	3c2384525c	Fix for --param-del being URL encoded in POST payload requests	2026-11-12 11:49:07 +01:00
Miroslav Štampar	161af41c9c	Fix for chained tamper hints (e.g. luanginx,space2comment)	2026-11-12 11:49:07 +01:00
Piyush satyarthi	cb5216564a	Close leaked sqlite3 connections (ResourceWarning on Python 3.13+) (#6181) ... Python 3.13+ reports sqlite3 connections that are garbage collected without being closed. The unit tests print a run of "ResourceWarning: unclosed database" lines on Linux/CPython 3.14: - SQLAlchemy.close() only returned its connection to the engine's pool, so the underlying DBAPI connection (e.g. sqlite3 for '-d sqlite://...') stayed open. Dispose the engine on close. - vulnTest() used "with sqlite3.connect(...)", which commits but does not close the connection. Use contextlib.closing(). - test_multibit and test_sqlalchemy never closed what they opened. Co-authored-by: PiyushSatyarthi <244159432+PiyushSatyarthi@users.noreply.github.com>	2026-11-12 09:46:10 +01:00
Miroslav Štampar	eca9ff2e13	Fixes #6180	2026-11-10 15:10:16 +01:00
Miroslav Štampar	397a3bde2e	Implements #6177	2026-11-06 15:31:35 +01:00
Miroslav Štampar	097f4d2c37	Fixes #6176	2026-11-06 15:03:08 +01:00
Miroslav Štampar	202d8cc1c4	Adding some more entries into common files list	2026-11-06 09:15:14 +01:00
Miroslav Štampar	f65de0e890	Minor update	2026-11-04 10:20:01 +01:00
cuteNBD	b333a14d8b	Keep WebSocket responses on normal closure (#6173) ... Co-authored-by: cuteNBD <206630735+bingdongni@users.noreply.github.com>	2026-11-04 10:18:29 +01:00
cuteNBD	74f50122fb	Preserve custom Host headers for WebSocket requests (#6172) ... Co-authored-by: cuteNBD <206630735+bingdongni@users.noreply.github.com>	2026-11-04 10:18:06 +01:00
Miroslav Štampar	bf8b9956e0	Fixes #6170	2026-11-03 22:04:29 +01:00
Miroslav Štampar	8476cf4d09	Fix related to the #6171 (WebSocket Host port)	2026-11-03 22:04:01 +01:00
cuteNBD	3130623afc	Preserve non-default ports in Host headers (#6171) ... Co-authored-by: cuteNBD <206630735+bingdongni@users.noreply.github.com>	2026-11-03 22:03:38 +01:00
Miroslav Štampar	c15f4bf055	Fixes #6168	2026-11-02 11:13:40 +01:00
Miroslav Štampar	9cd0619e2b	Dummy update	2026-10-30 17:31:39 +01:00
Miroslav Štampar	6faa9bb929	Release 1.10.11 (#6165)	2026-10-30 17:30:50 +01:00
Miroslav Štampar	2ff5db17ba	Fixes #6165	2026-10-30 17:26:13 +01:00
Miroslav Štampar	c42ebd7acf	Fixes #6164	2026-10-29 14:24:18 +01:00
Miroslav Štampar	2d046c1a75	Fixes #6163	2026-10-29 14:15:37 +01:00
Miroslav Štampar	f8a42cf016	Fixes CI/CD errors	2026-10-27 13:47:04 +01:00
Miroslav Štampar	81d17b1ad2	Fixes #6162	2026-10-27 13:29:36 +01:00
Miroslav Štampar	083d9d0e6f	Fix for Ctrl-C hang on Python 3.14 (leaked cache locks)	2026-10-27 13:11:04 +01:00
Miroslav Štampar	a01582b83f	Minor update	2026-10-27 11:10:16 +01:00
Miroslav Štampar	94f8cf8136	Minor update	2026-10-27 09:34:04 +01:00
Miroslav Štampar	6a94f23251	Update related to the #6161	2026-10-27 09:23:47 +01:00
Miroslav Štampar	6df778743f	Update related to the #6161	2026-10-27 09:17:37 +01:00
Miroslav Štampar	6e06114947	Fixes #6157	2026-10-25 16:29:02 +01:00
Miroslav Štampar	c9745f883d	Minor update	2026-10-23 00:33:58 +02:00
Miroslav Štampar	11afdcb026	Fixes #6152	2026-10-21 13:51:35 +02:00
Miroslav Štampar	5b8a2faab1	Doing some cleaning for web search requests	2026-10-21 12:10:18 +02:00
Miroslav Štampar	da21091459	Update regarding the search engines naggings	2026-10-21 11:08:07 +02:00
Raju Ranjan	5e2a6aeec8	fix(search): parse current Bing result links (#6150) ... While looking into #6009 I noticed the Bing fallback in -g never returns anything, even when Bing itself serves a normal results page. Two things changed on Bing's side. The result anchor now carries target="_blank" before href, so '<h2><a href="..." h=' no longer matches at all. And the href is no longer the target URL but a tracking redirect (https://www.bing.com/ck/a?...&u=a1<base64url>), where the real link sits base64url-encoded after the "a1" prefix in the u parameter. The regex now allows extra attributes on both tags and captures either the u payload of a ck/a redirect or a plain href. The payload is decoded with decodeBase64(), which already deals with the URL-safe alphabet and the missing padding. Plain hrefs still work the same as before (with &amp; unescaped), in case Bing serves the old markup to some clients. Checked against a saved live results page (0 -> 10 links) and the old markup, and --smoke-test passes. Google still can't be scraped since it only serves a JS page now, so this doesn't fully close #6009, but Bing is usable again as a fallback when DuckDuckGo blocks the IP.	2026-10-21 10:41:33 +02:00
Miroslav Štampar	8461fd402b	Fixes #6151	2026-10-21 10:37:13 +02:00
Miroslav Štampar	9b0e262560	Fix related to the #6149	2026-10-20 10:07:33 +02:00
Miroslav Štampar	d57415479a	Minor update	2026-10-19 18:37:58 +02:00
Miroslav Štampar	d0ad9b2e34	Adding cross-DBMS security configuration audit (--audit)	2026-10-19 18:34:39 +02:00
Miroslav Štampar	6530184e2c	Implements #4271	2026-10-19 11:46:27 +02:00
Miroslav Štampar	e90078184d	Implements --links (#21)	2026-10-19 10:19:34 +02:00
Miroslav Štampar	559d6f4543	Increasing the GraphQL timeout in tests	2026-10-18 22:37:59 +02:00
Miroslav Štampar	71af9b3d8a	Fixes CI/CD issues	2026-10-18 22:21:02 +02:00
Miroslav Štampar	516f55935c	Implements #4973	2026-10-18 22:14:12 +02:00
Miroslav Štampar	b208262c37	Fixes #4708	2026-10-18 21:54:21 +02:00
Miroslav Štampar	9a1660aa12	Minor cleaning after #6146	2026-10-17 13:06:38 +02:00
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
Miroslav Štampar	c94f6d0041	Update regarding #6145	2026-10-16 12:15:59 +02:00