CVE-2024-36543: Incorrect access control in the Kafka Connect REST API in the STRIMZI Project 0.41.0 and earlier allows an...
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.
Security readout for executives and security teams
Plain-English summary
This issue affects Strimzi deployments using Kafka MirrorMaker/Kafka Connect REST APIs in version 0.41.0 and earlier. Weak access control could let an unauthenticated network attacker disrupt Kafka mirroring, copy mirrored topic data to another Kafka cluster, or expose Kafka SASL credentials.
Executive priority
Treat as urgent for exposed Strimzi MirrorMaker environments because the described impact includes service disruption, data exposure, and credential theft. Prioritize internet-facing or broadly reachable REST APIs first.
Technical view
CVE-2024-36543 is an incorrect access control flaw in the Kafka Connect REST API in Strimzi Project 0.41.0 and earlier. The CVE describes network, low-complexity, no-auth exploitation with potential confidentiality, integrity, and availability impact through MirrorMaker Kafka REST API access.
Likely exposure
Organizations using Strimzi 0.41.0 or earlier with Kafka MirrorMaker or Kafka Connect REST interfaces reachable by untrusted networks are the clearest exposure group. Evidence does not define affected CPEs.
Exploitation context
The CVE is not listed as KEV in the provided bundle, and no cited source confirms active exploitation. A public research reference exists, but the bundle does not establish real-world exploitation.
Researcher notes
The strongest evidence is the CVE description and CVSS 9.8 vector. The bundle does not name a fixed release, vendor advisory, CPEs, or confirmed exploitation. Avoid assuming affected products beyond Strimzi 0.41.0 and earlier.
Mitigation direction
Inventory Strimzi deployments and identify versions 0.41.0 or earlier.
Restrict Kafka Connect and MirrorMaker REST API access to trusted administrative networks.
Review Strimzi project guidance for fixed versions or official mitigations.
Rotate Kafka SASL credentials if unauthorized REST API access is suspected.
Audit connector configurations for unauthorized mirroring destinations.
Validation and detection
Confirm whether any Strimzi deployment runs version 0.41.0 or earlier.
Check whether Kafka Connect or MirrorMaker REST APIs are externally reachable.
Review connector inventory for unexpected or unauthorized connector definitions.
Inspect logs for suspicious REST API access or connector changes.
Verify Kafka ACLs do not substitute for REST API authorization controls.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · low confidence lookup
CWE-400: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
1CVSS vectors
3Timeline events
2ADP providers
2Source links
SSVC decision data
CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: pocAutomatable: yesTechnical Impact: total
CVSS vector scores
1 official score
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-400 · source CWE mapping
Uncontrolled Resource Consumption
Uncontrolled Resource Consumption represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.