CVE-2025-27817

{
  "id": "CVE-2025-27817",
  "cveTags": [],
  "metrics": {
    "ssvcV203": [
      {
        "source": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
        "ssvcData": {
          "id": "CVE-2025-27817",
          "role": "CISA Coordinator",
          "options": [
            {
              "exploitation": "none"
            },
            {
              "automatable": "yes"
            },
            {
              "technicalImpact": "partial"
            }
          ],
          "version": "2.0.3",
          "timestamp": "2025-06-10T14:17:53.791454Z"
        }
      }
    ],
    "cvssMetricV31": [
      {
        "type": "Secondary",
        "source": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
        "cvssData": {
          "scope": "UNCHANGED",
          "version": "3.1",
          "baseScore": 7.5,
          "attackVector": "NETWORK",
          "baseSeverity": "HIGH",
          "vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N",
          "integrityImpact": "NONE",
          "userInteraction": "NONE",
          "attackComplexity": "LOW",
          "availabilityImpact": "NONE",
          "privilegesRequired": "NONE",
          "confidentialityImpact": "HIGH"
        },
        "impactScore": 3.6,
        "exploitabilityScore": 3.9
      }
    ]
  },
  "affected": [
    {
      "source": "security@apache.org",
      "affectedData": [
        {
          "vendor": "Apache Software Foundation",
          "product": "Apache Kafka Client",
          "versions": [
            {
              "status": "affected",
              "version": "3.1.0",
              "versionType": "semver",
              "lessThanOrEqual": "3.9.0"
            }
          ],
          "defaultStatus": "unaffected"
        }
      ]
    }
  ],
  "published": "2025-06-10T08:15:22.367",
  "references": [
    {
      "url": "https://kafka.apache.org/cve-list",
      "tags": [
        "Vendor Advisory"
      ],
      "source": "security@apache.org"
    },
    {
      "url": "http://www.openwall.com/lists/oss-security/2025/06/09/1",
      "tags": [
        "Mailing List",
        "Third Party Advisory"
      ],
      "source": "af854a3a-2127-422b-91ae-364da2661108"
    }
  ],
  "vulnStatus": "Analyzed",
  "weaknesses": [
    {
      "type": "Secondary",
      "source": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
      "description": [
        {
          "lang": "en",
          "value": "CWE-918"
        }
      ]
    }
  ],
  "descriptions": [
    {
      "lang": "en",
      "value": "A possible arbitrary file read and SSRF vulnerability has been identified in Apache Kafka Client. Apache Kafka Clients accept configuration data for setting the SASL/OAUTHBEARER connection with the brokers, including \"sasl.oauthbearer.token.endpoint.url\" and \"sasl.oauthbearer.jwks.endpoint.url\". Apache Kafka allows clients to read an arbitrary file and return the content in the error log, or sending requests to an unintended location. In applications where Apache Kafka Clients configurations can be specified by an untrusted party, attackers may use the \"sasl.oauthbearer.token.endpoint.url\" and \"sasl.oauthbearer.jwks.endpoint.url\" configuratin to read arbitrary contents of the disk and environment variables or make requests to an unintended location. In particular, this flaw may be used in Apache Kafka Connect to escalate from REST API access to filesystem/environment/URL access, which may be undesirable in certain environments, including SaaS products. \n\nSince Apache Kafka 3.9.1/4.0.0, we have added a system property (\"-Dorg.apache.kafka.sasl.oauthbearer.allowed.urls\") to set the allowed urls in SASL JAAS configuration. In 3.9.1, it accepts all urls by default for backward compatibility. However in 4.0.0 and newer, the default value is empty list and users have to set the allowed urls explicitly."
    },
    {
      "lang": "es",
      "value": "Se ha identificado una posible vulnerabilidad de lectura de archivos arbitrarios y SSRF en el cliente Apache Kafka. Los clientes Apache Kafka aceptan datos de configuración para establecer la conexión SASL/OAUTHBEARER con los brókeres, incluyendo \"sasl.oauthbearer.token.endpoint.url\" y \"sasl.oauthbearer.jwks.endpoint.url\". Apache Kafka permite a los clientes leer un archivo arbitrario y devolver el contenido en el registro de errores, o enviar solicitudes a una ubicación no deseada. En aplicaciones donde las configuraciones de los clientes Apache Kafka pueden ser especificadas por un tercero no confiable, los atacantes pueden usar las configuraciones \"sasl.oauthbearer.token.endpoint.url\" y \"sasl.oauthbearer.jwks.endpoint.url\" para leer contenido arbitrario del disco y las variables de entorno, o realizar solicitudes a una ubicación no deseada. En particular, esta falla puede utilizarse en Apache Kafka Connect para escalar desde el acceso a la API REST al acceso al sistema de archivos, entorno o URL, lo cual puede ser indeseable en ciertos entornos, incluidos los productos SaaS. A partir de Apache Kafka 3.9.1/4.0.0, hemos añadido una propiedad del sistema (\"-Dorg.apache.kafka.sasl.oauthbearer.allowed.urls\") para establecer las URL permitidas en la configuración SASL JAAS. En la versión 3.9.1, acepta todas las URL de forma predeterminada para garantizar la compatibilidad con versiones anteriores. Sin embargo, a partir de la versión 4.0.0, el valor predeterminado es una lista vacía y los usuarios deben configurar las URL permitidas explícitamente."
    }
  ],
  "lastModified": "2026-06-17T09:04:16.300",
  "configurations": [
    {
      "nodes": [
        {
          "negate": false,
          "cpeMatch": [
            {
              "criteria": "cpe:2.3:a:apache:kafka:*:*:*:*:*:*:*:*",
              "vulnerable": true,
              "matchCriteriaId": "4D04AEB9-4727-4A0B-85B2-3DCA8BE63570",
              "versionEndExcluding": "3.9.1",
              "versionStartIncluding": "3.1.0"
            }
          ],
          "operator": "OR"
        }
      ]
    }
  ],
  "sourceIdentifier": "security@apache.org"
}