dbcve.org
Incorrect Permission AssignmentWeakness · CWE-732

CVE-2023-39338

MEDIUM · 6.8 CVSS v3.0 Published 2025-07-12
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
75/100
Remediation priority · High
Remotely reachable No privileges

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
Enables an authenticated user (enrolled device) to access a service protected by Sentry even if they are not authorized according to the sentry policy to access that service. It does not enable the user to authenticate to or use the service, it just provides the tunnel access.

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

This is an authorization bypass vulnerability in Sentry where an authenticated user with an enrolled device can obtain tunnel access to a protected service even when the Sentry policy explicitly denies authorization for that service. The flaw allows unauthorized tunnel establishment but does not grant the ability to actually authenticate to or use the protected service itself.

MitigationReview and update Sentry policy enforcement logic to ensure tunnel access is properly gated by authorization checks, and verify that policy denies are correctly enforced for all authenticated sessions.

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

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
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
None

CVSS:3.0/AV:N/AC:H/PR:N/UI:R/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. Identify Sentry installation and version
    Locate the Sentry installation and retrieve its version number using the Sentry CLI command 'sentry --version' or by checking the UI under Administration > Settings > About. Compare this version to the version where CVE-2023-39338 was patched.
    Affected if The installed Sentry version is older than the patched version for this vulnerability.
  2. Confirm authenticated users with enrolled devices exist
    Review the Sentry user directory and check which users have devices enrolled through the authentication system. This can be verified in the UI under Settings > Users > [Select User] > Identities or via API queries for user enrollment status.
    Affected if There are authenticated users in the system who have enrolled devices, creating the precondition for this vulnerability.
  3. Identify protected services configured in Sentry
    Examine the Sentry configuration for any protected services or internal resources that are meant to be restricted. Check under Settings > Projects > [Project] > Security Token or similar protected resource configurations.
    Affected if Protected services or resources are defined in Sentry that should be subject to authorization policies.
  4. Review tunnel access policy enforcement
    Inspect the authorization policies governing tunnel access to protected services. Check if policies explicitly define denies for tunnel access and verify whether these denies are being correctly evaluated during session establishment.
    Affected if Tunnel access policies exist but deny rules may not be correctly enforced for authenticated sessions with enrolled devices.
  5. Test tunnel establishment with policy-denied service
    As an authenticated user with an enrolled device, attempt to establish a tunnel to a protected service that has an explicit policy deny. Observe whether the tunnel connection is successfully established despite the policy deny.
    Affected if A tunnel can be established to a protected service even when the Sentry policy explicitly denies authorization for that service.

A Sentry installation is affected if it runs a version predating the patch for CVE-2023-39338 and has authenticated users with enrolled devices accessing protected services, where tunnel access may be granted despite explicit policy denies.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Review and update Sentry policy enforcement logic to ensure tunnel access is properly gated by authorization checks, and verify that policy denies are correctly enforced for all authenticated sessions.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-39338 — 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-39338 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