You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Path to dependency file: /persistence/build.gradle
Path to vulnerable library: /home/wss-scanner/.gradle/caches/modules-2/files-2.1/org.apache.kafka/kafka-metadata/3.6.1/568acb2c4d16ac625be067dcfb68fc75f39e76b6/kafka-metadata-3.6.1.jar
While an Apache Kafka cluster is being migrated from ZooKeeper mode to KRaft mode, in some cases ACLs will not be correctly enforced.
Two preconditions are needed to trigger the bug:
The administrator decides to remove an ACL
The resource associated with the removed ACL continues to have two or more other ACLs associated with it after the removal.
When those two preconditions are met, Kafka will treat the resource as if it had only one ACL associated with it after the removal, rather than the two or more that would be correct.
The incorrect condition is cleared by removing all brokers in ZK mode, or by adding a new ACL to the affected resource. Once the migration is completed, there is no metadata loss (the ACLs all remain).
The full impact depends on the ACLs in use. If only ALLOW ACLs were configured during the migration, the impact would be limited to availability impact. if DENY ACLs were configured, the impact could include confidentiality and integrity impact depending on the ACLs configured, as the DENY ACLs might be ignored due to this vulnerability during the migration period.
mend-bolt-for-githubbot
changed the title
CVE-2024-27309 (Medium) detected in kafka-metadata-3.6.1.jar
CVE-2024-27309 (Critical) detected in kafka-metadata-3.6.1.jar
Apr 14, 2024
mend-bolt-for-githubbot
changed the title
CVE-2024-27309 (Critical) detected in kafka-metadata-3.6.1.jar
CVE-2024-27309 (Critical) detected in kafka-metadata-3.6.1.jar - autoclosed
Apr 24, 2024
✔️ This issue was automatically closed by Mend because the vulnerable library in the specific branch(es) was either marked as ignored or it is no longer part of the Mend inventory.
CVE-2024-27309 - Critical Severity Vulnerability
Library home page: https://kafka.apache.org
Path to dependency file: /persistence/build.gradle
Path to vulnerable library: /home/wss-scanner/.gradle/caches/modules-2/files-2.1/org.apache.kafka/kafka-metadata/3.6.1/568acb2c4d16ac625be067dcfb68fc75f39e76b6/kafka-metadata-3.6.1.jar
Dependency Hierarchy:
Found in HEAD commit: 335a4047c89f52dfe860e93daefb32dc86a521a2
Found in base branch: develop
While an Apache Kafka cluster is being migrated from ZooKeeper mode to KRaft mode, in some cases ACLs will not be correctly enforced.
Two preconditions are needed to trigger the bug:
When those two preconditions are met, Kafka will treat the resource as if it had only one ACL associated with it after the removal, rather than the two or more that would be correct.
The incorrect condition is cleared by removing all brokers in ZK mode, or by adding a new ACL to the affected resource. Once the migration is completed, there is no metadata loss (the ACLs all remain).
The full impact depends on the ACLs in use. If only ALLOW ACLs were configured during the migration, the impact would be limited to availability impact. if DENY ACLs were configured, the impact could include confidentiality and integrity impact depending on the ACLs configured, as the DENY ACLs might be ignored due to this vulnerability during the migration period.
Publish Date: 2024-04-12
URL: CVE-2024-27309
Base Score Metrics:
Type: Upgrade version
Origin: https://www.cve.org/CVERecord?id=CVE-2024-27309
Release Date: 2024-04-12
Fix Resolution: org.apache.kafka:kafka-metadata:3.6.2
Step up your Open Source Security Game with Mend here
The text was updated successfully, but these errors were encountered: