Aristotle Metadata Log4J Vulnerability report

Summary: Aristotle Metadata has been made aware of the Log4Shell (CVE-2021-44228) vulnerability and has taken all mitigating steps to protect against this vulnerability.

Log4Shell (CVE-2021-44228) is a zero-day vulnerability in Log4j, a popular Java logging framework, that is currently impacting web services worldwide.

Aristotle Metadata DevOps staff first became aware of the Log4Shell vulnerability on 10 December 2021 when this vulnerability was first published to the information security community.

Aristotle Metadata staff have performed an analysis of our system architecture and have identified AWS OpenSearch as our only infrastructure system current deployed based on or using the Java framework. No other Aristotle Metadata services are developed using the Java framework. Additionally, all other services are developing using containerised platforms using minimal operating systems to lower the security profile and reduce the risk of security threat.

Aristotle Metadata staff have also assessed the level of risk and exposure the Log4Shell vulnerability and believe that the Log4Shell vulnerability presents a low risk for our clients. Aristotle Metadata uses the AWS OpenSearch for rich-text search features for metadata content of the Aristotle Metadata Registry, and all AWS OpenSearch systems are controlled with virtual private networks that restrict all outgoing traffic from AWS OpenSearch services to the wider internet. Additionally, all search services operate on separate infrastructure to authentication data, and as such no personally identifying information was at risk of exposure.

Aristotle Metadata store all network logs using the AWS CloudWatch service in isolated have investigated network traffic and have identified no traffic that indicates the Log4Shell exploit has been utilised on any Aristotle Metadata services. Additionally, analysis from Elastic.co engineers has shown that the Log4Shell vulnerability is not exploitable to extract indexed data in an Elasticsearch instance, and as such no Aristotle Metadata client information was at risk of exfiltration due to this vulnerability.

As a client of Amazon Web Services (AWS), Aristotle Metadata inherits many of the protections of the AWS Shared Responsibility Model. One of these protections is the availability of “hotpatches”, bug fixes and security updates for AWS services – including AWS OpenSearch. On 13 December 2021, Amazon Web Services made security updates available for the Log4Shell vulnerability for all appropriate AWS Services, including AWS OpenSearch. Aristotle Metadata has taken all reasonable steps to implement these infrastructure and network updates for all clients.

Aristotle Metadata is proud to provide services to academic and government clients globally, and are dedicated to the ongoing security of our infrastructure for all clients.

Aristotle DevOps Team

Aristotle Marketing Team

Other articles you might enjoy

Uncategorized
Aristotle Marketing Team

Bridging the Skills Gap in Healthcare Data: Why Training Needs to Catch Up

Australia’s healthcare sector is swimming in data, but struggling to staff it. From digitised records to AI-assisted diagnostics, the systems are there. What’s missing is a steady pipeline of people trained to manage, govern and actually use that data safely. Right now, most clinical and operational staff aren’t taught the

Read More »
Uncategorized
Aristotle Marketing Team

Beyond Compliance: How Healthcare Teams Can Build a Better Data Culture

The frameworks that govern clinical information,  HL7, ICD-10, SNOMED, matter. But they’re only one part of what makes data usable, safe, and trustworthy. Compliance doesn’t cover everything. Especially when your organisation’s data is spread across dozens of systems that fall outside the usual health informatics scope. Staffing tools, research portals,

Read More »
Uncategorized
Aristotle Marketing Team

80% of Your Data Team’s Time Is Wasted: It’s Time to Fix That

Data teams are hired to solve problems, build models, and unlock insights. But in most organisations, that’s not where they’re spending their time. Too often, they’re stuck cleaning up messes, chasing down missing files, reconciling inconsistent sources, and piecing together context that should have been documented right from the start.

Read More »
Uncategorized
Aristotle Marketing Team

Why Most Metadata Tools Stop Short (and What to Do About It)

Metadata tools have become table stakes for organisations that care about data governance. But here’s the problem: most of them only work on the systems you already know about. And if your metadata strategy only sees what’s already documented, you’re not managing your data, you’re managing an illusion of it.

Read More »
Uncategorized
Aristotle Marketing Team

Do You Know Where All Your Data Is? The Hidden Risks of Shadow Data

At first glance, it’s easy to assume you’ve got a handle on your organisation’s data landscape. You know what’s in your CRM. You know what’s flowing through your data warehouse. You’ve got dashboards full of KPIs. But what about the LinkedIn engagement metrics sitting in your marketing team’s spreadsheets? Or

Read More »