Bug #24807
closed
CVE-2018-16861 - toast notification sends strings through as HTML
Added by Chris Duryee over 6 years ago.
Updated about 6 years ago.
Found in Releases:
1.16.0,
1.16.0-RC1,
1.16.0-RC2,
1.16.1,
1.16.2,
1.17.0,
1.17.0-RC1,
1.17.0-RC2,
1.17.1,
1.17.2,
1.17.3,
1.17.4,
1.18.0,
1.18.0-RC1,
1.18.0-RC2,
1.18.0-RC3,
1.18.1,
1.18.2,
1.19.0,
1.19.0-RC1,
1.19.0-RC2,
1.19.0-RC3
|
Description
If you call `Notification.setErrorMessage()` with a string that contains `<` and `>`, the string will get sent through to the browser and the browser will attempt to render it as HTML.
For example, it's possible to get Pulp to raise an error message like "The configuration parameter <foo> is not valid". This will display in the browser as "The configuration parameter is not valid".
It would be better if the notification escaped these strings so the "<>" is not lost.
- Category set to Security
- Assignee set to Avi Sharvit
- Priority changed from Normal to High
- Found in Releases 1.16.0, 1.16.0-RC1, 1.16.0-RC2, 1.16.1, 1.16.2, 1.17.0, 1.17.0-RC1, 1.17.0-RC2, 1.17.1, 1.17.2, 1.17.3, 1.17.4, 1.18.0, 1.18.0-RC1, 1.18.0-RC2, 1.18.0-RC3, 1.18.1, 1.18.2, 1.19.0, 1.19.0-RC1, 1.19.0-RC2, 1.19.0-RC3 added
- Status changed from New to Ready For Testing
- Pull request https://github.com/theforeman/foreman/pull/6041 added
- Fixed in Releases 1.19.1, 1.20.0 added
Foreman core helpers already escape messages before passing them on to the notifications, and therefor this isn't a significant risk of XSS here, but we fixed it just to be on the safe side.
- Status changed from Ready For Testing to Closed
- Pull request https://github.com/theforeman/foreman/pull/6060 added
- Fixed in Releases 1.18.3 added
- Related to Bug #25230: compute resource test connection is html incorrectly escaped added
- Bugzilla link set to 1652785
- Subject changed from toast notification sends strings through as HTML to CVE-2018-16861 - toast notification sends strings through as HTML
Also available in: Atom
PDF