> For the complete documentation index, see [llms.txt](https://docs.deepconverse.com/product-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.deepconverse.com/product-docs/security/reporting-security-vulnerabilities/log4shell-vulnerability.md).

# Log4Shell Vulnerability

A security vulnerability affecting the Java logging framework Log4j was publicly disclosed in December 2021

DeepConverse platform does not use Java technology for our core services, and as a result, our services are not impacted by the Log4Shell vulnerability.

We tested our systems for external exploitability of the vulnerability to identify possible attack vectors. We patched our logging infrastructure, and updated them accordingly based on the recommended guidance from Elastic and AWS.

Additional controls are also being employed to mitigate the risk. We are monitoring abnormal patterns in DeepConverse inbound and outbound traffic, and activating new web application firewall (WAF) rules and blocking suspicious IPs.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.deepconverse.com/product-docs/security/reporting-security-vulnerabilities/log4shell-vulnerability.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.
