dbcve.org
SentryApplication

CVE-2023-39531

MEDIUM · 6.8 CVSS v3.1 Published 2023-08-09
Fix available
A fix is available. Upgrade to 23.7.2 or later.
See remediation →
74/100
Remediation priority · Elevated
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

In Sentry versions 10.0.0 through 23.7.2, an OAuth token exchange vulnerability exists due to incorrect credential validation. An attacker with client-side exploits and knowledge of a client ID can obtain a valid access token for another user, provided the API application is already authorized on the target account.

MitigationSelf-hosted Sentry installations must upgrade to version 23.7.2 or higher. Additionally, users should review and revoke any unnecessary authorized applications on their accounts as a precautionary measure.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
SentryApplication
Affected:>= 10.0.0, < 23.7.2

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
High
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
None

CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check installed Sentry version
    Run 'sentry --version' or check the version in your Sentry deployment configuration (e.g., Docker container tags, Helm values, or package.json in self-hosted setups)
    Affected if The installed version is >= 10.0.0 and < 23.7.2
  2. Verify OAuth applications exist
    Access Sentry admin: navigate to Settings > Developer Settings, or query the database table 'sentry_apiapplication' if direct database access is available
    Affected if OAuth applications are registered in the Sentry instance
  3. Review authorized applications on accounts
    Check for authorized applications via API endpoint /api/0/applications/ or inspect the sentry_apigrant table in the database for granted authorizations
    Affected if Any user accounts have granted authorizations to OAuth applications
  4. Inspect OAuth token exchange configuration
    Review the Sentry authentication configuration files or the sentry.conf.py settings for OAuth-related settings such as 'SENTRY_OAUTH' or 'GOOGLE_OAUTH2' settings
    Affected if OAuth authentication providers are configured and enabled

You are affected if your Sentry version is between 10.0.0 and 23.7.2 inclusive and OAuth applications with authorized grants exist on your instance.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 23.7.2 or later
Fixed in 23.7.2
Interim mitigation

Self-hosted Sentry installations must upgrade to version 23.7.2 or higher. Additionally, users should review and revoke any unnecessary authorized applications on their accounts as a precautionary measure.

Recommended fix High confidence

Sentry self-hosted version 23.7.2 or higher

  1. Backup your Sentry self-hosted installation and database before upgrading
  2. Upgrade your Sentry self-hosted installation to version 23.7.2 or higher
  3. After upgrading, review the list of authorized applications on user accounts and revoke any that are no longer needed
  4. Consider rotating access tokens as a precautionary measure
  5. Verify the upgrade was successful by checking the Sentry version and testing OAuth functionality
Caveat Upgrading across many minor versions may introduce breaking changes; review the Sentry changelog for your specific version range before upgrading

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Sentry Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,080
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,328.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-39531 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2023-39531 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data