Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 1364389 - (CVE-2016-1000220) CVE-2016-1000220 kibana: XSS vulnerability ESA-2016-03
CVE-2016-1000220 kibana: XSS vulnerability ESA-2016-03
Status: CLOSED ERRATA
Product: Security Response
Classification: Other
Component: vulnerability (Show other bugs)
unspecified
All Linux
medium Severity medium
: ---
: ---
Assigned To: Red Hat Product Security
impact=moderate,public=20160803,repor...
: Security
Depends On: 1370891 1370892
Blocks: 1364395
  Show dependency treegraph
 
Reported: 2016-08-05 05:11 EDT by Adam Mariš
Modified: 2016-09-09 12:22 EDT (History)
29 users (show)

See Also:
Fixed In Version: kibana 4.5.4, kibana 4.1.11
Doc Type: If docs needed, set a value
Doc Text:
A cross-site scripting (XSS) flaw was found in Kibana. A remote attacker could use this flaw to inject arbitrary web script into pages served to other users.
Story Points: ---
Clone Of:
Environment:
Last Closed: 2016-09-08 17:57:38 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)


External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2016:1836 normal SHIPPED_LIVE Moderate: Red Hat OpenShift Enterprise Kibana security update 2016-09-08 16:22:07 EDT

  None (edit)
Description Adam Mariš 2016-08-05 05:11:00 EDT
It was reported that versions of Kibana before 4.5.4 and 4.1.11 are vulnerable to an XSS attack that would allow an attacker to execute arbitrary JavaScript in users' browsers.

External Reference:

https://www.elastic.co/community/security
Comment 4 errata-xmlrpc 2016-09-08 12:23:25 EDT
This issue has been addressed in the following products:

  Red Hat OpenShift Enterprise 3.2
  Red Hat OpenShift Enterprise 3.1

Via RHSA-2016:1836 https://access.redhat.com/errata/RHSA-2016:1836

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