{"answers":{"affected":"3 open source packages ship an affected version, including sentry.","exploited":"There is no known exploitation of CVE-2024-35196 in the wild and no public exploit code.","fix":"Upgrade sentry to 24.5.0 or later.","what":"CVE-2024-35196 is a low-severity vulnerability in getsentry sentry, published on 31 May 2024. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2024-35196 and fix it if it is affected.\n\nWhat it is: CVE-2024-35196 is a low-severity vulnerability in getsentry sentry, published on 31 May 2024. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2024-35196 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- sentry (PyPI): affected from 24.3.0; fixed in 24.5.0\n- sentry (PyPI): affected from 24.3.0; fixed in 24.5.0\n- sentry (PyPI): affected from 24.3.0; fixed in 24.5.0\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2024-35196/ (Markdown: https://insights.sbomify.com/CVE-2024-35196/index.md)","id":"CVE-2024-35196","markdown":"https://insights.sbomify.com/CVE-2024-35196/index.md","name":"CVE-2024-35196","record":{"aliases":["GHSA-c2g2-gx4j-rj3j","PYSEC-2026-1913"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["data_read","security_bypass"],"network_reachable":"yes","non_default_config":true,"product_category":"Sentry error tracking","requires_auth":"high_privilege","summary":"Sentry logs leak Slack verification tokens, allowing attackers to forge requests if using deprecated tokens in self-hosted configurations.","user_interaction":"required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":2,"severity":"low","source":"cna","vector":"CVSS:3.1/AV:N/AC:H/PR:H/UI:R/S:U/C:L/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-532","name":"Insertion of Sensitive Information into Log File"}],"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.*\" \u0026\u0026 name == \"sentry.integrations.slack\" \u0026\u0026 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.**","ecosystems":["PyPI"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"Slack integration leaks sensitive information in logs in Sentry","id":"CVE-2024-35196","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"PyPI","product":null,"products":[],"type":"information_disclosure","year":"2024"},"n_packages":3,"n_references":7,"next":{"headline":"gix refs and paths with reserved Windows device names access the devices","id":"CVE-2024-35197"},"packages":[{"ecosystem":"PyPI","fixed":["24.5.0"],"introduced":["24.3.0"],"last_affected":[],"package":"sentry","purl":null,"source":"GHSA-c2g2-gx4j-rj3j"},{"ecosystem":"PyPI","fixed":["24.5.0"],"introduced":["24.3.0"],"last_affected":[],"package":"sentry","purl":"pkg:pypi/sentry","source":"GHSA-c2g2-gx4j-rj3j"},{"ecosystem":"PyPI","fixed":["24.5.0"],"introduced":["24.3.0"],"last_affected":[],"package":"sentry","purl":"pkg:pypi/sentry","source":"PYSEC-2026-1913"}],"prev":{"headline":"Requests `Session` object does not verify requests after making first request with verify=False","id":"CVE-2024-35195"},"products":["sentry"],"published":"2024-05-31","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"CC BY 4.0","name":"PyPA Advisory Database","prefix":"PYSEC"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2024-08-02","vendors":["getsentry"]},"summary":"Sentry logs leak Slack verification tokens, allowing attackers to forge requests if using deprecated tokens in self-hosted configurations.","url":"https://insights.sbomify.com/CVE-2024-35196/"}