CVE-2024-24829 – SSRF in Sentry via Phabricator integration
https://notcve.org/view.php?id=CVE-2024-24829
Sentry is an error tracking and performance monitoring platform. Sentry’s integration platform provides a way for external services to interact with Sentry. One of such integrations, the Phabricator integration (maintained by Sentry) with version <=24.1.1 contains a constrained SSRF vulnerability. An attacker could make Sentry send POST HTTP requests to arbitrary URLs (including internal IP addresses) by providing an unsanitized input to the Phabricator integration. However, the body payload is constrained to a specific format. • https://github.com/getsentry/self-hosted/releases/tag/24.1.2 https://github.com/getsentry/sentry/pull/64882 https://github.com/getsentry/sentry/security/advisories/GHSA-rqxh-fp9p-p98r • CWE-918: Server-Side Request Forgery (SSRF) •
CVE-2023-39531 – Sentry vulnerable to incorrect credential validation on OAuth token requests
https://notcve.org/view.php?id=CVE-2023-39531
Sentry is an error tracking and performance monitoring platform. Starting in version 10.0.0 and prior to version 23.7.2, an attacker with sufficient client-side exploits could retrieve a valid access token for another user during the OAuth token exchange due to incorrect credential validation. The client ID must be known and the API application must have already been authorized on the targeted user account. Sentry SaaS customers do not need to take any action. Self-hosted installations should upgrade to version 23.7.2 or higher. • https://github.com/getsentry/sentry/security/advisories/GHSA-hgj4-h2x3-rfx4 • CWE-287: Improper Authentication •
CVE-2023-39349 – Sentry vulnerable to privilege escalation via ApiTokensEndpoint
https://notcve.org/view.php?id=CVE-2023-39349
Sentry is an error tracking and performance monitoring platform. Starting in version 22.1.0 and prior to version 23.7.2, an attacker with access to a token with few or no scopes can query `/api/0/api-tokens/` for a list of all tokens created by a user, including tokens with greater scopes, and use those tokens in other requests. There is no evidence that the issue was exploited on `sentry.io`. For self-hosted users, it is advised to rotate user auth tokens. A fix is available in version 23.7.2 of `sentry` and `self-hosted`. • https://github.com/getsentry/self-hosted/releases/tag/23.7.2 https://github.com/getsentry/sentry/commit/fad12c1150d1135edf9666ea72ca11bc110c1083 https://github.com/getsentry/sentry/pull/53850 https://github.com/getsentry/sentry/releases/tag/23.7.2 https://github.com/getsentry/sentry/security/advisories/GHSA-9jcq-jf57-c62c • CWE-284: Improper Access Control CWE-287: Improper Authentication •
CVE-2023-36826 – Sentry vulnerable to improper authorization on debug and artifact file downloads
https://notcve.org/view.php?id=CVE-2023-36826
Sentry is an error tracking and performance monitoring platform. Starting in version 8.21.0 and prior to version 23.5.2, an authenticated user can download a debug or artifact bundle from arbitrary organizations and projects with a known bundle ID. The user does not need to be a member of the organization or have permissions on the project. A patch was issued in version 23.5.2 to ensure authorization checks are properly scoped on requests to retrieve debug or artifact bundles. Authenticated users who do not have the necessary permissions on the particular project are no longer able to download them. • https://github.com/getsentry/sentry/commit/e932b15435bf36239431eaa3790a6bcfa47046a9 https://github.com/getsentry/sentry/pull/49680 https://github.com/getsentry/sentry/security/advisories/GHSA-m4hc-m2v6-hfw8 • CWE-285: Improper Authorization CWE-863: Incorrect Authorization •
CVE-2023-36829 – Sentry CORS misconfiguration vulnerability
https://notcve.org/view.php?id=CVE-2023-36829
Sentry is an error tracking and performance monitoring platform. Starting in version 23.6.0 and prior to version 23.6.2, the Sentry API incorrectly returns the `access-control-allow-credentials: true` HTTP header if the `Origin` request header ends with the `system.base-hostname` option of Sentry installation. This only affects installations that have `system.base-hostname` option explicitly set, as it is empty by default. Impact is limited since recent versions of major browsers have cross-site cookie blocking enabled by default. However, this flaw could allow other multi-step attacks. • https://github.com/getsentry/self-hosted/releases/tag/23.6.2 https://github.com/getsentry/sentry/commit/ee44c6be35e5e464bc40637580f39867898acd8b https://github.com/getsentry/sentry/pull/52276 https://github.com/getsentry/sentry/security/advisories/GHSA-4xqm-4p72-87h6 • CWE-697: Incorrect Comparison CWE-863: Incorrect Authorization CWE-942: Permissive Cross-domain Policy with Untrusted Domains •