CVE-2024-53253 – Sentry's improper error handling leaks Application Integration Client Secret
https://notcve.org/view.php?id=CVE-2024-53253
Sentry is an error tracking and performance monitoring platform. Version 24.11.0, and only version 24.11.0, is vulnerable to a scenario where a specific error message generated by the Sentry platform could include a plaintext Client ID and Client Secret for an application integration. The Client ID and Client Secret would not be displayed in the UI, but would be returned in the underlying HTTP response to the end user. This could occur under the following conditions: An app installation made use of a Search UI component with the `async` flag set to true (default: true); auser types types into the Search Component which creates a request to the third-party for search or query results; and that third-party response may then fail validation and Sentry would return the `select-requester.invalid-response` error code along with a serialized version of a Sentry application containing the integration Client Secret. Should this error be found, it's reasonable to assume the potential exposure of an integration Client Secret. • https://github.com/getsentry/sentry/pull/79377 https://github.com/getsentry/sentry/pull/81038 https://github.com/getsentry/sentry/security/advisories/GHSA-v5h2-q2w4-gpcx • CWE-209: Generation of Error Message Containing Sensitive Information •
CVE-2024-45605 – Improper authorization on deletion of user issue alert notifications in sentry
https://notcve.org/view.php?id=CVE-2024-45605
Sentry is a developer-first error tracking and performance monitoring platform. An authenticated user delete the user issue alert notifications for arbitrary users given a know alert ID. A patch was issued to ensure authorization checks are properly scoped on requests to delete user alert notifications. Sentry SaaS users do not need to take any action. Self-Hosted Sentry users should upgrade to version 24.9.0 or higher. • https://github.com/getsentry/self-hosted https://github.com/getsentry/sentry/pull/77093 https://github.com/getsentry/sentry/security/advisories/GHSA-54m3-95j9-v89j • CWE-639: Authorization Bypass Through User-Controlled Key •
CVE-2024-45606 – Improper authorization on muting of alert rules in sentry
https://notcve.org/view.php?id=CVE-2024-45606
Sentry is a developer-first error tracking and performance monitoring platform. An authenticated user can mute alert rules from arbitrary organizations and projects with a know rule ID. The user does not need to be a member of the organization or have permissions on the project. In our review, we have identified no instances where alerts have been muted by unauthorized parties. A patch was issued to ensure authorization checks are properly scoped on requests to mute alert rules. • https://github.com/getsentry/self-hosted https://github.com/getsentry/sentry/pull/77016 https://github.com/getsentry/sentry/security/advisories/GHSA-v345-w9f2-mpm5 • CWE-639: Authorization Bypass Through User-Controlled Key •
CVE-2024-41656 – Sentry vulnerable to stored Cross-Site Scripting (XSS)
https://notcve.org/view.php?id=CVE-2024-41656
Sentry is an error tracking and performance monitoring platform. Starting in version 10.0.0 and prior to version 24.7.1, an unsanitized payload sent by an Integration platform integration allows storing arbitrary HTML tags on the Sentry side with the subsequent rendering them on the Issues page. Self-hosted Sentry users may be impacted in case of untrustworthy Integration platform integrations sending external issues from their side to Sentry. A patch has been released in Sentry 24.7.1. For Sentry SaaS customers, no action is needed. • https://github.com/getsentry/self-hosted/releases/tag/24.7.1 https://github.com/getsentry/sentry/commit/5c679521f1539eabfb81287bfc30f34dbecd373e https://github.com/getsentry/sentry/pull/74648 https://github.com/getsentry/sentry/security/advisories/GHSA-fm88-hc3v-3www • CWE-79: Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') •
CVE-2024-40647 – Unintentional exposure of environment variables to subprocesses in sentry-sdk
https://notcve.org/view.php?id=CVE-2024-40647
sentry-sdk is the official Python SDK for Sentry.io. A bug in Sentry's Python SDK < 2.8.0 allows the environment variables to be passed to subprocesses despite the `env={}` setting. In Python's `subprocess` calls, all environment variables are passed to subprocesses by default. However, if you specifically do not want them to be passed to subprocesses, you may use `env` argument in `subprocess` calls. Due to the bug in Sentry SDK, with the Stdlib integration enabled (which is enabled by default), this expectation is not fulfilled, and all environment variables are being passed to subprocesses instead. • https://docs.python.org/3/library/subprocess.html https://docs.sentry.io/platforms/python/integrations/default-integrations https://docs.sentry.io/platforms/python/integrations/default-integrations/#stdlib https://github.com/getsentry/sentry-python/commit/763e40aa4cb57ecced467f48f78f335c87e9bdff https://github.com/getsentry/sentry-python/pull/3251 https://github.com/getsentry/sentry-python/releases/tag/2.8.0 https://github.com/getsentry/sentry-python/security/advisories/GHSA-g92j-qhmh-64v2 • CWE-200: Exposure of Sensitive Information to an Unauthorized Actor •