CVSS: 7.1EPSS: 0%CPEs: 1EXPL: 0CVE-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 •
CVSS: 7.1EPSS: 0%CPEs: 1EXPL: 0CVE-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') •
CVSS: 5.3EPSS: 0%CPEs: 1EXPL: 0CVE-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) •
CVSS: 6.8EPSS: 0%CPEs: 1EXPL: 0CVE-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 •
CVSS: 8.1EPSS: 0%CPEs: 1EXPL: 1CVE-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 •