cvelistv5 - cve-2024-56128

cve-2024-56128

Vulnerability from cvelistv5

Published

2024-12-18 13:38

Modified

2024-12-18 17:02

Severity ?

Summary

Incorrect Implementation of Authentication Algorithm in Apache Kafka's SCRAM implementation. Issue Summary: Apache Kafka's implementation of the Salted Challenge Response Authentication Mechanism (SCRAM) did not fully adhere to the requirements of RFC 5802 [1]. Specifically, as per RFC 5802, the server must verify that the nonce sent by the client in the second message matches the nonce sent by the server in its first message. However, Kafka's SCRAM implementation did not perform this validation. Impact: This vulnerability is exploitable only when an attacker has plaintext access to the SCRAM authentication exchange. However, the usage of SCRAM over plaintext is strongly discouraged as it is considered an insecure practice [2]. Apache Kafka recommends deploying SCRAM exclusively with TLS encryption to protect SCRAM exchanges from interception [3]. Deployments using SCRAM with TLS are not affected by this issue. How to Detect If You Are Impacted: If your deployment uses SCRAM authentication over plaintext communication channels (without TLS encryption), you are likely impacted. To check if TLS is enabled, review your server.properties configuration file for listeners property. If you have SASL_PLAINTEXT in the listeners, then you are likely impacted. Fix Details: The issue has been addressed by introducing nonce verification in the final message of the SCRAM authentication exchange to ensure compliance with RFC 5802. Affected Versions: Apache Kafka versions 0.10.2.0 through 3.9.0, excluding the fixed versions below. Fixed Versions: 3.9.0 3.8.1 3.7.2 Users are advised to upgrade to 3.7.2 or later to mitigate this issue. Recommendations for Mitigation: Users unable to upgrade to the fixed versions can mitigate the issue by: - Using TLS with SCRAM Authentication: Always deploy SCRAM over TLS to encrypt authentication exchanges and protect against interception. - Considering Alternative Authentication Mechanisms: Evaluate alternative authentication mechanisms, such as PLAIN, Kerberos or OAuth with TLS, which provide additional layers of security.

References

▼	URL	Tags
	security@apache.org	https://datatracker.ietf.org/doc/html/rfc5802
	security@apache.org	https://datatracker.ietf.org/doc/html/rfc5802#section-9
	security@apache.org	https://kafka.apache.org/documentation/#security_sasl_scram_security
	security@apache.org	https://lists.apache.org/thread/84dh4so32lwn7wr6c5s9mwh381vx9wkw
	af854a3a-2127-422b-91ae-364da2661108	http://www.openwall.com/lists/oss-security/2024/12/18/3

Impacted products

	Vendor	Product	Version
	Apache Software Foundation	Apache Kafka	Version: 0.10.2.0 ≤ Version: 3.8.0 ≤

Show details on NVD website

JSON

To clipboard

