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: Risk of leaking the scan result files #1202

Closed
1 task done
confd0 opened this issue Feb 21, 2024 · 3 comments · Fixed by #1301
Closed
1 task done

bug: Risk of leaking the scan result files #1202

confd0 opened this issue Feb 21, 2024 · 3 comments · Fixed by #1301
Labels
bug Something isn't working Security Security related issues top-priority

Comments

@confd0
Copy link

confd0 commented Feb 21, 2024

Is there an existing issue for this?

  • I have searched the existing issues

Current Behavior

The huntr.com link for reNgine is down, and email is not responsed. so I put it here.
image

I just install reNgine v2.0.3 and find a nginx config file: https://github.com/yogeshojha/rengine/blob/f362189c9b253fd38c7c17c08e5cfc87aee0bfaf/config/nginx/rengine.conf

image

look like I can read any scan results file from other rengine site if I know the file names, and the files names can be brute force:

image

Expected Behavior

non-login user should not have privilege to read scan result files

Steps To Reproduce

brute force https://rengine_example.com/media/<domain>_<int>/subdomains_sublister.txt , change <domain> and <int> to fuzz.

Environment

- reNgine: 2.0.3
- OS: Linux
- Python: 
- Docker Engine: 
- Docker Compose: 
- Browser:

Anything else?

No response

@confd0 confd0 added the bug Something isn't working label Feb 21, 2024
Copy link
Contributor

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

@psyray psyray added the Security Security related issues label Feb 21, 2024
@psyray psyray self-assigned this Feb 21, 2024
@0xtejas
Copy link
Contributor

0xtejas commented Apr 15, 2024

Maybe x-accel-redirect from Nginx helps?

@yogeshojha
Copy link
Owner

@confd0 Excellent one, thank you for reporting this.

@0xtejas Thanks for X-Accel-Redirect

@confd0 Feel free to test these changes and let me know if you need any help disclosing this or filing CVE. Thanks

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working Security Security related issues top-priority
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants