# CVE-2024-22412: ClickHouse's Role-based Access Control is bypassed when query caching is enabled.

> Attackers with role control can bypass access controls and read unauthorized data when query caching is enabled in ClickHouse.

- **Severity:** Low 2.4 (`CVSS:3.1/AV:A/AC:L/PR:H/UI:N/S:U/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 18 Mar 2024
- **Updated:** 1 Aug 2024
- **Also known as:** DEBIAN-CVE-2024-22412, ECHO-322b-5717-8504, GHSA-45h5-f7g3-gr8r, UBUNTU-CVE-2024-22412

## What is CVE-2024-22412?

CVE-2024-22412 is a low-severity missing authorization vulnerability in ClickHouse, published on 18 Mar 2024. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

ClickHouse is an open-source column-oriented database management system. A bug exists in the cloud ClickHouse offering prior to version 24.0.2.54535 and in github.com/clickhouse/clickhouse version 23.1. Query caching bypasses the role based access controls and the policies being enforced on roles. In affected versions, the query cache only respects separate users, however this is not documented and not expected behavior. People relying on ClickHouse roles can have their access control lists bypassed if they are using query caching. Attackers who have control of a role could guess queries and see data they shouldn't have access to. Version 24.1 of ClickHouse and version 24.0.2.54535 of ClickHouse Cloud contain a patch for this issue. Based on the documentation, role based access control should be enforced regardless if query caching is enabled or not.

Weakness: CWE-863 (Incorrect Authorization)

## Which versions are affected by CVE-2024-22412?

It affects 2 products.


Products: Clickhouse Clickhouse, Clickhouse Clickhouse Cloud.

## How do I fix CVE-2024-22412?

No fix has been published for CVE-2024-22412 yet. Limit exposure of the affected software until one is available.

## Is CVE-2024-22412 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-22412 exists.

## Other vulnerabilities in ClickHouse

- [CVE-2019-16535](https://insights.sbomify.com/CVE-2019-16535/): Memory corruption in ClickHouse (critical 9.8)
- [CVE-2018-14670](https://insights.sbomify.com/CVE-2018-14670/): Missing authorization in ClickHouse (critical 9.8)
- [CVE-2018-14671](https://insights.sbomify.com/CVE-2018-14671/): Code injection in ClickHouse (critical 9.8)
- [CVE-2021-43304](https://insights.sbomify.com/CVE-2021-43304/): Memory corruption in clickhouse (high 8.8)
- [CVE-2021-43305](https://insights.sbomify.com/CVE-2021-43305/): Memory corruption in clickhouse (high 8.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-22412 and fix it if it is affected.

What it is: CVE-2024-22412 is a low-severity missing authorization vulnerability in ClickHouse, published on 18 Mar 2024. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-22412 exists.

Affected product: ClickHouse. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2024-22412/ (Markdown: https://insights.sbomify.com/CVE-2024-22412/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2024-22412
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-22412
- OSV: https://osv.dev/vulnerability/CVE-2024-22412

---
From sbomify Insights: https://insights.sbomify.com/CVE-2024-22412/
Summaries are generated and may contain mistakes; the official description above is the record.