Bug 1728574 (CVE-2018-17146) - CVE-2018-17146 Nagios-XI: cross-site scripting via 'name' parameter in Account Information page
Summary: CVE-2018-17146 Nagios-XI: cross-site scripting via 'name' parameter in Accou...
Keywords:
Status: CLOSED NOTABUG
Alias: CVE-2018-17146
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:
Depends On: 1728575 1728576
Blocks: 1728577
TreeView+ depends on / blocked
 
Reported: 2019-07-10 07:45 UTC by Dhananjay Arunesh
Modified: 2021-02-16 21:44 UTC (History)
14 users (show)

Fixed In Version: nagios 5.5.4
Clone Of:
Environment:
Last Closed: 2019-07-11 19:03:42 UTC
Embargoed:


Attachments (Terms of Use)

Description Dhananjay Arunesh 2019-07-10 07:45:31 UTC
A cross-site scripting vulnerability exists in Nagios XI before 5.5.4 via the 'name' parameter within the Account Information page. Exploitation of this vulnerability allows an attacker to execute arbitrary JavaScript code within the auto login admin management page.

Reference:
https://assets.nagios.com/downloads/nagiosxi/CHANGES-5.TXT

Comment 1 Dhananjay Arunesh 2019-07-10 07:46:29 UTC
Created nagios tracking bugs for this issue:

Affects: epel-all [bug 1728576]
Affects: fedora-all [bug 1728575]

Comment 2 Scott Wilkerson 2019-07-11 19:03:42 UTC
This was for Nagios XI not nagios core.

Nagios XI is not distributed via epel, fedora or anything you have created all these bug for.

Comment 3 Hardik Vyas 2019-07-12 07:10:34 UTC
Latest upstream release shipped for Nagios core is 4.4.3(and the flaw says fixed in 5.5.4 i.e for Nagios XI), XI[1] is a commercial thing with is not included in any Red Hat offerings.

Closing out fedora and epel trackers as NOTABUG.

[1] https://www.nagios.com/products/nagios-xi/

Comment 4 Hardik Vyas 2019-07-12 07:10:36 UTC
Statement:

This issue did not affect Red Hat Gluster Storage 3 as it does not ship Nagios XI.


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