Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

CVE-2024-27309 (Critical) detected in kafka-metadata-3.6.1.jar - autoclosed #2433

Closed
mend-bolt-for-github bot opened this issue Apr 12, 2024 · 1 comment
Labels
Mend: dependency security vulnerability Security vulnerability detected by WhiteSource

Comments

@mend-bolt-for-github
Copy link
Contributor

mend-bolt-for-github bot commented Apr 12, 2024

CVE-2024-27309 - Critical Severity Vulnerability

Vulnerable Library - kafka-metadata-3.6.1.jar

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:

  • spring-kafka-test-3.1.3.jar (Root Library)
    • kafka-metadata-3.6.1.jar (Vulnerable Library)

Found in HEAD commit: 335a4047c89f52dfe860e93daefb32dc86a521a2

Found in base branch: develop

Vulnerability Details

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:

  1. The administrator decides to remove an ACL
  2. 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.

Publish Date: 2024-04-12

URL: CVE-2024-27309

CVSS 3 Score Details (9.8)

Base Score Metrics:

  • Exploitability Metrics:
    • Attack Vector: Network
    • Attack Complexity: Low
    • Privileges Required: None
    • User Interaction: None
    • Scope: Unchanged
  • Impact Metrics:
    • Confidentiality Impact: High
    • Integrity Impact: High
    • Availability Impact: High

For more information on CVSS3 Scores, click here.

Suggested Fix

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

@mend-bolt-for-github mend-bolt-for-github bot added the Mend: dependency security vulnerability Security vulnerability detected by WhiteSource label Apr 12, 2024
@mend-bolt-for-github mend-bolt-for-github bot 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-github mend-bolt-for-github bot 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
Copy link
Contributor Author

✔️ 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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Mend: dependency security vulnerability Security vulnerability detected by WhiteSource
Projects
None yet
Development

No branches or pull requests

0 participants