CVE-2024-35196 Slack integration leaks sensitive information in logs in Sentry
Sentry logs leak Slack verification tokens, allowing attackers to forge requests if using deprecated tokens in self-hosted configurations.
- Exploited in the wild
- Not known
- Login needed
- An administrator
- Attackable
- Over the internet
- Victim action needed
- A user has to click or open something
- Fix
- Available
What is CVE-2024-35196?
CVE-2024-35196 is a low-severity vulnerability in getsentry sentry, published on 31 May 2024. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.
Official 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.**
Weakness: CWE-532
Which versions are affected by CVE-2024-35196?
3 open source packages ship an affected version, including sentry.
| Package | Affected | Fixed in |
|---|---|---|
sentry PyPI | From 24.3.0 | 24.5.0 |
sentry PyPI | From 24.3.0 | 24.5.0 |
sentry PyPI | From 24.3.0 | 24.5.0 |
How do I fix CVE-2024-35196?
Upgrade sentry to 24.5.0 or later.
Is CVE-2024-35196 being exploited?
There is no known exploitation of CVE-2024-35196 in the wild and no public exploit code.
Sources
Also known as GHSA-c2g2-gx4j-rj3j, PYSEC-2026-1913.