# Logstash 2.2.1 Elasticsearch Output Vulnerability
**URL:** https://discuss.elastic.co/t/logstash-2-2-1-elasticsearch-output-vulnerability/42091
**Category:** Security Announcements
**Created:** [February 18, 2016, 2:03am UTC](https://discuss.elastic.co/t/logstash-2-2-1-elasticsearch-output-vulnerability/42091 "2016-02-18T02:03:37Z")
**Posts on this page:** 2
**Page:** 1
### Author:  [@suyograo](https://discuss.elastic.co/u/suyograo)
#### Post date: [February 18, 2016, 2:03am UTC](https://discuss.elastic.co/t/logstash-2-2-1-elasticsearch-output-vulnerability/42091/1 "2016-02-18T02:03:37Z")
Logstash version 2.2.1 is vulnerable to a man in the middle attack when used with Elasticsearch output. In version 2.2.1, the config which enables SSL/TLS default has been disabled inadvertently, so a malicious user could access payload data sent via HTTP during the initial handshake. This has been fixed in 2.2.2.
User who do not wish to upgrade immediately to 2.2.2 can use https prefix in their hosts configuration. For example, replace value of `"hosts" => "found-123.com:9200"` to `"https://found-123.com:9200"`. Please restart Logstash after you make this change.
> **[Logstash 2.2.2 released with important security bug fix](https://www.elastic.co/blog/logstash-2-2-2-released)**
>
> A short post to announce that Logstash version 2.2.2 has been released today with an important security bug fix!
---
### Author:  [@system](https://discuss.elastic.co/u/system)
#### Post date: [July 6, 2017, 1:46pm UTC](https://discuss.elastic.co/t/logstash-2-2-1-elasticsearch-output-vulnerability/42091/2 "2017-07-06T13:46:26Z")