cvelistv5 - cve-2024-27309

▼	URL	Tags
	security@apache.org	http://www.openwall.com/lists/oss-security/2024/04/12/3
	security@apache.org	https://lists.apache.org/thread/6536rmzyg076lzzdw2xdktvnz163mjpy
	security@apache.org	https://security.netapp.com/advisory/ntap-20240705-0002/

▼	Vendor	Product
	Apache Software Foundation	Apache Kafka

gsd-2024-27309

Vulnerability from gsd

Modified

2024-02-23 06:03

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.

Aliases

CVE-2024-27309

JSON

To clipboard

{
  "gsd": {
    "metadata": {
      "exploitCode": "unknown",
      "remediation": "unknown",
      "reportConfidence": "confirmed",
      "type": "vulnerability"
    },
    "osvSchema": {
      "aliases": [
        "CVE-2024-27309"
      ],
      "details": "While an Apache Kafka cluster is being migrated from ZooKeeper mode to KRaft mode, in some cases ACLs will not be correctly enforced.\n\nTwo preconditions are needed to trigger the bug:\n1. The administrator decides to remove an ACL\n2. The resource associated with the removed ACL continues to have two or more other ACLs associated with it after the removal.\n\nWhen 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.\n\nThe 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).\n\nThe 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.\n\n",
      "id": "GSD-2024-27309",
      "modified": "2024-02-23T06:03:43.529837Z",
      "schema_version": "1.4.0"
    }
  },
  "namespaces": {
    "cve.org": {
      "CVE_data_meta": {
        "ASSIGNER": "security@apache.org",
        "ID": "CVE-2024-27309",
        "STATE": "PUBLIC"
      },
      "affects": {
        "vendor": {
          "vendor_data": [
            {
              "product": {
                "product_data": [
                  {
                    "product_name": "Apache Kafka",
                    "version": {
                      "version_data": [
                        {
                          "version_affected": "\u003c=",
                          "version_name": "3.5.0",
                          "version_value": "3.5.2"
                        },
                        {
                          "version_affected": "\u003c=",
                          "version_name": "3.6.0",
                          "version_value": "3.6.1"
                        }
                      ]
                    }
                  }
                ]
              },
              "vendor_name": "Apache Software Foundation"
            }
          ]
        }
      },
      "data_format": "MITRE",
      "data_type": "CVE",
      "data_version": "4.0",
      "description": {
        "description_data": [
          {
            "lang": "eng",
            "value": "While an Apache Kafka cluster is being migrated from ZooKeeper mode to KRaft mode, in some cases ACLs will not be correctly enforced.\n\nTwo preconditions are needed to trigger the bug:\n1. The administrator decides to remove an ACL\n2. The resource associated with the removed ACL continues to have two or more other ACLs associated with it after the removal.\n\nWhen 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.\n\nThe 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).\n\nThe 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.\n\n"
          }
        ]
      },
      "generator": {
        "engine": "Vulnogram 0.1.0-dev"
      },
      "problemtype": {
        "problemtype_data": [
          {
            "description": [
              {
                "cweId": "CWE-863",
                "lang": "eng",
                "value": "CWE-863 Incorrect Authorization"
              }
            ]
          }
        ]
      },
      "references": {
        "reference_data": [
          {
            "name": "https://lists.apache.org/thread/6536rmzyg076lzzdw2xdktvnz163mjpy",
            "refsource": "MISC",
            "url": "https://lists.apache.org/thread/6536rmzyg076lzzdw2xdktvnz163mjpy"
          }
        ]
      },
      "source": {
        "discovery": "INTERNAL"
      }
    },
    "nvd.nist.gov": {
      "cve": {
        "descriptions": [
          {
            "lang": "en",
            "value": "While an Apache Kafka cluster is being migrated from ZooKeeper mode to KRaft mode, in some cases ACLs will not be correctly enforced.\n\nTwo preconditions are needed to trigger the bug:\n1. The administrator decides to remove an ACL\n2. The resource associated with the removed ACL continues to have two or more other ACLs associated with it after the removal.\n\nWhen 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.\n\nThe 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).\n\nThe 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.\n\n"
          },
          {
            "lang": "es",
            "value": "Mientras se migra un cl\u00faster de Apache Kafka del modo ZooKeeper al modo KRaft, en algunos casos las ACL no se aplicar\u00e1n correctamente. Se necesitan dos condiciones previas para desencadenar el error: 1. El administrador decide eliminar una ACL. 2. El recurso asociado con la ACL eliminada contin\u00faa teniendo dos o m\u00e1s ACL asociadas despu\u00e9s de la eliminaci\u00f3n. Cuando se cumplen esas dos condiciones previas, Kafka tratar\u00e1 el recurso como si tuviera solo una ACL asociada despu\u00e9s de la eliminaci\u00f3n, en lugar de las dos o m\u00e1s que ser\u00edan correctas. La condici\u00f3n incorrecta se elimina eliminando todos los intermediarios en modo ZK o agregando una nueva ACL al recurso afectado. Una vez que se completa la migraci\u00f3n, no hay p\u00e9rdida de metadatos (todas las ACL permanecen). El impacto total depende de las ACL en uso. Si solo se configuraran ALLOW ACL durante la migraci\u00f3n, el impacto se limitar\u00eda al impacto en la disponibilidad. Si se configuraron DENY ACL, el impacto podr\u00eda incluir un impacto en la confidencialidad e integridad seg\u00fan las ACL configuradas, ya que DENY ACL podr\u00edan ignorarse debido a esta vulnerabilidad durante el per\u00edodo de migraci\u00f3n."
          }
        ],
        "id": "CVE-2024-27309",
        "lastModified": "2024-04-12T12:43:46.210",
        "metrics": {},
        "published": "2024-04-12T07:15:08.560",
        "references": [
          {
            "source": "security@apache.org",
            "url": "https://lists.apache.org/thread/6536rmzyg076lzzdw2xdktvnz163mjpy"
          }
        ],
        "sourceIdentifier": "security@apache.org",
        "vulnStatus": "Awaiting Analysis",
        "weaknesses": [
          {
            "description": [
              {
                "lang": "en",
                "value": "CWE-863"
              }
            ],
            "source": "security@apache.org",
            "type": "Primary"
          }
        ]
      }
    }
  }
}

