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

bug(scan): Dalfox too long and heavy on target #60

Open
1 task done
psyray opened this issue Apr 22, 2024 · 0 comments
Open
1 task done

bug(scan): Dalfox too long and heavy on target #60

psyray opened this issue Apr 22, 2024 · 0 comments
Labels
bug Something isn't working

Comments

@psyray
Copy link
Contributor

psyray commented Apr 22, 2024

Is there an existing issue for this?

  • I have searched the existing issues

Current Behavior

While testing issues, I launched a Vuln scan on testphp.vulnweb.com.
It contains DalFox in the default Full Scan Engine.

It runs for more than 1h30 and it did not finish yet.
I try top stop scan, Dalfox continues.

So we need to test this part and look for the problem.

Maybe we should remove those long waiting scan to leave the user make a choice.
Or we should set a less resource intensive default config for Dalfox, which catch result faster

image

image

Expected Behavior

Dalfox should run fast and should stop when aborted from GUI

Steps To Reproduce

Run vulnerability scan contained in the Full Scan default engine
Beware of the target !!!

Environment

- reNgine: 2.0.5
- OS: Debian 12
- Python: 
- Docker Engine: 
- Docker Compose: 
- Browser:

Anything else?

To end Dalfox task, you need to find the root celery process id and kill it using root user.

@psyray psyray added the bug Something isn't working label Apr 22, 2024
@yarysp yarysp changed the title bug: Dalfox too long and heavy on target bug(scan): Dalfox too long and heavy on target May 21, 2024
@psyray psyray added this to the v2.1.0 release milestone Jul 7, 2024
@psyray psyray modified the milestones: v2.1.0 release, v2.2.0 release Aug 27, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant