DevOps Articles

Logit.io Log4Shell Security Update

Learn how Logit.io responded to the CVE-2021-4422 and CVE-2021-45046 security vulnerability This blog post provides a summary of CVE-2021-44228 and CVE-2021-45046 and provides details of the steps that have been taken by Logit.io to mitigate the exploitation of the vulnerability. Please be aware that Apache is publishing https://logging.apache.org/log4j/2.x/security.html# that should also be considered by your security teams.

Logit.io Log4J2 Security Update (CVE-2021-44228 & CVE-2021-45046)

Our teams responded with the highest priority to vulnerability CVE-2021-44228 that was impacting multiple versions of the Apache Log4j2, these are the steps taken by our teams: Logit.io engineers and security incident teams proceeded to actively analyse, identify and where necessary patch all affected log4j2 versions across all Logit.io Logstash and Elasticsearch instances.