Sentry vulnerable to privilege escalation via ApiTokensEndpoint
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| getsentry | sentry | affected |
|
No data.
No data available yet.
| Source | ID | Title |
|---|---|---|
EUVD |
EUVD-2023-2258 | 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`. There are no known workarounds. |
Github GHSA |
GHSA-9jcq-jf57-c62c | Privilege escalation via ApiTokensEndpoint |
No CVSS v4.0
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: 1.1% (1.056% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Getsentry
Getsentry sentry |
|
| CPEs | cpe:2.3:a:getsentry:sentry:*:*:*:*:*:*:*:* | |
| Vendors & Products |
Getsentry
Getsentry sentry |
|
| Metrics |
ssvc
|