ghsa-c9h3-c6qj-hh7q
Vulnerability from github
Published
2022-09-21 00:00
Modified
2024-05-08 17:44
Severity ?
7.5 (High) - CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
Summary
Apache Kafka vulnerability can lead to brokers hitting OutOfMemoryException, causing Denial of Service
Details

A security vulnerability has been identified in Apache Kafka. It affects all releases since 2.8.0. The vulnerability allows malicious unauthenticated clients to allocate large amounts of memory on brokers. This can lead to brokers hitting OutOfMemoryException and causing denial of service. Example scenarios: - Kafka cluster without authentication: Any clients able to establish a network connection to a broker can trigger the issue. - Kafka cluster with SASL authentication: Any clients able to establish a network connection to a broker, without the need for valid SASL credentials, can trigger the issue. - Kafka cluster with TLS authentication: Only clients able to successfully authenticate via TLS can trigger the issue. We advise the users to upgrade the Kafka installations to one of the 3.2.3, 3.1.2, 3.0.2, 2.8.2 versions.

Show details on source website

To clipboard 

{
   affected: [
      {
         package: {
            ecosystem: "Maven",
            name: "org.apache.kafka:kafka",
         },
         ranges: [
            {
               events: [
                  {
                     introduced: "2.8.0",
                  },
                  {
                     fixed: "2.8.2",
                  },
               ],
               type: "ECOSYSTEM",
            },
         ],
      },
      {
         package: {
            ecosystem: "Maven",
            name: "org.apache.kafka:kafka",
         },
         ranges: [
            {
               events: [
                  {
                     introduced: "3.0.0",
                  },
                  {
                     fixed: "3.0.2",
                  },
               ],
               type: "ECOSYSTEM",
            },
         ],
      },
      {
         package: {
            ecosystem: "Maven",
            name: "org.apache.kafka:kafka",
         },
         ranges: [
            {
               events: [
                  {
                     introduced: "3.1.0",
                  },
                  {
                     fixed: "3.1.2",
                  },
               ],
               type: "ECOSYSTEM",
            },
         ],
      },
      {
         package: {
            ecosystem: "Maven",
            name: "org.apache.kafka:kafka",
         },
         ranges: [
            {
               events: [
                  {
                     introduced: "3.2.0",
                  },
                  {
                     fixed: "3.2.3",
                  },
               ],
               type: "ECOSYSTEM",
            },
         ],
      },
   ],
   aliases: [
      "CVE-2022-34917",
   ],
   database_specific: {
      cwe_ids: [
         "CWE-400",
         "CWE-770",
         "CWE-789",
      ],
      github_reviewed: true,
      github_reviewed_at: "2022-09-21T21:15:52Z",
      nvd_published_at: "2022-09-20T09:15:00Z",
      severity: "HIGH",
   },
   details: "A security vulnerability has been identified in Apache Kafka. It affects all releases since 2.8.0. The vulnerability allows malicious unauthenticated clients to allocate large amounts of memory on brokers. This can lead to brokers hitting OutOfMemoryException and causing denial of service. Example scenarios: - Kafka cluster without authentication: Any clients able to establish a network connection to a broker can trigger the issue. - Kafka cluster with SASL authentication: Any clients able to establish a network connection to a broker, without the need for valid SASL credentials, can trigger the issue. - Kafka cluster with TLS authentication: Only clients able to successfully authenticate via TLS can trigger the issue. We advise the users to upgrade the Kafka installations to one of the 3.2.3, 3.1.2, 3.0.2, 2.8.2 versions.",
   id: "GHSA-c9h3-c6qj-hh7q",
   modified: "2024-05-08T17:44:34Z",
   published: "2022-09-21T00:00:52Z",
   references: [
      {
         type: "ADVISORY",
         url: "https://nvd.nist.gov/vuln/detail/CVE-2022-34917",
      },
      {
         type: "WEB",
         url: "https://github.com/apache/kafka/commit/14951a83e3fdead212156e5532359500d72f68bc",
      },
      {
         type: "WEB",
         url: "https://github.com/apache/kafka/commit/2bfa24b2bd416e7b8c4a0c566b984c43904fdecb",
      },
      {
         type: "WEB",
         url: "https://github.com/apache/kafka/commit/aaceb6b79bfcb1d32874ccdbc8f3138d1c1c00fb",
      },
      {
         type: "WEB",
         url: "https://github.com/apache/kafka/commit/c1295662768e64b4467e27c3d5158f95f2307657",
      },
      {
         type: "WEB",
         url: "https://issues.apache.org/jira/browse/KAFKA-14063",
      },
      {
         type: "WEB",
         url: "https://kafka.apache.org/cve-list",
      },
      {
         type: "WEB",
         url: "https://kafka.apache.org/cve-list#CVE-2022-34917",
      },
   ],
   schema_version: "1.4.0",
   severity: [
      {
         score: "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H",
         type: "CVSS_V3",
      },
   ],
   summary: "Apache Kafka vulnerability can lead to brokers hitting OutOfMemoryException, causing Denial of Service",
}


Log in or create an account to share your comment.

Security Advisory comment format.

This schema specifies the format of a comment related to a security advisory.

UUIDv4 of the comment
UUIDv4 of the Vulnerability-Lookup instance
When the comment was created originally
When the comment was last updated
Title of the comment
Description of the comment
The identifier of the vulnerability (CVE ID, GHSA-ID, PYSEC ID, etc.).



Tags
Taxonomy of the tags.




Sightings

Author Source Type Date

Nomenclature

  • Seen: The vulnerability was mentioned, discussed, or seen somewhere by the user.
  • Confirmed: The vulnerability is confirmed from an analyst perspective.
  • Exploited: This vulnerability was exploited and seen by the user reporting the sighting.
  • Patched: This vulnerability was successfully patched by the user reporting the sighting.
  • Not exploited: This vulnerability was not exploited or seen by the user reporting the sighting.
  • Not confirmed: The user expresses doubt about the veracity of the vulnerability.
  • Not patched: This vulnerability was not successfully patched by the user reporting the sighting.