CVE-2023-39531: Sentry vulnerable to incorrect credential validation on OAuth token requests

Published Aug 9, 2023
·
Updated

Impact

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.

Remediation

- Sentry SaaS customers do not need to take any action. Those with the highest risk will be contacted directly by Sentry. - Self-hosted installations should upgrade to version 23.7.2 or higher.

Workarounds

There are no direct workarounds, but users should review applications authorized on their account (User Settings > Authorized Applications) and remove any that are no longer needed.

Other sources

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. There are no direct workarounds, but users should review applications authorized on their account and remove any that are no longer needed.

MITRE

Affected Software

2 affected componentsFixes available
pip/sentry>=10.0.0<23.7.2
23.7.2
Sentry sentry>=10.0.0<23.7.2

Event History

Aug 9, 2023
CVE Published
via MITRE·04:09 PM
Data Sourced
via MITRE·04:09 PM
DescriptionSeverityWeakness
Advisory Published
08:58 PM

Frequently Asked Questions

1

What is the impact of CVE-2023-39531?

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.

2

How can an attacker exploit CVE-2023-39531?

The attacker needs to have knowledge of the client ID and the API application must have been authorized on the targeted user account.

3

What is the severity of CVE-2023-39531?

The severity of CVE-2023-39531 is medium with a severity value of 6.8.

4

What is the remedy for CVE-2023-39531?

The remedy for CVE-2023-39531 is to upgrade to version 23.7.2 of the Sentry package.

5

Where can I find more information about CVE-2023-39531?

You can find more information about CVE-2023-39531 at the following references: [GitHub Advisory](https://github.com/getsentry/sentry/security/advisories/GHSA-hgj4-h2x3-rfx4) and [NVD](https://nvd.nist.gov/vuln/detail/CVE-2023-39531).

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203