# Needed info on Kibana cross site scripting issue (ESA-2017-22)

**URL:** <https://discuss.elastic.co/t/needed-info-on-kibana-cross-site-scripting-issue-esa-2017-22/111917>\
**Category:** Kibana\
**Created:** [December 15, 2017, 7:33am UTC](https://discuss.elastic.co/t/needed-info-on-kibana-cross-site-scripting-issue-esa-2017-22/111917 "2017-12-15T07:33:35Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![SKumarMN](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/skumarmn/32/27537_2.png) [@SKumarMN](https://discuss.elastic.co/u/SKumarMN)\
**Post date:** [December 15, 2017, 7:33am UTC](https://discuss.elastic.co/t/needed-info-on-kibana-cross-site-scripting-issue-esa-2017-22/111917/1 "2017-12-15T07:33:35Z")

</div>

Hi,

Hi I am currently using Kibana 5.6.4 and As mentioned in the security announcements , it seems this issue is not present in 5.6.5. I tried to search in github what was the fix made or under what bug was this issue tracked. I couldn't get that info. Could you please help me to find the git issue number/commit id associated with this issue. Similarly how do i find what under which git issue /commits a particular SV reported in [https://www.elastic.co/community/security](https://www.elastic.co/community/security) is tracked/ fixed.

---

<div class="post-metadata">

**Author:** ![SKumarMN](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/skumarmn/32/27537_2.png) [@SKumarMN](https://discuss.elastic.co/u/SKumarMN)\
**Post date:** [December 15, 2017, 10:26am UTC](https://discuss.elastic.co/t/needed-info-on-kibana-cross-site-scripting-issue-esa-2017-22/111917/2 "2017-12-15T10:26:01Z")

</div>

@joshbressers Could you please assist in this

---

<div class="post-metadata">

**Author:** ![Christian\_Dahlqvist](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/christian_dahlqvist/32/4617_2.png) [@Christian\_Dahlqvist](https://discuss.elastic.co/u/Christian_Dahlqvist)\
**Post date:** [December 15, 2017, 10:41am UTC](https://discuss.elastic.co/t/needed-info-on-kibana-cross-site-scripting-issue-esa-2017-22/111917/3 "2017-12-15T10:41:32Z")

</div>

@SKumarMN Please read [this](https://discuss.elastic.co/t/about-the-elasticsearch-category/21), especially the "Also be patient" part.

This forum is manned by volunteers, so please be patient and do not ping anyone not already involved in the thread.

---

<div class="post-metadata">

**Author:** ![timroes](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/timroes/32/19712_2.png) [@timroes](https://discuss.elastic.co/u/timroes)\
**Post date:** [December 15, 2017, 4:10pm UTC](https://discuss.elastic.co/t/needed-info-on-kibana-cross-site-scripting-issue-esa-2017-22/111917/4 "2017-12-15T16:10:04Z")

</div>

Hello,

the PR, that fixes ESA-2017-22 is [#14994](https://github.com/elastic/kibana/pull/14994).

How to find them: we usually try to add the "ESA" number to the PR, once it's disclosed, so that you should be able to search for them on GitHub. This one didn't had it so I just added it.

Cheers,  
Tim

---

<div class="post-metadata">

**Author:** ![SKumarMN](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/skumarmn/32/27537_2.png) [@SKumarMN](https://discuss.elastic.co/u/SKumarMN)\
**Post date:** [December 16, 2017, 5:14am UTC](https://discuss.elastic.co/t/needed-info-on-kibana-cross-site-scripting-issue-esa-2017-22/111917/5 "2017-12-16T05:14:35Z")

</div>

Thanks @timroes . Also When i search for "ESA-2017" text in issues list i see just the three occurrences. Seems like many PR's are not associated with SV numbers..

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [January 13, 2018, 5:14am UTC](https://discuss.elastic.co/t/needed-info-on-kibana-cross-site-scripting-issue-esa-2017-22/111917/6 "2018-01-13T05:14:40Z")

</div>

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.
