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
Simplify Microsoft DNS, DHCP, and Active Directory with Micetro
Learn how Micetro makes it easy to administer Microsoft DNS, DHCP, and Active Directory sites and subnets and manage your DDI environment.
Get insight into your DDI environment with Live DDI Analytics
Enroll in our technology preview today to use the Live DDI Analytics tool to get real-time reports and analysis for your DDI environment.
Three business-focused reasons to embrace Unified DDI
Discover with BlueCat how cost optimization, risk reduction, and accelerated digital transformation offer three reasons to adopt Unified DDI.
Enhance RBAC for Microsoft DNS and DHCP servers with Micetro
Learn how easy it is to implement enhanced role-based access controls for Microsoft DNS and DHCP server environments with Micetro.