-
-
Notifications
You must be signed in to change notification settings - Fork 34
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
Tab characters in the Vulnerability Name cause Vulnerability Findings area to become non-responsive #75
Comments
Try the newest release 1.3.26 and let me know if the issue persists. |
Hi there, Many thanks for the prompt response. I've updated to the latest release.
Again, many thanks for the assistance thus far. |
* allow for optional reporting features * add additional jars to process reports * bug fix for #75
I think we got it everywhere now :) ... @gKelsoCsiro see if 1.3.27 fixes this last issue. |
Thanks for testing. I'll be trying to reproduce and get back to you. |
I'm still unable to recreate this on the updated versions. Have you tried clearing cache? Hoping it's just the old javascript causing issues. |
Excellent suggestion on purging the Cache. I should have thought of that before re-testing last time. In short: Fixed. Many thanks and much Kudos. |
Description:
The TAB character breaks the finding page when it's used as part of a Vulnerabilities name. This was found when copying a finding name from a MS Word template directly in.
POC:
The following POST data when sent to http://localhost:9000/portal/updateVulnerability will cause the issue.
vulnid=12&title=This is a Test asdf&_token=75779572-290f-4d62-a0cf-7011e4b59fe7
Screenshot:
The screenshot above shows the "You appear offline" popup and prevents interaction with the web browser.
Current work arounds:
Further details:
Commit hash: 137d9fa
Branch name: main
Date of checkout: 10/10/2024 - AEST (Australian Eastern Standard Time)
Other:
Have tested using a container image hosted on *nix and Windows environments.
Testing has confirmed issue in Ms Edge and Chromium.
The text was updated successfully, but these errors were encountered: