Indeni’s response to the Log4j vulnerability
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
Micetro 11.1 boosts DHCP management for Cisco Meraki SD-WAN
Learn how BlueCat Micetro 11.1 can help you overcome the limitations of Cisco Meraki SD-WAN devices to manage your distributed DHCP architecture.
BlueCat acquires LiveAction to drive network modernization and optimization
BlueCat’s acquisition of LiveAction will allow customers to expand their view beyond DNS and dive deeper into the health of their network.
Simplify NIS2 compliance with DNS management
Learn whether the EU’s NIS2 requirements apply to your organization and about how DNS management and BlueCat can boost your path to compliance.
Detect anomalies and CVE risks with Infrastructure Assurance 8.4
The Infrastructure Assurance 8.4 release features an anomaly detection engine for outliers and a CVE analysis engine to uncover device vulnerabilities.