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

[SECURITY] - Stored Cross-site Scripting while deleting a scan engine in the Scan Engine deletion confirmation modal box! #460

Closed
TheBinitGhimire opened this issue Aug 20, 2021 · 0 comments
Labels
Security Security related issues Work in Progress Working

Comments

@TheBinitGhimire
Copy link
Contributor

TheBinitGhimire commented Aug 20, 2021

Issue Summary

In reNgine v1.0, there is Stored Cross-site Scripting while deleting a Scan Engine in the Scan Engine deletion confirmation modal box!

Steps to Reproduce

  1. Visit your reNgine instance, and login to your account.
  2. Head over to the /scanEngine/ endpoint.
  3. Click on "Add New Engine" and write <img src=binit onerror=alert(document.location)> in the Engine name field.
  4. Now, click on the "Add Engine" button to save the changes.
  5. Click on the cross icon under the Action column, which is used for deleting the scan engine.

You will notice that, while displaying "Are you sure you want to delete {Scan_Engine_Name}?", it will render our Scan Engine Name as it is without performing any sort of sanitization, which results in our JavaScript code inside the XSS payload being executed.

This is how this vulnerability can be reproduced.

Stored Cross-site Scripting while deleting a scan engine in the Scan Engine deletion confirmation modal box!

  • I have confirmed that this issue can be reproduced as described on a latest version/pull of reNgine: yes

Technical details

  • Debian 4.19.181-1
@yogeshojha yogeshojha added Security Security related issues Work in Progress Working labels Aug 23, 2021
yogeshojha added a commit that referenced this issue Aug 23, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Security Security related issues Work in Progress Working
Projects
None yet
Development

No branches or pull requests

2 participants