fkie_cve-2022-34917
Vulnerability from fkie_nvd
Published
2022-09-20 09:15
Modified
2024-11-21 07:10
Severity ?
7.5 (High) - CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
Summary
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.
References
security@apache.orghttps://kafka.apache.org/cve-listVendor Advisory
af854a3a-2127-422b-91ae-364da2661108https://kafka.apache.org/cve-listVendor Advisory
Impacted products
Vendor Product Version
apache kafka *
apache kafka *
apache kafka *
apache kafka *


To clipboard 

{
   configurations: [
      {
         nodes: [
            {
               cpeMatch: [
                  {
                     criteria: "cpe:2.3:a:apache:kafka:*:*:*:*:*:*:*:*",
                     matchCriteriaId: "7AEDD691-C927-4B50-92D7-7C220C575878",
                     versionEndExcluding: "2.8.2",
                     versionStartIncluding: "2.8.0",
                     vulnerable: true,
                  },
                  {
                     criteria: "cpe:2.3:a:apache:kafka:*:*:*:*:*:*:*:*",
                     matchCriteriaId: "072B6FDE-E8C0-4C25-A3DD-E2CC88156B59",
                     versionEndExcluding: "3.0.2",
                     versionStartIncluding: "3.0.0",
                     vulnerable: true,
                  },
                  {
                     criteria: "cpe:2.3:a:apache:kafka:*:*:*:*:*:*:*:*",
                     matchCriteriaId: "D60DE54C-BC4D-4479-BCFD-58E242771CDF",
                     versionEndExcluding: "3.1.2",
                     versionStartIncluding: "3.1.0",
                     vulnerable: true,
                  },
                  {
                     criteria: "cpe:2.3:a:apache:kafka:*:*:*:*:*:*:*:*",
                     matchCriteriaId: "26FF6A2C-0A2A-4E06-B6BA-DA2F62190447",
                     versionEndExcluding: "3.2.3",
                     versionStartIncluding: "3.2.0",
                     vulnerable: true,
                  },
               ],
               negate: false,
               operator: "OR",
            },
         ],
      },
   ],
   cveTags: [],
   descriptions: [
      {
         lang: "en",
         value: "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.",
      },
      {
         lang: "es",
         value: "Se ha identificado una vulnerabilidad de seguridad en Apache Kafka. Afecta a todas las versiones desde la 2.8.0. La vulnerabilidad permite a clientes maliciosos no autenticados asignar grandes cantidades de memoria en los brokers. Esto puede conllevar a que los brokers sufran una OutOfMemoryException y causar una denegación de servicio. Ejemplos de escenarios: - Cluster Kafka sin autenticación: Cualquier cliente capaz de establecer una conexión de red con un broker puede desencadenar el problema. - Clúster Kafka con autenticación SASL: Cualquier cliente capaz de establecer una conexión de red con un broker, sin necesidad de credenciales SASL válidas, puede desencadenar el problema. - Clúster Kafka con autenticación TLS: Sólo los clientes capaces de autenticarse con éxito por medio de TLS pueden desencadenar el problema. REcomendamos a usuarios actualizar las instalaciones de Kafka a una de las versiones 3.2.3, 3.1.2, 3.0.2, 2.8.2",
      },
   ],
   id: "CVE-2022-34917",
   lastModified: "2024-11-21T07:10:25.960",
   metrics: {
      cvssMetricV31: [
         {
            cvssData: {
               attackComplexity: "LOW",
               attackVector: "NETWORK",
               availabilityImpact: "HIGH",
               baseScore: 7.5,
               baseSeverity: "HIGH",
               confidentialityImpact: "NONE",
               integrityImpact: "NONE",
               privilegesRequired: "NONE",
               scope: "UNCHANGED",
               userInteraction: "NONE",
               vectorString: "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H",
               version: "3.1",
            },
            exploitabilityScore: 3.9,
            impactScore: 3.6,
            source: "nvd@nist.gov",
            type: "Primary",
         },
      ],
   },
   published: "2022-09-20T09:15:09.437",
   references: [
      {
         source: "security@apache.org",
         tags: [
            "Vendor Advisory",
         ],
         url: "https://kafka.apache.org/cve-list",
      },
      {
         source: "af854a3a-2127-422b-91ae-364da2661108",
         tags: [
            "Vendor Advisory",
         ],
         url: "https://kafka.apache.org/cve-list",
      },
   ],
   sourceIdentifier: "security@apache.org",
   vulnStatus: "Modified",
   weaknesses: [
      {
         description: [
            {
               lang: "en",
               value: "CWE-789",
            },
         ],
         source: "security@apache.org",
         type: "Secondary",
      },
      {
         description: [
            {
               lang: "en",
               value: "CWE-770",
            },
         ],
         source: "nvd@nist.gov",
         type: "Primary",
      },
   ],
}


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.