CVE-2024-35196 is a low-severity (CVSS 2) CWE-532 vulnerability in sentry. A fix is available for sentry — see the affected versions and patch details below.
Slack integration leaks sensitive information in logs in Sentry
Exploitation Status
No confirmed exploitation observed yet
- CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.
Exploitation and automatability from CISA’s SSVC triage for CVE-2024-35196.
EPSS Exploitation Probability
EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.
How urgent is this, really
CVE-2024-35196 plotted by exploitation likelihood (EPSS) against impact (CVSS). The shaded corner — EPSS 50%+ and CVSS 7.0+ — is where this CVE doesn't sit, though severity or exploitability alone can still warrant action.
Where this sits among everything scored
Of 378,567 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Real counts from FIRST.org, not a sample — log-scaled since the landscape is heavily right-skewed.
Real-World Exposure
sentryReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects PyPI packages — download data is not available via public APIs for these ecosystems.
Description
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.
- If you are only using the
⚠️ 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
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐍PyPI | sentry | ≥ 24.3.0&&< 24.5.0 | 24.5.0pip install --upgrade 'sentry==24.5.0' |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for sentry, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update sentry to 24.5.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2024-35196 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like CVE-2024-35196 can be triaged on real exposure rather than presence alone.
Tailored to CVE-2024-35196. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is CVE-2024-35196 in your dependencies?
O3 Security finds CVE-2024-35196 across PyPI dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.