> For the complete documentation index, see [llms.txt](https://docs.onyxia.sh/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.onyxia.sh/vulnerability-disclosure/known-vulnerabilities/cve-2024-56333.md).

# CVE-2024-56333

This vulnerability is critical.

### Description

This critical vulnerability allows authenticated users to remotely execute code within the Onyxia-API, leading to potential consequences such as unauthorized access to other user environments and denial of service attacks.

### Remediation

| Patches for Major Version of the helm chart of Onyxia                                                                         |
| ----------------------------------------------------------------------------------------------------------------------------- |
| Versions 7 and below are no longer supported. Upgrade to a newer version to resolve this issue.                               |
| Version 8 is built on Onyxia API v2.x. To update, use Onyxia chart v8.27.16 and explicitly set the API tag to v2.8.2 or after |
| Version 9 is built on Onyxia API v3.x. To update, use Onyxia chart v9.2.1 and explicitly set the API tag to v3.1.1 or after   |
| Version 10 is built on Onyxia API v4.x. You can use Onyxia chart v10.4.0 and after.                                           |

### Details

For version 8 and 9 you need to modify the \`values.yaml\`

{% code title="values-v9.yaml" %}

```yaml
  api:
    image:
      tag: "v3.1.1"
```

{% endcode %}

{% code title="values-v8.yaml" %}

```yaml
  api:
    image:
      tag: "v2.8.2"
```

{% endcode %}


---

# 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://docs.onyxia.sh/vulnerability-disclosure/known-vulnerabilities/cve-2024-56333.md?ask=<question>&goal=<user_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.