CVE-2024-35196: Slack integration leaks sensitive information in logs
Impact 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.
Published Jun 2, 2024
Affected packages
sentry
- Ecosystem
- PyPI
- Affected
- >= 24.3.0, < 24.5.0
- Fixed in
- 24.5.0
- Check
pip show sentry
Advisory details
From the GitHub Advisory Database (CC BY 4.0).
Impact
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.
Example event:
{
"name": "sentry.integrations.slack",
"level": "info",
"event": "slack.event.message", # This could be any of the `slack.*` events
"request_data": {
# Other keys are omitted for brevity
"token": "<MyDeprecatedSlackVerificationToken>",
}
}Patches
- 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.
- If you are only using the
slack.signing-secretin your self-hosted configuration, then the legacy verification token is not used to verify the webhook payload. It is ignored.
⚠️ Sentry's support for validating Slack requests via the legacy verification token will be deprecated in version 24.7.0.
Workarounds
Option 1
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.
Option 2
The deprecated Slack verification token is leaked in log levels of INFO and ERROR in the Slack integration. 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.
Below you'll find an example of the configuration adjustments necessary to remove the Slack integration logs:
# src/sentry/conf/server.py
...
LOGGING: LoggingConfig = {
...
handlers: {
# the line below already exists in the default configuration
"null": {"class": "logging.NullHandler"},
...
},
"loggers": {
"sentry.integrations.slack": {
"handlers": ["null"], # route logs to null handler
"level": "CRITICAL", # prevent generation of logs a lower levels (ex. ERROR and INFO)
},
...
},
}References
- https://github.com/getsentry/sentry/pull/70508
- Sentry Slack Integration Documentation for Self-Hosted users
- Documentation on Slack Signing Secrets
- Slack Deprecation for Verification Tokens
Credited to asottile, asottile-sentry.
References
- https://github.com/getsentry/sentry/security/advisories/GHSA-c2g2-gx4j-rj3j
- https://nvd.nist.gov/vuln/detail/CVE-2024-35196
- 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
- https://github.com/advisories/GHSA-c2g2-gx4j-rj3j
How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. No analysis has been written for this entry yet. Methodology
More PyPI vulnerabilities
All PyPI entriesCVE-2021-47935
Sentry: Superusers can execute arbitrary commands by injecting malicious pickle-serialized objects through audit log entry data parameter
high8.8May 10, 2026CVE-2026-42354
Sentry's improper authentication on SAML SSO process allows user identity linking
critical9.1Apr 30, 2026CVE-2026-27197
Sentry: Improper authentication on SAML SSO process allows user identity linking
critical9.1No fixApr 17, 2026CVE-2025-22146
Sentry's improper authentication on SAML SSO process allows user impersonation
critical9.1Jan 15, 2025CVE-2024-53253
Sentry improper error handling leaks Application Integration Client Secret
medium5.3Nov 22, 2024CVE-2024-45605
Sentry improperly authorizes deletion of user issue alert notifications
high6.5Sep 17, 2024
