Users of Zendesk services do not need to take any action at this time concerning the Log4j vulnerability. However, users of custom products developed under Professional Services agreements should review their agreements and validate their use of the Log4j component. It's also recommended that customers evaluate their own use of the Apache Log4j library in any custom apps or integrations and upgrade to a fixed version if a vulnerable version is identified.
The Apache Log4j vulnerability, also known as CVE-2021-44228, is a serious security flaw in the popular Java logging library, Log4j. This vulnerability allows an unauthenticated attacker to execute code on systems using this library by sending…
Zendesk has taken significant steps to mitigate the Log4j vulnerability within its products. Upon discovery, Zendesk activated its incident response process, identified all Log4j deployments, and applied vendor-provided updates or recommended…
Yes, Zendesk investigated additional Log4j vulnerabilities, specifically CVE-2021-45046 and CVE-2021-45105. A risk assessment was conducted, and actions were taken where significant risks were identified. Notably, CVE-2021-45105 is a Denial of…
For more detailed information about the Log4j vulnerability, you can refer to resources provided by the Apache Software Foundation and the National Vulnerability Database. These sources offer comprehensive insights into the nature and impact of the…