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(scope): Nuclei only scan the first endpoint (https://domain.com/) (HTTPS) and do not scan the next endpoints (http://domain.com/) (HTTP) #217

Open
3 tasks done
haryisharry opened this issue Oct 14, 2024 · 1 comment
Labels
bug Something isn't working

Comments

@haryisharry
Copy link

Current Behavior

Run Full Scan and in the Vulnerability Scan, Nuclei only scan the first endpoint (https://domain.com/) (HTTPS) and do not scan the next endpoints (http://domain.com/) (HTTP) , in the target we have a bug to test. I search in the source code and found the file "input_endpoints_vulnerability_scan.txt" is called one time only before it be converted to urls_unfurled.txt. This may cause this issue.

Expected Behavior

Nuclei scan ALL found endpoints.

Steps To Reproduce

  1. Install Branch: release/2.1.0 or any version
  2. Run "Full Scan" on target with multi vulnerabilities on many endpoints, especially : "https" endpoint and "http" endpoints
  3. No vulnerabilities endpoint on "http endpoints" found.

Environment

- reNgine: 2.1.0 PR
- OS: Ubuntu 22.04
- Python: 3.11
- Docker Engine: 
- Docker Compose: 2.33
- Browser: Chrome

Anything else?

By the way, the current log of scan only show 1 command per steps of the scan,for eg.

sort -u /home/rengine/scan_results/domain.net/scans/8ac36e99-8125-11ef-9a4a-9b45a032b0f2/urls_unfurled.txt -o /home/rengine/scan_results/domain.net/scans/8ac36e99-8125-11ef-9a4a-9b45a032b0f2/urls_unfurled.txt

It will better for debugging if we have a way to show full command had been run on the scan AND keep all the tempt files, for eg. "urls_unfurled.txt". Maybe we should add "Debug_Mode" in the configure file

Acknowledgements

  • This issue is not a duplicate of an existing bug report.
  • I have chosen an appropriate title.
  • All requested information has been provided properly.
@haryisharry haryisharry added the bug Something isn't working label Oct 14, 2024
@psyray psyray added this to the v2.2.0 release milestone Nov 9, 2024
@psyray
Copy link
Contributor

psyray commented Nov 29, 2024

Hi, could you test the 2.1.1 branch and make feedback about this issue.

It should be resolved with #238

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

2 participants