First published: Wed Aug 09 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.
Credit: security-advisories@github.com security-advisories@github.com security-advisories@github.com
Affected Software | Affected Version | How to fix |
---|---|---|
Sentry Sentry | >=10.0.0<23.7.2 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
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 attacker needs to have knowledge of the client ID and the API application must have been authorized on the targeted user account.
The severity of CVE-2023-39531 is medium with a severity value of 6.8.
The remedy for CVE-2023-39531 is to upgrade to version 23.7.2 of the Sentry package.
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).