> For the complete documentation index, see [llms.txt](https://doc.engenius.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://doc.engenius.ai/engenius-cloud-esp/security-advisories/apache-log4j-library-vulnerability.md).
# Apache log4j library vulnerability
## Overview
On December 9th, 2021, a vulnerability in certain versions of the Apache log4j library was disclosed. Products utilizing this library are susceptible to remote code execution vulnerability, where a remote attacker can leverage this vulnerability to gain full control of the impacted device. More details can be found at [NIST](https://nvd.nist.gov/vuln/detail/CVE-2021-44228).
## Details
Since the discovery of this vulnerability, EnGenius Research Center has been closely monitoring this threat and how it may affect EnGenius products. Only few EnGenius cloud services use the log4j library, none of them use it in a way that makes them vulnerable to CVE-2021-44228. The conclusion of the investigation is that the products listed below under the Unaffected Products section are not vulnerable to CVE-2021-44228. If new information is discovered, this advisory will be updated.
## Affected Products
* ezWifiPlanner service
Although ezWifiPlanner does not enable any JNDI and LDAP features that cause the vulnerability, we still upgraded relative log4j libraries to ensure the safety.
## Unaffected Products
* EnGenius Cloud
* ezMaster
* EnSky
* EWS Access Points
* EWS Ethernet Switchs
* ECW Access Points
* ECS Ethernet Switches
* ENH Access Points
* ENS Access Points
* EnStation Access Points
* EMR Routers
* ESR Routers
* All EnGenius Mobile Apps
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://doc.engenius.ai/engenius-cloud-esp/security-advisories/apache-log4j-library-vulnerability.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.