{
   containers: {
      adp: [
         {
            metrics: [
               {
                  cvssV3_1: {
                     attackComplexity: "LOW",
                     attackVector: "NETWORK",
                     availabilityImpact: "NONE",
                     baseScore: 5.3,
                     baseSeverity: "MEDIUM",
                     confidentialityImpact: "LOW",
                     integrityImpact: "NONE",
                     privilegesRequired: "NONE",
                     scope: "UNCHANGED",
                     userInteraction: "NONE",
                     vectorString: "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N",
                     version: "3.1",
                  },
               },
               {
                  other: {
                     content: {
                        id: "CVE-2024-56128",
                        options: [
                           {
                              Exploitation: "none",
                           },
                           {
                              Automatable: "no",
                           },
                           {
                              "Technical Impact": "partial",
                           },
                        ],
                        role: "CISA Coordinator",
                        timestamp: "2024-12-18T16:15:35.208336Z",
                        version: "2.0.3",
                     },
                     type: "ssvc",
                  },
               },
            ],
            providerMetadata: {
               dateUpdated: "2024-12-18T16:19:50.073Z",
               orgId: "134c704f-9b21-4f2e-91b3-4a467353bcc0",
               shortName: "CISA-ADP",
            },
            title: "CISA ADP Vulnrichment",
         },
         {
            providerMetadata: {
               dateUpdated: "2024-12-18T17:02:47.926Z",
               orgId: "af854a3a-2127-422b-91ae-364da2661108",
               shortName: "CVE",
            },
            references: [
               {
                  url: "http://www.openwall.com/lists/oss-security/2024/12/18/3",
               },
            ],
            title: "CVE Program Container",
         },
      ],
      cna: {
         affected: [
            {
               defaultStatus: "unaffected",
               product: "Apache Kafka",
               vendor: "Apache Software Foundation",
               versions: [
                  {
                     lessThan: "3.7.2",
                     status: "affected",
                     version: "0.10.2.0",
                     versionType: "semver",
                  },
                  {
                     status: "affected",
                     version: "3.8.0",
                     versionType: "semver",
                  },
               ],
            },
         ],
         credits: [
            {
               lang: "en",
               type: "finder",
               value: "Tim Fox (timvolpe@gmail.com)",
            },
            {
               lang: "en",
               type: "remediation developer",
               value: "Vikas Singh <vikas@confluent.io>",
            },
         ],
         descriptions: [
            {
               lang: "en",
               supportingMedia: [
                  {
                     base64: false,
                     type: "text/html",
                     value: "<p>Incorrect Implementation of Authentication Algorithm in Apache Kafka's SCRAM implementation.<br><br>Issue Summary:<br>Apache Kafka's implementation of the Salted Challenge Response Authentication Mechanism (SCRAM) did not fully adhere to the requirements of RFC 5802 [1].<br>Specifically, as per RFC 5802, the server must verify that the nonce sent by the client in the second message matches the nonce sent by the server in its first message.<br>However, Kafka's SCRAM implementation did not perform this validation.<br><br>Impact:<br>This vulnerability is exploitable only when an attacker has plaintext access to the SCRAM authentication exchange. However, the usage of SCRAM over plaintext is strongly<br>discouraged as it is considered an insecure practice [2]. Apache Kafka recommends deploying SCRAM exclusively with TLS encryption to protect SCRAM exchanges from interception [3].<br>Deployments using SCRAM with TLS are not affected by this issue.</p>How to Detect If You Are Impacted:<br>If your deployment uses SCRAM authentication over plaintext communication channels (without TLS encryption), you are likely impacted.<br>To check if TLS is enabled, review your server.properties configuration file for listeners property. If you have SASL_PLAINTEXT in the listeners, then you are likely impacted.<br><br><span style=\"background-color: var(--wht);\">Fix Details:<br></span><span style=\"background-color: var(--wht);\">The issue has been addressed by introducing nonce verification in the final message of the SCRAM authentication exchange to ensure compliance with RFC 5802.<br><br></span><span style=\"background-color: var(--wht);\">Affected Versions:<br></span><span style=\"background-color: var(--wht);\">Apache Kafka versions 0.10.2.0 through 3.9.0, excluding the fixed versions below.<br><br></span><span style=\"background-color: var(--wht);\">Fixed Versions:<br></span><span style=\"background-color: var(--wht);\">3.9.0<br></span><span style=\"background-color: var(--wht);\">3.8.1<br></span><span style=\"background-color: var(--wht);\">3.7.2<br><br></span><span style=\"background-color: var(--wht);\">Users are advised to upgrade to 3.7.2 or later to mitigate this issue.<br><br></span><span style=\"background-color: var(--wht);\">Recommendations for Mitigation:<br></span><span style=\"background-color: var(--wht);\">Users unable to upgrade to the fixed versions can mitigate the issue by:<br></span><span style=\"background-color: var(--wht);\">- Using TLS with SCRAM Authentication:<br></span><span style=\"background-color: var(--wht);\">Always deploy SCRAM over TLS to encrypt authentication exchanges and protect against interception.<br></span><span style=\"background-color: var(--wht);\">- Considering Alternative Authentication Mechanisms:<br></span><span style=\"background-color: var(--wht);\">Evaluate alternative authentication mechanisms, such as PLAIN, Kerberos or OAuth with TLS, which provide additional layers of security.</span><br>",
                  },
               ],
               value: "Incorrect Implementation of Authentication Algorithm in Apache Kafka's SCRAM implementation.\n\nIssue Summary:\nApache Kafka's implementation of the Salted Challenge Response Authentication Mechanism (SCRAM) did not fully adhere to the requirements of RFC 5802 [1].\nSpecifically, as per RFC 5802, the server must verify that the nonce sent by the client in the second message matches the nonce sent by the server in its first message.\nHowever, Kafka's SCRAM implementation did not perform this validation.\n\nImpact:\nThis vulnerability is exploitable only when an attacker has plaintext access to the SCRAM authentication exchange. However, the usage of SCRAM over plaintext is strongly\ndiscouraged as it is considered an insecure practice [2]. Apache Kafka recommends deploying SCRAM exclusively with TLS encryption to protect SCRAM exchanges from interception [3].\nDeployments using SCRAM with TLS are not affected by this issue.\n\nHow to Detect If You Are Impacted:\nIf your deployment uses SCRAM authentication over plaintext communication channels (without TLS encryption), you are likely impacted.\nTo check if TLS is enabled, review your server.properties configuration file for listeners property. If you have SASL_PLAINTEXT in the listeners, then you are likely impacted.\n\nFix Details:\nThe issue has been addressed by introducing nonce verification in the final message of the SCRAM authentication exchange to ensure compliance with RFC 5802.\n\nAffected Versions:\nApache Kafka versions 0.10.2.0 through 3.9.0, excluding the fixed versions below.\n\nFixed Versions:\n3.9.0\n3.8.1\n3.7.2\n\nUsers are advised to upgrade to 3.7.2 or later to mitigate this issue.\n\nRecommendations for Mitigation:\nUsers unable to upgrade to the fixed versions can mitigate the issue by:\n- Using TLS with SCRAM Authentication:\nAlways deploy SCRAM over TLS to encrypt authentication exchanges and protect against interception.\n- Considering Alternative Authentication Mechanisms:\nEvaluate alternative authentication mechanisms, such as PLAIN, Kerberos or OAuth with TLS, which provide additional layers of security.",
            },
         ],
         metrics: [
            {
               other: {
                  content: {
                     text: "low",
                  },
                  type: "Textual description of severity",
               },
            },
         ],
         problemTypes: [
            {
               descriptions: [
                  {
                     cweId: "CWE-303",
                     description: "CWE-303 Incorrect Implementation of Authentication Algorithm",
                     lang: "en",
                     type: "CWE",
                  },
               ],
            },
         ],
         providerMetadata: {
            dateUpdated: "2024-12-18T13:38:03.068Z",
            orgId: "f0158376-9dc2-43b6-827c-5f631a4d8d09",
            shortName: "apache",
         },
         references: [
            {
               tags: [
                  "related",
               ],
               url: "https://datatracker.ietf.org/doc/html/rfc5802",
            },
            {
               tags: [
                  "related",
               ],
               url: "https://datatracker.ietf.org/doc/html/rfc5802#section-9",
            },
            {
               url: "https://kafka.apache.org/documentation/#security_sasl_scram_security",
            },
            {
               tags: [
                  "vendor-advisory",
               ],
               url: "https://lists.apache.org/thread/84dh4so32lwn7wr6c5s9mwh381vx9wkw",
            },
         ],
         source: {
            discovery: "EXTERNAL",
         },
         title: "Apache Kafka: SCRAM authentication vulnerable to replay attacks when used without encryption",
         x_generator: {
            engine: "Vulnogram 0.2.0",
         },
      },
   },
   cveMetadata: {
      assignerOrgId: "f0158376-9dc2-43b6-827c-5f631a4d8d09",
      assignerShortName: "apache",
      cveId: "CVE-2024-56128",
      datePublished: "2024-12-18T13:38:03.068Z",
      dateReserved: "2024-12-16T14:52:48.326Z",
      dateUpdated: "2024-12-18T17:02:47.926Z",
      state: "PUBLISHED",
   },
   dataType: "CVE_RECORD",
   dataVersion: "5.1",
   "vulnerability-lookup:meta": {
      fkie_nvd: {
         descriptions: "[{\"lang\": \"en\", \"value\": \"Incorrect Implementation of Authentication Algorithm in Apache Kafka's SCRAM implementation.\\n\\nIssue Summary:\\nApache Kafka's implementation of the Salted Challenge Response Authentication Mechanism (SCRAM) did not fully adhere to the requirements of RFC 5802 [1].\\nSpecifically, as per RFC 5802, the server must verify that the nonce sent by the client in the second message matches the nonce sent by the server in its first message.\\nHowever, Kafka's SCRAM implementation did not perform this validation.\\n\\nImpact:\\nThis vulnerability is exploitable only when an attacker has plaintext access to the SCRAM authentication exchange. However, the usage of SCRAM over plaintext is strongly\\ndiscouraged as it is considered an insecure practice [2]. Apache Kafka recommends deploying SCRAM exclusively with TLS encryption to protect SCRAM exchanges from interception [3].\\nDeployments using SCRAM with TLS are not affected by this issue.\\n\\nHow to Detect If You Are Impacted:\\nIf your deployment uses SCRAM authentication over plaintext communication channels (without TLS encryption), you are likely impacted.\\nTo check if TLS is enabled, review your server.properties configuration file for listeners property. If you have SASL_PLAINTEXT in the listeners, then you are likely impacted.\\n\\nFix Details:\\nThe issue has been addressed by introducing nonce verification in the final message of the SCRAM authentication exchange to ensure compliance with RFC 5802.\\n\\nAffected Versions:\\nApache Kafka versions 0.10.2.0 through 3.9.0, excluding the fixed versions below.\\n\\nFixed Versions:\\n3.9.0\\n3.8.1\\n3.7.2\\n\\nUsers are advised to upgrade to 3.7.2 or later to mitigate this issue.\\n\\nRecommendations for Mitigation:\\nUsers unable to upgrade to the fixed versions can mitigate the issue by:\\n- Using TLS with SCRAM Authentication:\\nAlways deploy SCRAM over TLS to encrypt authentication exchanges and protect against interception.\\n- Considering Alternative Authentication Mechanisms:\\nEvaluate alternative authentication mechanisms, such as PLAIN, Kerberos or OAuth with TLS, which provide additional layers of security.\"}, {\"lang\": \"es\", \"value\": \"Implementaci\\u00f3n incorrecta del algoritmo de autenticaci\\u00f3n en la implementaci\\u00f3n SCRAM de Apache Kafka. Resumen del problema: La implementaci\\u00f3n de Apache Kafka del mecanismo de autenticaci\\u00f3n de respuesta a desaf\\u00edo con sal (SCRAM) no se adhiri\\u00f3 completamente a los requisitos de RFC 5802 [1]. Espec\\u00edficamente, seg\\u00fan RFC 5802, el servidor debe verificar que el nonce enviado por el cliente en el segundo mensaje coincida con el nonce enviado por el servidor en su primer mensaje. Sin embargo, la implementaci\\u00f3n SCRAM de Kafka no realiz\\u00f3 esta validaci\\u00f3n. Impacto: Esta vulnerabilidad es explotable solo cuando un atacante tiene acceso de texto simple al intercambio de autenticaci\\u00f3n SCRAM. Sin embargo, el uso de SCRAM sobre texto simple se desaconseja enf\\u00e1ticamente ya que se considera una pr\\u00e1ctica insegura [2]. Apache Kafka recomienda implementar SCRAM exclusivamente con cifrado TLS para proteger los intercambios SCRAM de la intercepci\\u00f3n [3]. Las implementaciones que utilizan SCRAM con TLS no se ven afectadas por este problema. C\\u00f3mo detectar si est\\u00e1 afectado: si su implementaci\\u00f3n utiliza autenticaci\\u00f3n SCRAM sobre canales de comunicaci\\u00f3n de texto plano (sin cifrado TLS), es probable que est\\u00e9 afectado. Para verificar si TLS est\\u00e1 habilitado, revise su archivo de configuraci\\u00f3n server.properties para la propiedad listeners. Si tiene SASL_PLAINTEXT en los listeners, es probable que est\\u00e9 afectado. Detalles de la soluci\\u00f3n: el problema se ha solucionado introduciendo la verificaci\\u00f3n de nonce en el mensaje final del intercambio de autenticaci\\u00f3n SCRAM para garantizar el cumplimiento de RFC 5802. Versiones afectadas: Apache Kafka versiones 0.10.2.0 a 3.9.0, excluidas las versiones corregidas a continuaci\\u00f3n. Versiones corregidas: 3.9.0 3.8.1 3.7.2 Se recomienda a los usuarios que actualicen a 3.7.2 o posterior para mitigar este problema. Recomendaciones para la mitigaci\\u00f3n: los usuarios que no puedan actualizar a las versiones corregidas pueden mitigar el problema mediante lo siguiente: - Uso de TLS con autenticaci\\u00f3n SCRAM: siempre implemente SCRAM sobre TLS para cifrar los intercambios de autenticaci\\u00f3n y protegerse contra la interceptaci\\u00f3n. - Consideraci\\u00f3n de mecanismos de autenticaci\\u00f3n alternativos: evaluar mecanismos de autenticaci\\u00f3n alternativos, como PLAIN, Kerberos u OAuth con TLS, que proporcionan capas adicionales de seguridad.\"}]",
         id: "CVE-2024-56128",
         lastModified: "2024-12-18T17:15:15.003",
         metrics: "{\"cvssMetricV31\": [{\"source\": \"134c704f-9b21-4f2e-91b3-4a467353bcc0\", \"type\": \"Secondary\", \"cvssData\": {\"version\": \"3.1\", \"vectorString\": \"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N\", \"baseScore\": 5.3, \"baseSeverity\": \"MEDIUM\", \"attackVector\": \"NETWORK\", \"attackComplexity\": \"LOW\", \"privilegesRequired\": \"NONE\", \"userInteraction\": \"NONE\", \"scope\": \"UNCHANGED\", \"confidentialityImpact\": \"LOW\", \"integrityImpact\": \"NONE\", \"availabilityImpact\": \"NONE\"}, \"exploitabilityScore\": 3.9, \"impactScore\": 1.4}]}",
         published: "2024-12-18T14:15:23.277",
         references: "[{\"url\": \"https://datatracker.ietf.org/doc/html/rfc5802\", \"source\": \"security@apache.org\"}, {\"url\": \"https://datatracker.ietf.org/doc/html/rfc5802#section-9\", \"source\": \"security@apache.org\"}, {\"url\": \"https://kafka.apache.org/documentation/#security_sasl_scram_security\", \"source\": \"security@apache.org\"}, {\"url\": \"https://lists.apache.org/thread/84dh4so32lwn7wr6c5s9mwh381vx9wkw\", \"source\": \"security@apache.org\"}, {\"url\": \"http://www.openwall.com/lists/oss-security/2024/12/18/3\", \"source\": \"af854a3a-2127-422b-91ae-364da2661108\"}]",
         sourceIdentifier: "security@apache.org",
         vulnStatus: "Awaiting Analysis",
         weaknesses: "[{\"source\": \"security@apache.org\", \"type\": \"Secondary\", \"description\": [{\"lang\": \"en\", \"value\": \"CWE-303\"}]}]",
      },
      nvd: "{\"cve\":{\"id\":\"CVE-2024-56128\",\"sourceIdentifier\":\"security@apache.org\",\"published\":\"2024-12-18T14:15:23.277\",\"lastModified\":\"2024-12-18T17:15:15.003\",\"vulnStatus\":\"Received\",\"cveTags\":[],\"descriptions\":[{\"lang\":\"en\",\"value\":\"Incorrect Implementation of Authentication Algorithm in Apache Kafka's SCRAM implementation.\\n\\nIssue Summary:\\nApache Kafka's implementation of the Salted Challenge Response Authentication Mechanism (SCRAM) did not fully adhere to the requirements of RFC 5802 [1].\\nSpecifically, as per RFC 5802, the server must verify that the nonce sent by the client in the second message matches the nonce sent by the server in its first message.\\nHowever, Kafka's SCRAM implementation did not perform this validation.\\n\\nImpact:\\nThis vulnerability is exploitable only when an attacker has plaintext access to the SCRAM authentication exchange. However, the usage of SCRAM over plaintext is strongly\\ndiscouraged as it is considered an insecure practice [2]. Apache Kafka recommends deploying SCRAM exclusively with TLS encryption to protect SCRAM exchanges from interception [3].\\nDeployments using SCRAM with TLS are not affected by this issue.\\n\\nHow to Detect If You Are Impacted:\\nIf your deployment uses SCRAM authentication over plaintext communication channels (without TLS encryption), you are likely impacted.\\nTo check if TLS is enabled, review your server.properties configuration file for listeners property. If you have SASL_PLAINTEXT in the listeners, then you are likely impacted.\\n\\nFix Details:\\nThe issue has been addressed by introducing nonce verification in the final message of the SCRAM authentication exchange to ensure compliance with RFC 5802.\\n\\nAffected Versions:\\nApache Kafka versions 0.10.2.0 through 3.9.0, excluding the fixed versions below.\\n\\nFixed Versions:\\n3.9.0\\n3.8.1\\n3.7.2\\n\\nUsers are advised to upgrade to 3.7.2 or later to mitigate this issue.\\n\\nRecommendations for Mitigation:\\nUsers unable to upgrade to the fixed versions can mitigate the issue by:\\n- Using TLS with SCRAM Authentication:\\nAlways deploy SCRAM over TLS to encrypt authentication exchanges and protect against interception.\\n- Considering Alternative Authentication Mechanisms:\\nEvaluate alternative authentication mechanisms, such as PLAIN, Kerberos or OAuth with TLS, which provide additional layers of security.\"}],\"metrics\":{\"cvssMetricV31\":[{\"source\":\"134c704f-9b21-4f2e-91b3-4a467353bcc0\",\"type\":\"Secondary\",\"cvssData\":{\"version\":\"3.1\",\"vectorString\":\"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N\",\"baseScore\":5.3,\"baseSeverity\":\"MEDIUM\",\"attackVector\":\"NETWORK\",\"attackComplexity\":\"LOW\",\"privilegesRequired\":\"NONE\",\"userInteraction\":\"NONE\",\"scope\":\"UNCHANGED\",\"confidentialityImpact\":\"LOW\",\"integrityImpact\":\"NONE\",\"availabilityImpact\":\"NONE\"},\"exploitabilityScore\":3.9,\"impactScore\":1.4}]},\"weaknesses\":[{\"source\":\"security@apache.org\",\"type\":\"Secondary\",\"description\":[{\"lang\":\"en\",\"value\":\"CWE-303\"}]}],\"references\":[{\"url\":\"https://datatracker.ietf.org/doc/html/rfc5802\",\"source\":\"security@apache.org\"},{\"url\":\"https://datatracker.ietf.org/doc/html/rfc5802#section-9\",\"source\":\"security@apache.org\"},{\"url\":\"https://kafka.apache.org/documentation/#security_sasl_scram_security\",\"source\":\"security@apache.org\"},{\"url\":\"https://lists.apache.org/thread/84dh4so32lwn7wr6c5s9mwh381vx9wkw\",\"source\":\"security@apache.org\"},{\"url\":\"http://www.openwall.com/lists/oss-security/2024/12/18/3\",\"source\":\"af854a3a-2127-422b-91ae-364da2661108\"}]}}",
      vulnrichment: {
         containers: "{\"adp\": [{\"title\": \"CVE Program Container\", \"references\": [{\"url\": \"http://www.openwall.com/lists/oss-security/2024/12/18/3\"}], \"providerMetadata\": {\"orgId\": \"af854a3a-2127-422b-91ae-364da2661108\", \"shortName\": \"CVE\", \"dateUpdated\": \"2024-12-18T17:02:47.926Z\"}}, {\"title\": \"CISA ADP Vulnrichment\", \"metrics\": [{\"cvssV3_1\": {\"scope\": \"UNCHANGED\", \"version\": \"3.1\", \"baseScore\": 5.3, \"attackVector\": \"NETWORK\", \"baseSeverity\": \"MEDIUM\", \"vectorString\": \"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N\", \"integrityImpact\": \"NONE\", \"userInteraction\": \"NONE\", \"attackComplexity\": \"LOW\", \"availabilityImpact\": \"NONE\", \"privilegesRequired\": \"NONE\", \"confidentialityImpact\": \"LOW\"}}, {\"other\": {\"type\": \"ssvc\", \"content\": {\"id\": \"CVE-2024-56128\", \"role\": \"CISA Coordinator\", \"options\": [{\"Exploitation\": \"none\"}, {\"Automatable\": \"no\"}, {\"Technical Impact\": \"partial\"}], \"version\": \"2.0.3\", \"timestamp\": \"2024-12-18T16:15:35.208336Z\"}}}], \"providerMetadata\": {\"orgId\": \"134c704f-9b21-4f2e-91b3-4a467353bcc0\", \"shortName\": \"CISA-ADP\", \"dateUpdated\": \"2024-12-18T16:15:44.224Z\"}}], \"cna\": {\"title\": \"Apache Kafka: SCRAM authentication vulnerable to replay attacks when used without encryption\", \"source\": {\"discovery\": \"EXTERNAL\"}, \"credits\": [{\"lang\": \"en\", \"type\": \"finder\", \"value\": \"Tim Fox (timvolpe@gmail.com)\"}, {\"lang\": \"en\", \"type\": \"remediation developer\", \"value\": \"Vikas Singh <vikas@confluent.io>\"}], \"metrics\": [{\"other\": {\"type\": \"Textual description of severity\", \"content\": {\"text\": \"low\"}}}], \"affected\": [{\"vendor\": \"Apache Software Foundation\", \"product\": \"Apache Kafka\", \"versions\": [{\"status\": \"affected\", \"version\": \"0.10.2.0\", \"lessThan\": \"3.7.2\", \"versionType\": \"semver\"}, {\"status\": \"affected\", \"version\": \"3.8.0\", \"versionType\": \"semver\"}], \"defaultStatus\": \"unaffected\"}], \"references\": [{\"url\": \"https://datatracker.ietf.org/doc/html/rfc5802\", \"tags\": [\"related\"]}, {\"url\": \"https://datatracker.ietf.org/doc/html/rfc5802#section-9\", \"tags\": [\"related\"]}, {\"url\": \"https://kafka.apache.org/documentation/#security_sasl_scram_security\"}, {\"url\": \"https://lists.apache.org/thread/84dh4so32lwn7wr6c5s9mwh381vx9wkw\", \"tags\": [\"vendor-advisory\"]}], \"x_generator\": {\"engine\": \"Vulnogram 0.2.0\"}, \"descriptions\": [{\"lang\": \"en\", \"value\": \"Incorrect Implementation of Authentication Algorithm in Apache Kafka's SCRAM implementation.\\n\\nIssue Summary:\\nApache Kafka's implementation of the Salted Challenge Response Authentication Mechanism (SCRAM) did not fully adhere to the requirements of RFC 5802 [1].\\nSpecifically, as per RFC 5802, the server must verify that the nonce sent by the client in the second message matches the nonce sent by the server in its first message.\\nHowever, Kafka's SCRAM implementation did not perform this validation.\\n\\nImpact:\\nThis vulnerability is exploitable only when an attacker has plaintext access to the SCRAM authentication exchange. However, the usage of SCRAM over plaintext is strongly\\ndiscouraged as it is considered an insecure practice [2]. Apache Kafka recommends deploying SCRAM exclusively with TLS encryption to protect SCRAM exchanges from interception [3].\\nDeployments using SCRAM with TLS are not affected by this issue.\\n\\nHow to Detect If You Are Impacted:\\nIf your deployment uses SCRAM authentication over plaintext communication channels (without TLS encryption), you are likely impacted.\\nTo check if TLS is enabled, review your server.properties configuration file for listeners property. If you have SASL_PLAINTEXT in the listeners, then you are likely impacted.\\n\\nFix Details:\\nThe issue has been addressed by introducing nonce verification in the final message of the SCRAM authentication exchange to ensure compliance with RFC 5802.\\n\\nAffected Versions:\\nApache Kafka versions 0.10.2.0 through 3.9.0, excluding the fixed versions below.\\n\\nFixed Versions:\\n3.9.0\\n3.8.1\\n3.7.2\\n\\nUsers are advised to upgrade to 3.7.2 or later to mitigate this issue.\\n\\nRecommendations for Mitigation:\\nUsers unable to upgrade to the fixed versions can mitigate the issue by:\\n- Using TLS with SCRAM Authentication:\\nAlways deploy SCRAM over TLS to encrypt authentication exchanges and protect against interception.\\n- Considering Alternative Authentication Mechanisms:\\nEvaluate alternative authentication mechanisms, such as PLAIN, Kerberos or OAuth with TLS, which provide additional layers of security.\", \"supportingMedia\": [{\"type\": \"text/html\", \"value\": \"<p>Incorrect Implementation of Authentication Algorithm in Apache Kafka's SCRAM implementation.<br><br>Issue Summary:<br>Apache Kafka's implementation of the Salted Challenge Response Authentication Mechanism (SCRAM) did not fully adhere to the requirements of RFC 5802 [1].<br>Specifically, as per RFC 5802, the server must verify that the nonce sent by the client in the second message matches the nonce sent by the server in its first message.<br>However, Kafka's SCRAM implementation did not perform this validation.<br><br>Impact:<br>This vulnerability is exploitable only when an attacker has plaintext access to the SCRAM authentication exchange. However, the usage of SCRAM over plaintext is strongly<br>discouraged as it is considered an insecure practice [2]. Apache Kafka recommends deploying SCRAM exclusively with TLS encryption to protect SCRAM exchanges from interception [3].<br>Deployments using SCRAM with TLS are not affected by this issue.</p>How to Detect If You Are Impacted:<br>If your deployment uses SCRAM authentication over plaintext communication channels (without TLS encryption), you are likely impacted.<br>To check if TLS is enabled, review your server.properties configuration file for listeners property. If you have SASL_PLAINTEXT in the listeners, then you are likely impacted.<br><br><span style=\\\"background-color: var(--wht);\\\">Fix Details:<br></span><span style=\\\"background-color: var(--wht);\\\">The issue has been addressed by introducing nonce verification in the final message of the SCRAM authentication exchange to ensure compliance with RFC 5802.<br><br></span><span style=\\\"background-color: var(--wht);\\\">Affected Versions:<br></span><span style=\\\"background-color: var(--wht);\\\">Apache Kafka versions 0.10.2.0 through 3.9.0, excluding the fixed versions below.<br><br></span><span style=\\\"background-color: var(--wht);\\\">Fixed Versions:<br></span><span style=\\\"background-color: var(--wht);\\\">3.9.0<br></span><span style=\\\"background-color: var(--wht);\\\">3.8.1<br></span><span style=\\\"background-color: var(--wht);\\\">3.7.2<br><br></span><span style=\\\"background-color: var(--wht);\\\">Users are advised to upgrade to 3.7.2 or later to mitigate this issue.<br><br></span><span style=\\\"background-color: var(--wht);\\\">Recommendations for Mitigation:<br></span><span style=\\\"background-color: var(--wht);\\\">Users unable to upgrade to the fixed versions can mitigate the issue by:<br></span><span style=\\\"background-color: var(--wht);\\\">- Using TLS with SCRAM Authentication:<br></span><span style=\\\"background-color: var(--wht);\\\">Always deploy SCRAM over TLS to encrypt authentication exchanges and protect against interception.<br></span><span style=\\\"background-color: var(--wht);\\\">- Considering Alternative Authentication Mechanisms:<br></span><span style=\\\"background-color: var(--wht);\\\">Evaluate alternative authentication mechanisms, such as PLAIN, Kerberos or OAuth with TLS, which provide additional layers of security.</span><br>\", \"base64\": false}]}], \"problemTypes\": [{\"descriptions\": [{\"lang\": \"en\", \"type\": \"CWE\", \"cweId\": \"CWE-303\", \"description\": \"CWE-303 Incorrect Implementation of Authentication Algorithm\"}]}], \"providerMetadata\": {\"orgId\": \"f0158376-9dc2-43b6-827c-5f631a4d8d09\", \"shortName\": \"apache\", \"dateUpdated\": \"2024-12-18T13:38:03.068Z\"}}}",
         cveMetadata: "{\"cveId\": \"CVE-2024-56128\", \"state\": \"PUBLISHED\", \"dateUpdated\": \"2024-12-18T17:02:47.926Z\", \"dateReserved\": \"2024-12-16T14:52:48.326Z\", \"assignerOrgId\": \"f0158376-9dc2-43b6-827c-5f631a4d8d09\", \"datePublished\": \"2024-12-18T13:38:03.068Z\", \"assignerShortName\": \"apache\"}",
         dataType: "CVE_RECORD",
         dataVersion: "5.1",
      },
   },
}

