Headline
GHSA-hgj4-h2x3-rfx4: Sentry vulnerable to incorrect credential validation on OAuth token requests
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.
Skip to content
Actions
Automate any workflow
Packages
Host and manage packages
Security
Find and fix vulnerabilities
Codespaces
Instant dev environments
Copilot
Write better code with AI
Code review
Manage code changes
Issues
Plan and track work
Discussions
Collaborate outside of code
GitHub Sponsors
Fund open source developers
* The ReadME Project
GitHub community articles
- Pricing
- GitHub Advisory Database
- GitHub Reviewed
- CVE-2023-39531
Sentry vulnerable to incorrect credential validation on OAuth token requests
Moderate severity GitHub Reviewed Published Aug 9, 2023 in getsentry/sentry • Updated Aug 9, 2023
Affected versions
>= 10.0.0, < 23.7.2
Description
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.
References
- GHSA-hgj4-h2x3-rfx4
- https://nvd.nist.gov/vuln/detail/CVE-2023-39531
Published to the GitHub Advisory Database
Aug 9, 2023
Related news
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.