2

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

Deferred
AliasesGHSA-c2g2-gx4j-rj3jPYSEC-2026-1913
Published 31-05-2024Last modified 02-08-2024

Vulnerability summary

CVE-2024-35196 is a low (CVSS 2.0) vulnerability in getsentry sentry. EPSS estimates a 0.57% chance of exploitation in the next 30 days, higher than 47.4% of scored vulnerabilities.

Priority
Routine

Not severe (CVSS 2, network access); no exploitation reported by the 5 checked sources

Source freshness unavailable

How is this decided?
CVSS score
2.0/10
010
Low · v3.1 (CVE.org)
EPSS score
0.57%
0%100%
Low · 0.00 pp in 30 days
KEVNot listedNot listed by any tracked catalog.
RansomwareNot flaggedNo ransomware use recorded.
Public exploits0No public exploits recorded

Timeline

  1. 31-05-2024
    PublishedVulnerability first disclosed.
  2. 02-08-2024
    Last modifiedVulnerability information updated.

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 metrics

3 scores · 3 sources · 1 version

EPSS trend

Probability

0.57%

Chance of exploitation in the next 30 days

Percentile

47%

Versus all other CVEs

30-day change

No change 0.00 pp

From 0.57% on 04-10-2026

04-10-202603-11-2026

Known exploited

Compare KEV catalogs
CISA KEV

Not in the CISA KEV catalog.

ENISA CNW

Not in the ENISA CNW catalog.

CIRCL

Not in the CIRCL catalog.

Public exploits

0 found

No public exploits indexed.

Weaknesses

CWE · root cause

Affected systems

Version check

Known conditions: network-reachable, administrative account, user interaction (CVSS vector). Other conditions: not stated in public data.

Getsentry1 product
PyPI1 product
  • sentry≥ 24.3.0, < 24.5.0

2 vendors · 2 products

References

11 links
Show all 11 references