{"cve":"CVE-2024-35196","nvd":{"published":"2024-05-31T18:15:12.993","modified":"2026-06-17T07:34:31.340","status":"Deferred","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.**","cvss_v4":null,"cvss_v3":{"version":"3.1","vector":"CVSS:3.1/AV:N/AC:H/PR:H/UI:R/S:U/C:L/I:N/A:N","score":2.0},"cwes":["CWE-532"],"references":["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"],"products":[],"source":"nvd","synced_at":"2026-10-19T21:51:20.603330631+00:00"},"epss":{"cve":"CVE-2024-35196","score":0.00575,"percentile":0.47469,"date":"2026-10-31"},"kev":null,"osv":[{"id":"GHSA-c2g2-gx4j-rj3j","url":"https://osv.dev/vulnerability/GHSA-c2g2-gx4j-rj3j","summary":"Slack integration leaks sensitive information in logs","modified":"2026-07-07T17:57:24.563277777Z","packages":[{"ecosystem":"PyPI","name":"sentry","purl":"pkg:pypi/sentry","ranges":[">=24.3.0 <24.5.0"],"fixed":["24.5.0"]}]},{"id":"PYSEC-2026-1913","url":"https://osv.dev/vulnerability/PYSEC-2026-1913","summary":"Slack integration leaks sensitive information in logs","modified":"2026-07-07T17:48:09.564063430Z","packages":[{"ecosystem":"PyPI","name":"sentry","purl":"pkg:pypi/sentry","ranges":[">=24.3.0 <24.5.0"],"fixed":["24.5.0"]}]}],"attribution":["This product uses the NVD API but is not endorsed or certified by the NVD.","EPSS scores: FIRST Exploit Prediction Scoring System, https://www.first.org/epss","Known exploited vulnerabilities: CISA Known Exploited Vulnerabilities Catalog, https://www.cisa.gov/known-exploited-vulnerabilities-catalog","Package advisories: OSV (https://osv.dev), from the GitHub Advisory Database, PyPA, Go, RustSec and other ecosystem databases, under CC-BY 4.0 or CC0","CVE records: the CVE Program's CVE List (https://www.cve.org), under its terms of use (https://www.cve.org/Legal/TermsOfUse). CVE is a registered trademark of The MITRE Corporation; this product is not affiliated with the CVE Program."]}