# We getting vulnerability on ES port

**URL:** <https://discuss.elastic.co/t/we-getting-vulnerability-on-es-port/321747>\
**Category:** Elasticsearch\
**Created:** [December 21, 2022, 10:57am UTC](https://discuss.elastic.co/t/we-getting-vulnerability-on-es-port/321747 "2022-12-21T10:57:27Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![umesh1](https://avatars.discourse-cdn.com/v4/letter/u/258eb7/32.png) [@umesh1](https://discuss.elastic.co/u/umesh1)\
**Post date:** [December 21, 2022, 10:57am UTC](https://discuss.elastic.co/t/we-getting-vulnerability-on-es-port/321747/1 "2022-12-21T10:57:27Z")

</div>

We getting vulnerability on ES port which is 5200.

Plugin Output:  
The following web pages use Basic Authentication over an unencrypted  
channel :

/😕 realm=""security""

---

<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:** [December 21, 2022, 7:49pm UTC](https://discuss.elastic.co/t/we-getting-vulnerability-on-es-port/321747/2 "2022-12-21T19:49:31Z")

</div>

Do you have TLS enabled?

---

<div class="post-metadata">

**Author:** ![umesh1](https://avatars.discourse-cdn.com/v4/letter/u/258eb7/32.png) [@umesh1](https://discuss.elastic.co/u/umesh1)\
**Post date:** [December 22, 2022, 5:12am UTC](https://discuss.elastic.co/t/we-getting-vulnerability-on-es-port/321747/3 "2022-12-22T05:12:28Z")

</div>

Hi mark warkolm ,

Thanks for update. here is my cfg file.

```auto
node.name: elasticsearch_1
path.data: /opt/elasticsearch
path.logs: /var/log/elasticsearch
http.port: 5200
transport.port: 5300
path.repo: /opt/elastic_snapshot

 

cluster.name: sbiuk-dev
cluster.initial_master_nodes: ['10.191.155.181', '10.191.155.182', '10.191.155.179']
discovery.seed_hosts: ['10.191.155.181', '10.191.155.182', '10.191.155.179']
network.host: 0.0.0.0
http.host: 0.0.0.0
node.master: True
node.data: True
node.ingest: True
discovery.zen.minimum_master_nodes: 2
xpack.security.transport.ssl.enabled: true
xpack.security.transport.ssl.verification_mode: certificate
xpack.security.transport.ssl.keystore.path: elasticsearch_1.p12
xpack.security.transport.ssl.truststore.path: elasticsearch_1.p12
xpack.monitoring.collection.enabled: true
```

---

<div class="post-metadata">

**Author:** ![leandrojmp](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/leandrojmp/32/107231_2.png) [@leandrojmp](https://discuss.elastic.co/u/leandrojmp)\
**Post date:** [December 22, 2022, 1:05pm UTC](https://discuss.elastic.co/t/we-getting-vulnerability-on-es-port/321747/4 "2022-12-22T13:05:03Z")

</div>

You do not have `https` enable, you need to enable it if you want to stop receiving that vulnerability alert.

Check the [documentation](https://www.elastic.co/guide/en/elasticsearch/reference/current/security-basic-setup-https.html) for your specific version on how to configure it.

---

<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 19, 2023, 1:05pm UTC](https://discuss.elastic.co/t/we-getting-vulnerability-on-es-port/321747/5 "2023-01-19T13:05:52Z")

</div>

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