ghsa-p7c9-8xx8-h74f

Vulnerability from github

Published

2024-12-18 15:33

Modified

2024-12-18 19:16

Severity ?

5.3 (Medium) - CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
1.7 (Low) - CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N/E:U

Summary

Apache Kafka's SCRAM implementation Incorrectly Implements Authentication Algorithm

Details

Incorrect Implementation of Authentication Algorithm in Apache Kafka's SCRAM implementation.

Issue Summary: Apache Kafka's implementation of the Salted Challenge Response Authentication Mechanism (SCRAM) did not fully adhere to the requirements of RFC 5802 [1]. Specifically, as per RFC 5802, the server must verify that the nonce sent by the client in the second message matches the nonce sent by the server in its first message. However, Kafka's SCRAM implementation did not perform this validation.

Impact: This vulnerability is exploitable only when an attacker has plaintext access to the SCRAM authentication exchange. However, the usage of SCRAM over plaintext is strongly discouraged as it is considered an insecure practice [2]. Apache Kafka recommends deploying SCRAM exclusively with TLS encryption to protect SCRAM exchanges from interception [3]. Deployments using SCRAM with TLS are not affected by this issue.

How to Detect If You Are Impacted: If your deployment uses SCRAM authentication over plaintext communication channels (without TLS encryption), you are likely impacted. To check if TLS is enabled, review your server.properties configuration file for listeners property. If you have SASL_PLAINTEXT in the listeners, then you are likely impacted.

