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: If scan engines has no module to scan, it causes entire scan history to crash, causing AttributeError #1103

Closed
1 task done
yogeshojha opened this issue Dec 5, 2023 · 1 comment · Fixed by #1104
Closed
1 task done
Labels
bug Something isn't working

Comments

@yogeshojha
Copy link
Owner

Is there an existing issue for this?

  • I have searched the existing issues

Current Behavior

Say an scan engine exists, some scans are performed. But due to any reasons, scan engine now has commented out all the modules, or say scan engine has some issues, it causes entire scan history to not load up.

Example:

image

Expected Behavior

Scan history should load as usual even if scan engines has no modules at the moment.

Steps To Reproduce

  1. Create a scan engine
  2. Scan a target
  3. Comment out the entire yaml config
  4. Scan history will not load up

Environment

- reNgine: 2.0.X
- OS: Ubuntu
- Python: NA
- Docker Engine: NA
- Docker Compose: NA 
- Browser: NA

Anything else?

No response

@yogeshojha yogeshojha added the bug Something isn't working label Dec 5, 2023
Copy link
Contributor

github-actions bot commented Dec 5, 2023

👋 Hi @yogeshojha,
Issues is only for reporting a bug/feature request. Please read documentation before raising an issue https://rengine.wiki
For very limited support, questions, and discussions, please join reNgine Discord channel: https://discord.gg/azv6fzhNCE
Please include all the requested and relevant information when opening a bug report. Improper reports will be closed without any response.

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

Successfully merging a pull request may close this issue.

1 participant