Skip to content

Privilege escalation via ApiTokensEndpoint

High severity GitHub Reviewed Published Aug 7, 2023 in getsentry/sentry • Updated Nov 10, 2023

Package

pip sentry (pip)

Affected versions

>= 22.1.0, < 23.7.2

Patched versions

23.7.2

Description

Impact

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 https://sentry.io. For self-hosted users, it is advised to rotate user auth tokens via https://your-self-hosted-sentry-installation/settings/account/api/auth-tokens/.

Patches

The issue was fixed in getsentry/sentry#53850 and is available in the release 23.7.2 of sentry and self-hosted.

Workarounds

There are no known workarounds.

References

@oioki oioki published to getsentry/sentry Aug 7, 2023
Published by the National Vulnerability Database Aug 7, 2023
Published to the GitHub Advisory Database Aug 8, 2023
Reviewed Aug 8, 2023
Last updated Nov 10, 2023

Severity

High

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Network
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
None

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N

EPSS score

0.092%
(40th percentile)

Weaknesses

CVE ID

CVE-2023-39349

GHSA ID

GHSA-9jcq-jf57-c62c

Source code

Credits

Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.