# WebNMS security vulnerability

**URL:** <https://discuss.elastic.co/t/webnms-security-vulnerability/316766>\
**Category:** Elasticsearch\
**Created:** [October 17, 2022, 11:05am UTC](https://discuss.elastic.co/t/webnms-security-vulnerability/316766 "2022-10-17T11:05:13Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![aligege123](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/aligege123/32/112146_2.png) [@aligege123](https://discuss.elastic.co/u/aligege123)\
**Post date:** [October 17, 2022, 11:05am UTC](https://discuss.elastic.co/t/webnms-security-vulnerability/316766/1 "2022-10-17T11:05:13Z")

</div>

Is elasticsearch related with ZOHO webNMS ? I recently meet a vulnerability report from es http server port 9200 about webNMS. The vulnerability detail: [CVE - CVE-2016-6600 (mitre.org)](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-6600)

My elasticsearch version is 7.6.1. I don't hava any clue about this vulnerability, or may be it's just a wrong report. Any help will be appreciated.

---

<div class="post-metadata">

**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\
**Post date:** [October 17, 2022, 10:24pm UTC](https://discuss.elastic.co/t/webnms-security-vulnerability/316766/2 "2022-10-17T22:24:55Z")

</div>

It's possible that webnms integrates with Elasticsearch, but that's not something that we maintain.

---

<div class="post-metadata">

**Author:** ![Yang\_Wang](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/yang_wang/32/48857_2.png) [@Yang\_Wang](https://discuss.elastic.co/u/Yang_Wang)\
**Post date:** [October 17, 2022, 11:33pm UTC](https://discuss.elastic.co/t/webnms-security-vulnerability/316766/3 "2022-10-17T23:33:25Z")

</div>

@aligege123 I believe what @warkolm said is correct. But if you have any concerns, we have a dedicated channel for security vulnerability related report and I encourage you to use it. Elastic's security reporting guidelines are available at [Security issues | Elastic](https://www.elastic.co/community/security). Per those guidelines, all reports of potential security issues or vulnerabilities should be sent via email to [security@elastic.co](mailto:security@elastic.co).

---

<div class="post-metadata">

**Author:** ![aligege123](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/aligege123/32/112146_2.png) [@aligege123](https://discuss.elastic.co/u/aligege123)\
**Post date:** [October 18, 2022, 1:19am UTC](https://discuss.elastic.co/t/webnms-security-vulnerability/316766/4 "2022-10-18T01:19:18Z")

</div>

Oh, I see, thanks very much!

---

<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:** [November 15, 2022, 1:19am UTC](https://discuss.elastic.co/t/webnms-security-vulnerability/316766/5 "2022-11-15T01:19:38Z")

</div>

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