Fix Details: The issue has been addressed by introducing nonce verification in the final message of the SCRAM authentication exchange to ensure compliance with RFC 5802.

Affected Versions: Apache Kafka versions 0.10.2.0 through 3.9.0, excluding the fixed versions below.

Fixed Versions: 3.9.0 3.8.1 3.7.2

Users are advised to upgrade to 3.7.2 or later to mitigate this issue.

Recommendations for Mitigation: Users unable to upgrade to the fixed versions can mitigate the issue by: - Using TLS with SCRAM Authentication: Always deploy SCRAM over TLS to encrypt authentication exchanges and protect against interception. - Considering Alternative Authentication Mechanisms: Evaluate alternative authentication mechanisms, such as PLAIN, Kerberos or OAuth with TLS, which provide additional layers of security.

Show details on source website

JSON

To clipboard

{
   affected: [
      {
         package: {
            ecosystem: "Maven",
            name: "org.apache.kafka:kafka",
         },
         ranges: [
            {
               events: [
                  {
                     introduced: "0.10.2.0",
                  },
                  {
                     fixed: "3.7.2",
                  },
               ],
               type: "ECOSYSTEM",
            },
         ],
      },
      {
         package: {
            ecosystem: "Maven",
            name: "org.apache.kafka:kafka",
         },
         ranges: [
            {
               events: [
                  {
                     introduced: "3.8.0",
                  },
                  {
                     fixed: "3.8.1",
                  },
               ],
               type: "ECOSYSTEM",
            },
         ],
         versions: [
            "3.8.0",
         ],
      },
   ],
   aliases: [
      "CVE-2024-56128",
   ],
   database_specific: {
      cwe_ids: [
         "CWE-303",
      ],
      github_reviewed: true,
      github_reviewed_at: "2024-12-18T19:16:18Z",
      nvd_published_at: "2024-12-18T14:15:23Z",
      severity: "LOW",
   },
   details: "Incorrect Implementation of Authentication Algorithm in Apache Kafka's SCRAM implementation.\n\nIssue Summary:\nApache Kafka's implementation of the Salted Challenge Response Authentication Mechanism (SCRAM) did not fully adhere to the requirements of RFC 5802 [1].\nSpecifically, as per RFC 5802, the server must verify that the nonce sent by the client in the second message matches the nonce sent by the server in its first message.\nHowever, Kafka's SCRAM implementation did not perform this validation.\n\nImpact:\nThis vulnerability is exploitable only when an attacker has plaintext access to the SCRAM authentication exchange. However, the usage of SCRAM over plaintext is strongly discouraged as it is considered an insecure practice [2]. Apache Kafka recommends deploying SCRAM exclusively with TLS encryption to protect SCRAM exchanges from interception [3].\nDeployments using SCRAM with TLS are not affected by this issue.\n\nHow to Detect If You Are Impacted:\nIf your deployment uses SCRAM authentication over plaintext communication channels (without TLS encryption), you are likely impacted.\nTo check if TLS is enabled, review your server.properties configuration file for listeners property. If you have SASL_PLAINTEXT in the listeners, then you are likely impacted.\n\nFix Details:\nThe issue has been addressed by introducing nonce verification in the final message of the SCRAM authentication exchange to ensure compliance with RFC 5802.\n\nAffected Versions:\nApache Kafka versions 0.10.2.0 through 3.9.0, excluding the fixed versions below.\n\nFixed Versions:\n3.9.0\n3.8.1\n3.7.2\n\nUsers are advised to upgrade to 3.7.2 or later to mitigate this issue.\n\nRecommendations for Mitigation:\nUsers unable to upgrade to the fixed versions can mitigate the issue by:\n- Using TLS with SCRAM Authentication:\nAlways deploy SCRAM over TLS to encrypt authentication exchanges and protect against interception.\n- Considering Alternative Authentication Mechanisms:\nEvaluate alternative authentication mechanisms, such as PLAIN, Kerberos or OAuth with TLS, which provide additional layers of security.",
   id: "GHSA-p7c9-8xx8-h74f",
   modified: "2024-12-18T19:16:18Z",
   published: "2024-12-18T15:33:00Z",
   references: [
      {
         type: "ADVISORY",
         url: "https://nvd.nist.gov/vuln/detail/CVE-2024-56128",
      },
      {
         type: "WEB",
         url: "https://github.com/apache/kafka/commit/2cbc5bd3ca22185d9cd357c9db23a2cfb43a0fff",
      },
      {
         type: "WEB",
         url: "https://datatracker.ietf.org/doc/html/rfc5802",
      },
      {
         type: "WEB",
         url: "https://datatracker.ietf.org/doc/html/rfc5802#section-9",
      },
      {
         type: "PACKAGE",
         url: "https://github.com/apache/kafka",
      },
      {
         type: "WEB",
         url: "https://kafka.apache.org/documentation/#security_sasl_scram_security",
      },
      {
         type: "WEB",
         url: "https://lists.apache.org/thread/84dh4so32lwn7wr6c5s9mwh381vx9wkw",
      },
      {
         type: "WEB",
         url: "http://www.openwall.com/lists/oss-security/2024/12/18/3",
      },
   ],
   schema_version: "1.4.0",
   severity: [
      {
         score: "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N",
         type: "CVSS_V3",
      },
      {
         score: "CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N/E:U",
         type: "CVSS_V4",
      },
   ],
   summary: "Apache Kafka's SCRAM implementation Incorrectly Implements Authentication Algorithm",
}

