Goal Reached Thanks to every supporter — we hit 100%!

Goal: 1000 CNY · Raised: 1359 CNY

100%
Buy Us a Coffee

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

Quick assessment

Affected
getsentry sentry
Exploitation
No confirmed in-the-wild exploitation; assess based on exposure
Recommended action
Check the vendor advisory and references for a fixed version. If immediate upgrade is impossible, restrict exposure and increase monitoring.

SENTRY是SENTRY公司的一个面向开发人员的错误跟踪和性能监控平台。 Sentry 24.3.0 到 24.5.0版本存在安全漏洞，该漏洞源于Slack 集成在日志中泄露了已弃用的验证令牌。

CVSS 2.0 · Low EPSS 0.57% · P46

Possible ATT&CK Techniques 1 AI

T1530 · Data from Cloud Storage
Get alerts for future matching vulnerabilities Log in to subscribe

I. Basic Information for CVE-2024-35196

Vulnerability Information
Have questions about the vulnerability? See if Shenlong's analysis helps!
View Shenlong Deep Dive ↗

Although we use advanced large model technology, its output may still contain inaccurate or outdated information.Shenlong tries to ensure data accuracy, but please verify and judge based on the actual situation.

Vulnerability Title
Slack integration leaks sensitive information in logs in Sentry
Source: CVE Program / CVE List V5
Vulnerability 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.**
Source: CVE Program / CVE List V5
CVSS Information
CVSS:3.1/AV:N/AC:H/PR:H/UI:R/S:U/C:L/I:N/A:N
Source: CVE Program / CVE List V5
Vulnerability Type
通过日志文件的信息暴露
Source: CVE Program / CVE List V5
Vulnerability Title
Sentry 安全漏洞
Source: CNNVD (China National Vulnerability Database)
Vulnerability Description
SENTRY是SENTRY公司的一个面向开发人员的错误跟踪和性能监控平台。 Sentry 24.3.0 到 24.5.0版本存在安全漏洞，该漏洞源于Slack 集成在日志中泄露了已弃用的验证令牌。
Source: CNNVD (China National Vulnerability Database)
CVSS Information
N/A
Source: CNNVD (China National Vulnerability Database)
Vulnerability Type
N/A
Source: CNNVD (China National Vulnerability Database)

Affected Products

Vendor Product Affected Versions CPE Subscribe
getsentry sentry >= 24.3.0, < 24.5.0 -

II. Public POCs for CVE-2024-35196

# POC Description Source Link Shenlong Link
AI-Generated POC Premium

No public POC found.

Login to generate AI POC

III. Intelligence Information for CVE-2024-35196

请登录查看更多情报信息。

Patches & Fixes for CVE-2024-35196 (1)

Vendor Advisories for CVE-2024-35196 (1)

Other References for CVE-2024-35196 (5)

IV. Related Vulnerabilities

Same product: sentry
Same vendor: getsentry
Same weakness: CWE-532

V. Comments for CVE-2024-35196

No comments yet

Leave a comment