Bug 1645201 (CVE-2018-16861) - CVE-2018-16861 foreman: stored XSS in success notification after entity creation
Summary: CVE-2018-16861 foreman: stored XSS in success notification after entity creation
Keywords:
Status: CLOSED ERRATA
Alias: CVE-2018-16861
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Red Hat Product Security
QA Contact:
URL:
Whiteboard:
: 1645208 (view as bug list)
Depends On: 1652785
Blocks: 1637732 1640755
TreeView+ depends on / blocked
 
Reported: 2018-11-01 15:42 UTC by Laura Pardo
Modified: 2021-02-16 22:50 UTC (History)
9 users (show)

Fixed In Version: foreman 1.18.3, foreman 1.19.1, foreman 1.20.0
Clone Of:
Environment:
Last Closed: 2019-06-10 10:41:38 UTC
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2019:1222 0 None None None 2019-05-14 12:36:16 UTC

Description Laura Pardo 2018-11-01 15:42:03 UTC 
A flaw was found in foreman before versions 1.18.3, 1.19.1, 1.20.0. An stored XSS in the entity creation field.


References:
https://projects.theforeman.org/issues/24807

Upstream Patches:
https://github.com/theforeman/foreman/pull/6060
https://github.com/theforeman/foreman/pull/6041
Comment 1 Laura Pardo 2018-11-01 15:42:15 UTC 
Acknowledgments:

Name: Sanket Jagtap (Red Hat Pune India)
Comment 7 Richard Maciel Costa 2018-12-04 21:21:08 UTC 
*** Bug 1645208 has been marked as a duplicate of this bug. ***
Comment 8 Richard Maciel Costa 2018-12-04 21:22:50 UTC 
Note job invocation uses the same code to generate a toast message when successfully creating the job, hence that's another vector for exploiting this issue. That's the reason for Bug #1645208 being marked as duplicate as this one.
Comment 9 errata-xmlrpc 2019-05-14 12:36:15 UTC 
This issue has been addressed in the following products:

  Red Hat Satellite 6.5 for RHEL 7

Via RHSA-2019:1222 https://access.redhat.com/errata/RHSA-2019:1222
Note You need to log in before you can comment on or make changes to this bug.