Log4j vulnerability threat impact on Elasticsearch 2.3.4 and Logstash 2.3.4

Can any one please provide information on Log4j vulnerability threat impact on Elasticsearch 2.3.4 and Logstash 2.3.4. These are very old versions. If any resolution possible without upgrading the stack.

Please don't post the same topic more than once, it makes it much harder for people to help you :slight_smile: