Bug 1471262 (CVE-2017-7538) - CVE-2017-7538 Satellite 5: organization name allows XSS
Summary: CVE-2017-7538 Satellite 5: organization name allows XSS
Keywords:
Status: CLOSED ERRATA
Alias: CVE-2017-7538
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: impact=moderate,public=20170714,repor...
Depends On: 1460208 1471263
Blocks: 1471265
TreeView+ depends on / blocked
 
Reported: 2017-07-14 20:42 UTC by Kurt Seifried
Modified: 2019-06-08 22:07 UTC (History)
6 users (show)

Fixed In Version: rhn_satellite 5.8
Doc Type: If docs needed, set a value
Doc Text:
A cross-site scripting (XSS) flaw was found in how an organization name is displayed in Satellite 5. A user able to change an organization's name could exploit this flaw to perform XSS attacks against other Satellite users.
Clone Of:
Environment:
Last Closed: 2017-09-14 09:12:54 UTC


Attachments (Terms of Use)


Links
System ID Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2017:2645 normal SHIPPED_LIVE Moderate: satellite and spacewalk security and bug fix update 2017-09-06 16:26:43 UTC

Description Kurt Seifried 2017-07-14 20:42:29 UTC
Ales Dujicek of Red Hat reports:
The organization name is used in a variety of web pages without being sanitized for HTML special characters, resulting in a stored cross site scripting (XSS) vulnerability.

Comment 1 Kurt Seifried 2017-07-14 20:42:40 UTC
Acknowledgments:

Name: Ales Dujicek (Red Hat)

Comment 4 errata-xmlrpc 2017-09-06 12:28:42 UTC
This issue has been addressed in the following products:

  Red Hat Satellite 5.8
  Red Hat Satellite 5.8 ELS

Via RHSA-2017:2645 https://access.redhat.com/errata/RHSA-2017:2645

Comment 5 Tomas Lestach 2017-09-14 08:16:17 UTC
Can this BZ be closed? The associated erratum went live on 2017-09-06

Comment 6 Andrej Nemec 2017-09-14 09:12:54 UTC
(In reply to Tomas Lestach from comment #5)
> Can this BZ be closed? The associated erratum went live on 2017-09-06

This is fine to close, thanks!


Note You need to log in before you can comment on or make changes to this bug.