Indeni’s response to the Log4j vulnerability
Notice: This blog post was originally published on Indeni before its acquisition by BlueCat.
The content reflects the expertise and perspectives of the Indeni team at the time of writing. While some references may be outdated, the insights remain valuable. For the latest updates and solutions, explore the rest of our blog
At Indeni, as in many organizations, we took immediate actions following the details emerging around CVE-2021-44228. The Log4j vulnerability has come to be known as Log4Shell. Security researchers disclosed this vulnerability on Friday Dec 10, 2021. In situations like these, we quickly identify any risks to customers and thoroughly investigate any exposure we may have ourselves.
Indeni product is running version 1.12 which does not use a Log4j version vulnerable to CVE-2021-44228. You can find the locations of the log4j logback.xml configuration files below.
Here at Indeni, we take risk and vulnerability in open-source software very seriously. If you have additional questions related to the Log4j vulnerability, please do not hesitate to contact us.
Ulrica de Fort-Menares is the Vice President of Product Management for Infrastructure Assurance.
Related content
Route traffic intelligently with DNS-based GSLB for BlueCat Edge
Discover how DNS-based GSLB with BlueCat Edge empowers networking teams to control traffic steering, reduce costs, and improve resilience.
Webinar Making APIs Work for You (Part 5)
Welcome to Part 5 of Making APIs Work for You. Our community specialist, Vivek Mistry, is your guide, and today, Vivek will focus on user security…
Exciting product update: Introducing BlueCat Integrity X
Introducing BlueCat Integrity X, a single platform for complete visibility and control over critical network services.
Article What is protective DNS (PDNS) and why is PDNS important?
Discover what protective DNS is, how it prevents cyber threats like phishing and malware, and why it’s essential for modern enterprise network security.