wid-sec-w-2024-0857

Vulnerability from csaf_certbund

Published

2024-04-11 22:00

Modified

2024-07-23 22:00

Summary

Apache Kafka: Schwachstelle ermöglicht Umgehen von Sicherheitsvorkehrungen

Notes

Das BSI ist als Anbieter für die eigenen, zur Nutzung bereitgestellten Inhalte nach den allgemeinen Gesetzen verantwortlich. Nutzerinnen und Nutzer sind jedoch dafür verantwortlich, die Verwendung und/oder die Umsetzung der mit den Inhalten bereitgestellten Informationen sorgfältig im Einzelfall zu prüfen.

Produktbeschreibung

Apache Kafka ist eine verteilte Streaming-Plattform mit einer Publish-Subcribe-Architektur (Pub-Sub).

Angriff

Ein entfernter, anonymer Angreifer kann eine Schwachstelle in Apache Kafka ausnutzen, um Sicherheitsvorkehrungen zu umgehen.

Betroffene Betriebssysteme

- Linux - MacOS X - Sonstiges - Windows

JSON

To clipboard

{
  "document": {
    "aggregate_severity": {
      "text": "mittel"
    },
    "category": "csaf_base",
    "csaf_version": "2.0",
    "distribution": {
      "tlp": {
        "label": "WHITE",
        "url": "https://www.first.org/tlp/"
      }
    },
    "lang": "de-DE",
    "notes": [
      {
        "category": "legal_disclaimer",
        "text": "Das BSI ist als Anbieter f\u00fcr die eigenen, zur Nutzung bereitgestellten Inhalte nach den allgemeinen Gesetzen verantwortlich. Nutzerinnen und Nutzer sind jedoch daf\u00fcr verantwortlich, die Verwendung und/oder die Umsetzung der mit den Inhalten bereitgestellten Informationen sorgf\u00e4ltig im Einzelfall zu pr\u00fcfen."
      },
      {
        "category": "description",
        "text": "Apache Kafka ist eine verteilte Streaming-Plattform mit einer Publish-Subcribe-Architektur (Pub-Sub).",
        "title": "Produktbeschreibung"
      },
      {
        "category": "summary",
        "text": "Ein entfernter, anonymer Angreifer kann eine Schwachstelle in Apache Kafka ausnutzen, um Sicherheitsvorkehrungen zu umgehen.",
        "title": "Angriff"
      },
      {
        "category": "general",
        "text": "- Linux\n- MacOS X\n- Sonstiges\n- Windows",
        "title": "Betroffene Betriebssysteme"
      }
    ],
    "publisher": {
      "category": "other",
      "contact_details": "csaf-provider@cert-bund.de",
      "name": "Bundesamt f\u00fcr Sicherheit in der Informationstechnik",
      "namespace": "https://www.bsi.bund.de"
    },
    "references": [
      {
        "category": "self",
        "summary": "WID-SEC-W-2024-0857 - CSAF Version",
        "url": "https://wid.cert-bund.de/.well-known/csaf/white/2024/wid-sec-w-2024-0857.json"
      },
      {
        "category": "self",
        "summary": "WID-SEC-2024-0857 - Portal Version",
        "url": "https://wid.cert-bund.de/portal/wid/securityadvisory?name=WID-SEC-2024-0857"
      },
      {
        "category": "external",
        "summary": "OSS Mailing List vom 2024-04-11",
        "url": "https://seclists.org/oss-sec/2024/q2/105"
      },
      {
        "category": "external",
        "summary": "IBM Security Bulletin 7161416 vom 2024-07-24",
        "url": "https://www.ibm.com/support/pages/node/7161416"
      }
    ],
    "source_lang": "en-US",
    "title": "Apache Kafka: Schwachstelle erm\u00f6glicht Umgehen von Sicherheitsvorkehrungen",
    "tracking": {
      "current_release_date": "2024-07-23T22:00:00.000+00:00",
      "generator": {
        "date": "2024-07-24T09:32:47.927+00:00",
        "engine": {
          "name": "BSI-WID",
          "version": "1.3.0"
        }
      },
      "id": "WID-SEC-W-2024-0857",
      "initial_release_date": "2024-04-11T22:00:00.000+00:00",
      "revision_history": [
        {
          "date": "2024-04-11T22:00:00.000+00:00",
          "number": "1",
          "summary": "Initiale Fassung"
        },
        {
          "date": "2024-07-23T22:00:00.000+00:00",
          "number": "2",
          "summary": "Neue Updates von IBM aufgenommen"
        }
      ],
      "status": "final",
      "version": "2"
    }
  },
  "product_tree": {
    "branches": [
      {
        "branches": [
          {
            "branches": [
              {
                "category": "product_version",
                "name": "3.5.0",
                "product": {
                  "name": "Apache Kafka 3.5.0",
                  "product_id": "T034098",
                  "product_identification_helper": {
                    "cpe": "cpe:/a:apache:kafka:3.5.0"
                  }
                }
              },
              {
                "category": "product_version",
                "name": "3.5.1",
                "product": {
                  "name": "Apache Kafka 3.5.1",
                  "product_id": "T034099",
                  "product_identification_helper": {
                    "cpe": "cpe:/a:apache:kafka:3.5.1"
                  }
                }
              },
              {
                "category": "product_version",
                "name": "3.5.2",
                "product": {
                  "name": "Apache Kafka 3.5.2",
                  "product_id": "T034100",
                  "product_identification_helper": {
                    "cpe": "cpe:/a:apache:kafka:3.5.2"
                  }
                }
              },
              {
                "category": "product_version",
                "name": "3.6.0",
                "product": {
                  "name": "Apache Kafka 3.6.0",
                  "product_id": "T034101",
                  "product_identification_helper": {
                    "cpe": "cpe:/a:apache:kafka:3.6.0"
                  }
                }
              },
              {
                "category": "product_version",
                "name": "3.6.1",
                "product": {
                  "name": "Apache Kafka 3.6.1",
                  "product_id": "T034102",
                  "product_identification_helper": {
                    "cpe": "cpe:/a:apache:kafka:3.6.1"
                  }
                }
              }
            ],
            "category": "product_name",
            "name": "Kafka"
          }
        ],
        "category": "vendor",
        "name": "Apache"
      },
      {
        "branches": [
          {
            "category": "product_name",
            "name": "IBM Tivoli Netcool/OMNIbus",
            "product": {
              "name": "IBM Tivoli Netcool/OMNIbus",
              "product_id": "T004181",
              "product_identification_helper": {
                "cpe": "cpe:/a:ibm:tivoli_netcool%2fomnibus:-"
              }
            }
          }
        ],
        "category": "vendor",
        "name": "IBM"
      }
    ]
  },
  "vulnerabilities": [
    {
      "cve": "CVE-2024-27309",
      "notes": [
        {
          "category": "description",
          "text": "Es besteht eine Schwachstelle in Apache Kafka. Dieser Fehler besteht w\u00e4hrend der Migration vom ZK-Modus zum KRaft-Modus aufgrund einer falschen Zugriffskontrolle, die zu einer unsachgem\u00e4\u00dfen Implementierung von ACLs f\u00fchrt. Ein entfernter, authentisierter Angreifer kann diese Schwachstelle ausnutzen, um Sicherheitsma\u00dfnahmen zu umgehen."
        }
      ],
      "product_status": {
        "known_affected": [
          "T034099",
          "T034098",
          "T004181",
          "T034102",
          "T034101",
          "T034100"
        ]
      },
      "release_date": "2024-04-11T22:00:00Z",
      "title": "CVE-2024-27309"
    }
  ]
}