fkie_cve-2024-56128

Vulnerability from fkie_nvd

Published

2024-12-18 14:15

Modified

2024-12-18 17:15

Severity ?

5.3 (Medium) - CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N

Summary

References

▼	URL	Tags
	security@apache.org	https://datatracker.ietf.org/doc/html/rfc5802
	security@apache.org	https://datatracker.ietf.org/doc/html/rfc5802#section-9
	security@apache.org	https://kafka.apache.org/documentation/#security_sasl_scram_security
	security@apache.org	https://lists.apache.org/thread/84dh4so32lwn7wr6c5s9mwh381vx9wkw
	af854a3a-2127-422b-91ae-364da2661108	http://www.openwall.com/lists/oss-security/2024/12/18/3

Impacted products

	Vendor	Product	Version

JSON

To clipboard

{
   cveTags: [],
   descriptions: [
      {
         lang: "en",
         value: "Incorrect Implementation of Authentication Algorithm in Apache Kafka's SCRAM implementation.\n\nIssue Summary:\nApache Kafka's implementation of the Salted Challenge Response Authentication Mechanism (SCRAM) did not fully adhere to the requirements of RFC 5802 [1].\nSpecifically, as per RFC 5802, the server must verify that the nonce sent by the client in the second message matches the nonce sent by the server in its first message.\nHowever, Kafka's SCRAM implementation did not perform this validation.\n\nImpact:\nThis vulnerability is exploitable only when an attacker has plaintext access to the SCRAM authentication exchange. However, the usage of SCRAM over plaintext is strongly\ndiscouraged as it is considered an insecure practice [2]. Apache Kafka recommends deploying SCRAM exclusively with TLS encryption to protect SCRAM exchanges from interception [3].\nDeployments using SCRAM with TLS are not affected by this issue.\n\nHow to Detect If You Are Impacted:\nIf your deployment uses SCRAM authentication over plaintext communication channels (without TLS encryption), you are likely impacted.\nTo check if TLS is enabled, review your server.properties configuration file for listeners property. If you have SASL_PLAINTEXT in the listeners, then you are likely impacted.\n\nFix Details:\nThe issue has been addressed by introducing nonce verification in the final message of the SCRAM authentication exchange to ensure compliance with RFC 5802.\n\nAffected Versions:\nApache Kafka versions 0.10.2.0 through 3.9.0, excluding the fixed versions below.\n\nFixed Versions:\n3.9.0\n3.8.1\n3.7.2\n\nUsers are advised to upgrade to 3.7.2 or later to mitigate this issue.\n\nRecommendations for Mitigation:\nUsers unable to upgrade to the fixed versions can mitigate the issue by:\n- Using TLS with SCRAM Authentication:\nAlways deploy SCRAM over TLS to encrypt authentication exchanges and protect against interception.\n- Considering Alternative Authentication Mechanisms:\nEvaluate alternative authentication mechanisms, such as PLAIN, Kerberos or OAuth with TLS, which provide additional layers of security.",
      },
      {
         lang: "es",
         value: "Implementación incorrecta del algoritmo de autenticación en la implementación SCRAM de Apache Kafka. Resumen del problema: La implementación de Apache Kafka del mecanismo de autenticación de respuesta a desafío con sal (SCRAM) no se adhirió completamente a los requisitos de RFC 5802 [1]. Específicamente, según RFC 5802, el servidor debe verificar que el nonce enviado por el cliente en el segundo mensaje coincida con el nonce enviado por el servidor en su primer mensaje. Sin embargo, la implementación SCRAM de Kafka no realizó esta validación. Impacto: Esta vulnerabilidad es explotable solo cuando un atacante tiene acceso de texto simple al intercambio de autenticación SCRAM. Sin embargo, el uso de SCRAM sobre texto simple se desaconseja enfáticamente ya que se considera una práctica insegura [2]. Apache Kafka recomienda implementar SCRAM exclusivamente con cifrado TLS para proteger los intercambios SCRAM de la intercepción [3]. Las implementaciones que utilizan SCRAM con TLS no se ven afectadas por este problema. Cómo detectar si está afectado: si su implementación utiliza autenticación SCRAM sobre canales de comunicación de texto plano (sin cifrado TLS), es probable que esté afectado. Para verificar si TLS está habilitado, revise su archivo de configuración server.properties para la propiedad listeners. Si tiene SASL_PLAINTEXT en los listeners, es probable que esté afectado. Detalles de la solución: el problema se ha solucionado introduciendo la verificación de nonce en el mensaje final del intercambio de autenticación SCRAM para garantizar el cumplimiento de RFC 5802. Versiones afectadas: Apache Kafka versiones 0.10.2.0 a 3.9.0, excluidas las versiones corregidas a continuación. Versiones corregidas: 3.9.0 3.8.1 3.7.2 Se recomienda a los usuarios que actualicen a 3.7.2 o posterior para mitigar este problema. Recomendaciones para la mitigación: los usuarios que no puedan actualizar a las versiones corregidas pueden mitigar el problema mediante lo siguiente: - Uso de TLS con autenticación SCRAM: siempre implemente SCRAM sobre TLS para cifrar los intercambios de autenticación y protegerse contra la interceptación. - Consideración de mecanismos de autenticación alternativos: evaluar mecanismos de autenticación alternativos, como PLAIN, Kerberos u OAuth con TLS, que proporcionan capas adicionales de seguridad.",
      },
   ],
   id: "CVE-2024-56128",
   lastModified: "2024-12-18T17:15:15.003",
   metrics: {
      cvssMetricV31: [
         {
            cvssData: {
               attackComplexity: "LOW",
               attackVector: "NETWORK",
               availabilityImpact: "NONE",
               baseScore: 5.3,
               baseSeverity: "MEDIUM",
               confidentialityImpact: "LOW",
               integrityImpact: "NONE",
               privilegesRequired: "NONE",
               scope: "UNCHANGED",
               userInteraction: "NONE",
               vectorString: "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N",
               version: "3.1",
            },
            exploitabilityScore: 3.9,
            impactScore: 1.4,
            source: "134c704f-9b21-4f2e-91b3-4a467353bcc0",
            type: "Secondary",
         },
      ],
   },
   published: "2024-12-18T14:15:23.277",
   references: [
      {
         source: "security@apache.org",
         url: "https://datatracker.ietf.org/doc/html/rfc5802",
      },
      {
         source: "security@apache.org",
         url: "https://datatracker.ietf.org/doc/html/rfc5802#section-9",
      },
      {
         source: "security@apache.org",
         url: "https://kafka.apache.org/documentation/#security_sasl_scram_security",
      },
      {
         source: "security@apache.org",
         url: "https://lists.apache.org/thread/84dh4so32lwn7wr6c5s9mwh381vx9wkw",
      },
      {
         source: "af854a3a-2127-422b-91ae-364da2661108",
         url: "http://www.openwall.com/lists/oss-security/2024/12/18/3",
      },
   ],
   sourceIdentifier: "security@apache.org",
   vulnStatus: "Awaiting Analysis",
   weaknesses: [
      {
         description: [
            {
               lang: "en",
               value: "CWE-303",
            },
         ],
         source: "security@apache.org",
         type: "Secondary",
      },
   ],
}

