You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Keep in mind that in Amsterdam we currently only have an Elastic cluster running version 6 at our disposal. So if this package needs to be updated in the python code we need to check if we can also update the elastic cluster in Amsterdam. This is something we currently do not have under our own control.
Activity
bartjkdp commentedon Oct 25, 2021
I agree we should update the Elasticsearch 7.x. Updating the Elasticsearch package probably is not too much work.
vanbuiten commentedon Oct 26, 2021
Keep in mind that in Amsterdam we currently only have an Elastic cluster running version 6 at our disposal. So if this package needs to be updated in the python code we need to check if we can also update the elastic cluster in Amsterdam. This is something we currently do not have under our own control.
martijncalker commentedon Dec 10, 2021
Maybe it's time to upgrade the Elasticseach version, since Elasticsearch ships with Log4j > 2.9.0 since version 6 :)
vanbuiten commentedon Dec 13, 2021
@martijncalker for your information I found this update on the issue on the elastic discuss https://discuss.elastic.co/t/apache-log4j2-remote-code-execution-rce-vulnerability-cve-2021-44228-esa-2021-31/291476 We are looking into this.
bartjkdp commentedon Dec 13, 2021
Elasticsearch 6.8.21 released with a fix: https://www.elastic.co/guide/en/elasticsearch/reference/6.8/release-notes-6.8.21.html