ghsa-79vv-vp32-gpp7

Vulnerability from github

Published

2024-04-12 09:33

Modified

2024-07-09 21:39

Severity ?

6.8 (Medium) - CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:N
7.6 (High) - CVSS:4.0/AV:N/AC:H/AT:N/PR:L/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N

Summary

Apache Kafka: Potential incorrect access control during migration from ZK mode to KRaft mode

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.

Show details on source website

JSON

To clipboard

{
  "affected": [
    {
      "package": {
        "ecosystem": "Maven",
        "name": "org.apache.kafka:kafka-metadata"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "3.5.0"
            },
            {
              "fixed": "3.6.2"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ]
    }
  ],
  "aliases": [
    "CVE-2024-27309"
  ],
  "database_specific": {
    "cwe_ids": [
      "CWE-863"
    ],
    "github_reviewed": true,
    "github_reviewed_at": "2024-04-12T21:26:30Z",
    "nvd_published_at": "2024-04-12T07:15:08Z",
    "severity": "MODERATE"
  },
  "details": "While an Apache Kafka cluster is being migrated from ZooKeeper mode to KRaft mode, in some cases ACLs will not be correctly enforced.\n\nTwo preconditions are needed to trigger the bug:\n1. The administrator decides to remove an ACL\n2. The resource associated with the removed ACL continues to have two or more other ACLs associated with it after the removal.\n\nWhen 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.\n\nThe 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).\n\nThe 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.\n\n",
  "id": "GHSA-79vv-vp32-gpp7",
  "modified": "2024-07-09T21:39:36Z",
  "published": "2024-04-12T09:33:40Z",
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2024-27309"
    },
    {
      "type": "WEB",
      "url": "https://github.com/apache/kafka/commit/c000b1fae2bd7d4b76713a53508f128a13431ab6"
    },
    {
      "type": "PACKAGE",
      "url": "https://github.com/apache/kafka"
    },
    {
      "type": "WEB",
      "url": "https://lists.apache.org/thread/6536rmzyg076lzzdw2xdktvnz163mjpy"
    },
    {
      "type": "WEB",
      "url": "https://security.netapp.com/advisory/ntap-20240705-0002"
    },
    {
      "type": "WEB",
      "url": "http://www.openwall.com/lists/oss-security/2024/04/12/3"
    }
  ],
  "schema_version": "1.4.0",
  "severity": [
    {
      "score": "CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:N",
      "type": "CVSS_V3"
    },
    {
      "score": "CVSS:4.0/AV:N/AC:H/AT:N/PR:L/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N",
      "type": "CVSS_V4"
    }
  ],
  "summary": "Apache Kafka: Potential incorrect access control during migration from ZK mode to KRaft mode"
}

cve-2024-27309

Vulnerability from cvelistv5

Tags

Sightings

Nomenclature

Action not permitted

cve-2024-27309

Vulnerability from cvelistv5

gsd-2024-27309

Vulnerability from gsd

wid-sec-w-2024-0857

Vulnerability from csaf_certbund

ghsa-79vv-vp32-gpp7

Vulnerability from github

Tags

Sightings

Nomenclature