# CVE-2024-36543: STRIMZI incorrect access control

> Attackers can bypass access controls in Kafka Connect to deny service, mirror data, or steal SASL credentials via the MirrorMaker REST API.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 17 Jun 2024
- **Updated:** 9 Jul 2026
- **Also known as:** GHSA-q2xx-f8r3-9mg5

## What is CVE-2024-36543?

CVE-2024-36543 is a critical missing authorization vulnerability in n/a, published on 17 Jun 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Incorrect access control in the Kafka Connect REST API in the STRIMZI Project 0.41.0 and earlier allows an attacker to deny the service for Kafka Mirroring, potentially mirror the topics' content to his Kafka cluster via a malicious connector (bypassing Kafka ACL if it exists), and potentially steal Kafka SASL credentials, by querying the MirrorMaker Kafka REST API.

Weakness: CWE-400 (Uncontrolled Resource Consumption)

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

2 open source packages ship an affected version, including io.strimzi:strimzi.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `io.strimzi:strimzi` | Maven | All versions to 0.41.0 | None |
| `io.strimzi:strimzi` | Maven | All versions to 0.41.0 | None |

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

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

## Is CVE-2024-36543 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2024-36543 is a critical missing authorization vulnerability in n/a, published on 17 Jun 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-36543 exists.

Affected packages and fixed versions:
- io.strimzi:strimzi (Maven): affected all versions up to 0.41.0; no fix listed
- io.strimzi:strimzi (Maven): affected all versions up to 0.41.0; no fix listed

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-36543/ (Markdown: https://insights.sbomify.com/CVE-2024-36543/index.md)
```

## Sources

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

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