CVE-2024-35196

{"id": "CVE-2024-35196", "metrics": {"cvssMetricV31": [{"type": "Secondary", "source": "security-advisories@github.com", "cvssData": {"scope": "UNCHANGED", "version": "3.1", "baseScore": 2.0, "attackVector": "NETWORK", "baseSeverity": "LOW", "vectorString": "CVSS:3.1/AV:N/AC:H/PR:H/UI:R/S:U/C:L/I:N/A:N", "integrityImpact": "NONE", "userInteraction": "REQUIRED", "attackComplexity": "HIGH", "availabilityImpact": "NONE", "privilegesRequired": "HIGH", "confidentialityImpact": "LOW"}, "impactScore": 1.4, "exploitabilityScore": 0.5}]}, "published": "2024-05-31T18:15:12.993", "references": [{"url": "https://api.slack.com/authentication/verifying-requests-from-slack#app-management-updates", "source": "security-advisories@github.com"}, {"url": "https://api.slack.com/authentication/verifying-requests-from-slack#deprecation", "source": "security-advisories@github.com"}, {"url": "https://api.slack.com/authentication/verifying-requests-from-slack#regenerating", "source": "security-advisories@github.com"}, {"url": "https://develop.sentry.dev/integrations/slack", "source": "security-advisories@github.com"}, {"url": "https://github.com/getsentry/sentry/blob/17d2b87e39ccd57e11da4deed62971ff306253d1/src/sentry/conf/server.py#L1307", "source": "security-advisories@github.com"}, {"url": "https://github.com/getsentry/sentry/pull/70508", "source": "security-advisories@github.com"}, {"url": "https://github.com/getsentry/sentry/security/advisories/GHSA-c2g2-gx4j-rj3j", "source": "security-advisories@github.com"}, {"url": "https://api.slack.com/authentication/verifying-requests-from-slack#app-management-updates", "source": "af854a3a-2127-422b-91ae-364da2661108"}, {"url": "https://api.slack.com/authentication/verifying-requests-from-slack#deprecation", "source": "af854a3a-2127-422b-91ae-364da2661108"}, {"url": "https://api.slack.com/authentication/verifying-requests-from-slack#regenerating", "source": "af854a3a-2127-422b-91ae-364da2661108"}, {"url": "https://develop.sentry.dev/integrations/slack", "source": "af854a3a-2127-422b-91ae-364da2661108"}, {"url": "https://github.com/getsentry/sentry/blob/17d2b87e39ccd57e11da4deed62971ff306253d1/src/sentry/conf/server.py#L1307", "source": "af854a3a-2127-422b-91ae-364da2661108"}, {"url": "https://github.com/getsentry/sentry/pull/70508", "source": "af854a3a-2127-422b-91ae-364da2661108"}, {"url": "https://github.com/getsentry/sentry/security/advisories/GHSA-c2g2-gx4j-rj3j", "source": "af854a3a-2127-422b-91ae-364da2661108"}], "vulnStatus": "Awaiting Analysis", "weaknesses": [{"type": "Secondary", "source": "security-advisories@github.com", "description": [{"lang": "en", "value": "CWE-532"}]}], "descriptions": [{"lang": "en", "value": "Sentry is a developer-first error tracking and performance monitoring platform. Sentry's Slack integration incorrectly records the incoming request body in logs. This request data can contain sensitive information, including the deprecated Slack verification token. With this verification token, it is possible under specific configurations, an attacker can forge requests and act as the Slack integration. The request body is leaked in log entries matching `event == \"slack.*\" && name == \"sentry.integrations.slack\" && request_data == *`. The deprecated slack verification token, will be found in the `request_data.token` key. **SaaS users** do not need to take any action. **Self-hosted users** should upgrade to version 24.5.0 or higher, rotate their Slack verification token, and use the Slack Signing Secret instead of the verification token. For users only using the `slack.signing-secret` in their self-hosted configuration, the legacy verification token is not used to verify the webhook payload. It is ignored. Users unable to upgrade should either set the `slack.signing-secret` instead of `slack.verification-token`. The signing secret is Slack's recommended way of authenticating webhooks. By having `slack.singing-secret` set, Sentry self-hosted will no longer use the verification token for authentication of the webhooks, regardless of whether `slack.verification-token` is set or not. Alternatively if the self-hosted instance is unable to be upgraded or re-configured to use the `slack.signing-secret`, the logging configuration can be adjusted to not generate logs from the integration. The default logging configuration can be found in `src/sentry/conf/server.py`. **Services should be restarted once the configuration change is saved.**\n"}, {"lang": "es", "value": "Sentry es una plataforma de seguimiento de errores y supervisi\u00f3n del rendimiento orientada a los desarrolladores. La integraci\u00f3n de Sentry con Slack registra incorrectamente el cuerpo de la solicitud entrante en los registros. Los datos de esta solicitud pueden contener informaci\u00f3n confidencial, incluido el token de verificaci\u00f3n de Slack obsoleto. Con este token de verificaci\u00f3n, es posible que, en configuraciones espec\u00edficas, un atacante pueda falsificar solicitudes y actuar como integraci\u00f3n de Slack. El cuerpo de la solicitud se filtra en las entradas del registro que coinciden con `event == \"slack.*\" && name == \"sentry.integrations.slack\" && request_data == *`. El token de verificaci\u00f3n de holgura obsoleto se encontrar\u00e1 en la clave `request_data.token`. **Los usuarios de SaaS** no necesitan realizar ninguna acci\u00f3n. **Los usuarios autohospedados** deben actualizar a la versi\u00f3n 24.5.0 o superior, rotar su token de verificaci\u00f3n de Slack y usar el secreto de firma de Slack en lugar del token de verificaci\u00f3n. Para los usuarios que solo usan `slack.signing-secret` en su configuraci\u00f3n autohospedada, el token de verificaci\u00f3n heredado no se usa para verificar la carga \u00fatil del webhook. Se ignora. Los usuarios que no puedan actualizar deben configurar `slack.signing-secret` en lugar de `slack.verification-token`. El secreto de firma es la forma recomendada por Slack de autenticar webhooks. Al tener configurado `slack.singing-secret`, Sentry autohospedado ya no usar\u00e1 el token de verificaci\u00f3n para la autenticaci\u00f3n de los webhooks, independientemente de si `slack.verification-token` est\u00e1 configurado o no. Alternativamente, si la instancia autohospedada no se puede actualizar o reconfigurar para usar `slack.signing-secret`, la configuraci\u00f3n de registro se puede ajustar para no generar registros de la integraci\u00f3n. La configuraci\u00f3n de registro predeterminada se puede encontrar en `src/sentry/conf/server.py`. **Los servicios deben reiniciarse una vez que se guarda el cambio de configuraci\u00f3n.**"}], "lastModified": "2024-11-21T09:19:54.650", "sourceIdentifier": "security-advisories@github.com"}