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: Error creating EyeWitness screenshots with a non-standard URL #1176

Closed
1 task done
solo10010 opened this issue Jan 18, 2024 · 5 comments · Fixed by #1308
Closed
1 task done

bug: Error creating EyeWitness screenshots with a non-standard URL #1176

solo10010 opened this issue Jan 18, 2024 · 5 comments · Fixed by #1308
Assignees
Labels
bug Something isn't working release/2.1.1

Comments

@solo10010
Copy link

solo10010 commented Jan 18, 2024

Is there an existing issue for this?

  • I have searched the existing issues

Current Behavior

The task of creating screenshots stops completely if EyeWitness encounters a strange URL

python3 /usr/src/github/EyeWitness/Python/EyeWitness.py -f /usr/src/scan_results/**********.com_9/endpoints_alive.txt -d /usr/src/scan_results/* *********.com_9/screenshots --no-prompt --timeout 10 --threads 40

Scan logs.

TERM environment variable not set.
################################################## ###############################
#EyeWitness#
################################################## ###############################
# Red Siege Information Security - https://www.redsiege.com #
################################################## ###############################

ERROR: You potentially provided an mal-formed URL!
ERROR: URL is - https://account.servicenow.com/sign-in?client_id=0oapi9ote73XCWSst0x7&redirect_uri=https://account.servicenow.com/auth&response_type=code&state=/profile/home?locale=en-us&scope=openid&source_id= account&locale=en-us

Expected Behavior

I expected that if errors occurred, the collection of screenshots would continue and not be interrupted completely.

Steps To Reproduce

  1. Install the latest version of rengine
  2. Set up any scan with collection of subdomains and creation of screenshots for the servicenow.com domain
  3. Monitor scanning tasks, screenshot creation has been stopped on the account.servicenow.com subdomain

Environment

- reNgine: 2.0.2
- OS: Ubuntu 22.04.1 LTS.
- Python: 3.10.4
- Docker engine: 24.0.7
- Docker Compose: v2.23.0
- Browser: Chrome 120.0.6099.224.

Anything else?

No response

@solo10010 solo10010 added the bug Something isn't working label Jan 18, 2024
Copy link
Contributor

👋 Hi @solo10010,
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.

@AnonymousWP
Copy link
Contributor

Why didn't you fill in the template regarding versions. We can't help you if you didn't fill it correctly.

@solo10010
Copy link
Author

I'm sorry

  • rengin: 2.0.2
  • OS: Ubuntu 22.04.1 LTS.
  • Python: 3.10.4
  • Docker engine: 24.0.7
  • Docker Compose: v2.23.0
  • Browser: Chrome 120.0.6099.224.

So far I have found such a way out that the scanning of subdomains will be completed, run Further Scan Subdomain on all subdomains - screenshot

@yogeshojha
Copy link
Owner

@solo10010 The URL is malformed.

if you check the get parameters source_id= account&locale=en-us space shouldn't be there in URLs. The problem does not lie in Eyewitness itself.

@yogeshojha yogeshojha linked a pull request Jul 13, 2024 that will close this issue
@yogeshojha
Copy link
Owner

@solo10010 this will be fixed in #1308

I have added validators before storing them in file. this will prevent storing any junk http urls in a file.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working release/2.1.1
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants