CVE - CVE-2024-35196

CVE-ID
CVE-2024-35196	Learn more at National Vulnerability Database (NVD) • CVSS Severity Rating • Fix Information • Vulnerable Software Versions • SCAP Mappings • CPE Information
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.
References
Note: References are provided for the convenience of the reader to help distinguish between vulnerabilities. The list is not intended to be complete.
MISC:https://api.slack.com/authentication/verifying-requests-from-slack#app-management-updates URL:https://api.slack.com/authentication/verifying-requests-from-slack#app-management-updates MISC:https://api.slack.com/authentication/verifying-requests-from-slack#deprecation URL:https://api.slack.com/authentication/verifying-requests-from-slack#deprecation MISC:https://api.slack.com/authentication/verifying-requests-from-slack#regenerating URL:https://api.slack.com/authentication/verifying-requests-from-slack#regenerating MISC:https://develop.sentry.dev/integrations/slack URL:https://develop.sentry.dev/integrations/slack MISC:https://github.com/getsentry/sentry/blob/17d2b87e39ccd57e11da4deed62971ff306253d1/src/sentry/conf/server.py#L1307 URL:https://github.com/getsentry/sentry/blob/17d2b87e39ccd57e11da4deed62971ff306253d1/src/sentry/conf/server.py#L1307 MISC:https://github.com/getsentry/sentry/pull/70508 URL:https://github.com/getsentry/sentry/pull/70508 MISC:https://github.com/getsentry/sentry/security/advisories/GHSA-c2g2-gx4j-rj3j URL:https://github.com/getsentry/sentry/security/advisories/GHSA-c2g2-gx4j-rj3j
Assigning CNA
GitHub (maintainer security advisories)
Date Record Created
20240510	Disclaimer: The record creation date may reflect when the CVE ID was allocated or reserved, and does not necessarily indicate when this vulnerability was discovered, shared with the affected vendor, publicly disclosed, or updated in CVE.
Phase (Legacy)
Assigned (20240510)
Votes (Legacy)

Comments (Legacy)

Proposed (Legacy)
N/A
This is an record on the CVE List, which provides common identifiers for publicly known cybersecurity vulnerabilities.
Search CVE Using Keywords: You can also search by reference using the CVE Reference Maps.
For More Information: CVE Request Web Form (select "Other" from dropdown)