-
Notifications
You must be signed in to change notification settings - Fork 168
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
Fixed support of the HTML tags in the description of parameters #332
base: master
Are you sure you want to change the base?
Conversation
…iously description shows HTML tags instead
Could somebody check the build? I suppose the build is somehow broken, as other pullrequests fail too and only build on windows-17 fails. I have tried clean install of windows + jdk 17 + mvn and build succeeded. I could not reproduce the error: My log around the parcel build is: |
see #341 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
From a quick glance, this looks like it would introduce XSS vulnerabilities.
you mean this change can introduce XSS? Would you please suggest better approach? |
I do not know about the source code, but the screenshots look like a standard XSS setup.
Not doing this. |
…ethod which uses Markup Formatter, that can be changed to the OWASP Markup Formatter, which renders html instead of plaintext
Maybe solved? Not sure, no one maintains this plugin anyway.
Previously description shows HTML tags instead of rendered them as HTML.
As-is
To-Be
The Input plugin itself uses default parameter rendering so it renders the description as HTML.
Testing done
I have extended as-is unit test with check of description so it contains the html tags.
Submitter checklist