wid-sec-w-2024-3725

Vulnerability from csaf_certbund

Published

2024-12-18 23:00

Modified

2024-12-18 23: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

- Sonstiges

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ü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.",
         },
         {
            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: "- Sonstiges",
            title: "Betroffene Betriebssysteme",
         },
      ],
      publisher: {
         category: "other",
         contact_details: "csaf-provider@cert-bund.de",
         name: "Bundesamt für Sicherheit in der Informationstechnik",
         namespace: "https://www.bsi.bund.de",
      },
      references: [
         {
            category: "self",
            summary: "WID-SEC-W-2024-3725 - CSAF Version",
            url: "https://wid.cert-bund.de/.well-known/csaf/white/2024/wid-sec-w-2024-3725.json",
         },
         {
            category: "self",
            summary: "WID-SEC-2024-3725 - Portal Version",
            url: "https://wid.cert-bund.de/portal/wid/securityadvisory?name=WID-SEC-2024-3725",
         },
         {
            category: "external",
            summary: "Red Hat Bugtracker #2333013 vom 2024-12-18",
            url: "https://bugzilla.redhat.com/show_bug.cgi?id=2333013",
         },
         {
            category: "external",
            summary: "GitHub Advisory Database vom 2024-12-18",
            url: "https://github.com/advisories/GHSA-p7c9-8xx8-h74f",
         },
      ],
      source_lang: "en-US",
      title: "Apache Kafka: Schwachstelle ermöglicht Umgehen von Sicherheitsvorkehrungen",
      tracking: {
         current_release_date: "2024-12-18T23:00:00.000+00:00",
         generator: {
            date: "2024-12-19T09:12:23.978+00:00",
            engine: {
               name: "BSI-WID",
               version: "1.3.10",
            },
         },
         id: "WID-SEC-W-2024-3725",
         initial_release_date: "2024-12-18T23:00:00.000+00:00",
         revision_history: [
            {
               date: "2024-12-18T23:00:00.000+00:00",
               number: "1",
               summary: "Initiale Fassung",
            },
         ],
         status: "final",
         version: "1",
      },
   },
   product_tree: {
      branches: [
         {
            branches: [
               {
                  branches: [
                     {
                        category: "product_version_range",
                        name: "<3.7.2",
                        product: {
                           name: "Apache Kafka <3.7.2",
                           product_id: "T039930",
                        },
                     },
                     {
                        category: "product_version",
                        name: "3.7.2",
                        product: {
                           name: "Apache Kafka 3.7.2",
                           product_id: "T039930-fixed",
                           product_identification_helper: {
                              cpe: "cpe:/a:apache:kafka:3.7.2",
                           },
                        },
                     },
                     {
                        category: "product_version_range",
                        name: "<3.8.1",
                        product: {
                           name: "Apache Kafka <3.8.1",
                           product_id: "T039931",
                        },
                     },
                     {
                        category: "product_version",
                        name: "3.8.1",
                        product: {
                           name: "Apache Kafka 3.8.1",
                           product_id: "T039931-fixed",
                           product_identification_helper: {
                              cpe: "cpe:/a:apache:kafka:3.8.1",
                           },
                        },
                     },
                  ],
                  category: "product_name",
                  name: "Kafka",
               },
            ],
            category: "vendor",
            name: "Apache",
         },
      ],
   },
   vulnerabilities: [
      {
         cve: "CVE-2024-56128",
         notes: [
            {
               category: "description",
               text: "Es besteht eine Schwachstelle in Apache Kafka. Diese Schwachstelle betrifft die Implementierung des Salted Challenge Response Authentication Mechanism (SCRAM) aufgrund einer unsachgemäßen Eingabevalidierung. Ein entfernter, anonymer Angreifer kann diese Schwachstelle ausnutzen, um die Authentifizierung zu umgehen. Die Ausnutzung dieser Schwachstelle erfordert eine SCRAM-Authentifizierung über Klartextkommunikation und den Zugriff des Angreifers auf den abgefangenen Authentifizierungsaustausch.",
            },
         ],
         product_status: {
            known_affected: [
               "T039931",
               "T039930",
            ],
         },
         release_date: "2024-12-18T23:00:00.000+00:00",
         title: "CVE-2024-56128",
      },
   ],
}

All sightings related to this event Export sightings related to this event

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.

Action not permitted

cve-2024-56128

Vulnerability from cvelistv5

ghsa-p7c9-8xx8-h74f

Vulnerability from github

fkie_cve-2024-56128

Vulnerability from fkie_nvd

wid-sec-w-2024-3725

Vulnerability from csaf_certbund

Tags

Sightings

Nomenclature