You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It is possible to inject HTML through exception stack messages and stack traces displayed in system error messages. The developer of an application is likely not to take this into account and may inadvertently introduce XSS vulnerabilities in applications through this mechanism.
Another path to exploit this is to convince the end user to paste text that will fail field validation and injects HTML/javascript.
It should be noted that the UserError class now provides separate text and HTML modes for messages. Previously, the text mode permitted HTML even though the documentation specified that the message should be plain text only.
Applications relying on the previous functionality should change to use the CONTENT_XHTML mode instead of the default CONTENT_TEXT mode.
Furthermore, subclasses of InvalidValueException can override getHtmlMessage() to bypass the default escaping of messages.
Originally by @hesara
It is possible to inject HTML through exception stack messages and stack traces displayed in system error messages. The developer of an application is likely not to take this into account and may inadvertently introduce XSS vulnerabilities in applications through this mechanism.
Another path to exploit this is to convince the end user to paste text that will fail field validation and injects HTML/javascript.
This vulnerability was discovered by Wouter Coekaerts (http://wouter.coekaerts.be).
Imported from https://dev.vaadin.com/ issue #7671
The text was updated successfully, but these errors were encountered: