CVE-2024-35196
Last modified
CVE-2024-35196 is a low-severity vulnerability rated 2/10 on the CVSS scale. Sentry is a developer-first error tracking and performance monitoring platform. Sentry's Slack integration incorrectly records the incoming request body in logs. EPSS estimates a 0.57% chance of exploitation in the next 30 days.
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.**
Metrics
CVSS:3.1/AV:N/AC:H/PR:H/UI:R/S:U/C:L/I:N/A:N
Weakness Enumeration
References
Timeline
- Published
- Last Modified
- Status
- Deferred
Frequently Asked Questions
What is CVE-2024-35196?
How severe is CVE-2024-35196?
How do I fix CVE-2024-35196?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2024
- CVE-2024-3519The Media Library Assistant plugin for WordPress is vulnerab…6.1
- CVE-2024-35190Asterisk is an open source private branch exchange and telep…5.3
- CVE-2024-35191Formie is a Craft CMS plugin for creating forms. Prior to 2.…4.4
- CVE-2024-35192Trivy is a security scanner. Prior to 0.51.2, if a malicious…5.5
- CVE-2024-35194Minder is a software supply chain security platform. Prior t…5.3
- CVE-2024-35195Requests is a HTTP library. Prior to 2.32.0, when making req…5.6
- CVE-2024-35197gitoxide is a pure Rust implementation of Git. On Windows, f…5.4
- CVE-2024-35198TorchServe is a flexible and easy-to-use tool for serving an…9.8
- CVE-2024-35199TorchServe is a flexible and easy-to-use tool for serving an…8.2
- CVE-2024-3520The Country State City Dropdown CF7 plugin for WordPress is …4.3
- CVE-2024-35200When NGINX Plus or NGINX OSS are configured to use the HTTP/…5.3
- CVE-2024-35201Incorrect default permissions in the Intel(R) SDP Tool for W…7.8
Are you affected by CVE-2024-35196?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
