Log4J Response

On Thursday, December 9, 2021, SEDNA was made aware of a vulnerability in the Log4J logging framework. Our Engineering Team immediately worked on determining the usage of this framework and impact within our application and infrastructure.

SEDNA is not affected by the Log4Shell vulnerability as we do not use the Log4J logging library in our infrastructure. SEDNA uses the AWS Elastic Search service to power our search and immediately updated our clusters to the latest version of AWS which included their patch for the Log4J vulnerability.

We continue to monitor the situation and will provide updates should we identity any new risks or vulnerabilities.