dbcve.org
TeamcityApplication · Jetbrains

CVE-2023-39173

HIGH · 8.8 CVSS v3.1 Published 2023-07-25
Fix available
A fix is available. Upgrade to 2023.05.2 or later.
See remediation →
94/100
Remediation priority · Urgent
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
In JetBrains TeamCity before 2023.05.2 a token with limited permissions could be used to gain full account 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

In JetBrains TeamCity versions prior to 2023.05.2, an authentication token with restricted or limited permissions could be exploited to obtain full account access, representing a privilege escalation vulnerability in the token validation logic.

MitigationUpgrade JetBrains TeamCity to version 2023.05.2 or later to resolve the token authorization bypass. Review existing tokens for potential compromise and rotate them 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
TeamcityApplication
Affected:< 2023.05.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
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

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

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. Determine TeamCity server version
    Access the TeamCity administration web interface and navigate to 'About' page, or check the version via the <TeamCity_home>/buildAgent/conf/buildAgent.properties file, or run: curl -s http://<server>/app/rest/server/version
    Affected if The installed version is earlier than 2023.05.2 (e.g., 2023.05.1, 2023.04.x, etc.)
  2. Verify authentication token usage
    Check if the TeamCity server has any user tokens configured by reviewing the 'Tokens' section under 'User Management' in the administration area, or query the REST API endpoint: /app/rest/users/{userId}/tokens
    Affected if Any authentication tokens exist in the system, regardless of permission scope assigned
  3. Inspect token permission scope
    Review each token's assigned permissions in the TeamCity administration panel under 'User Management' > 'Tokens', noting any tokens with 'limited' or 'restricted' permissions
    Affected if Tokens with limited or restricted permission scopes are present in the environment
  4. Check for unexpected full-access tokens
    Audit token creation timestamps and associated user accounts via the administration panel or by reviewing server logs for token creation events: grep -i 'token.*created' <TeamCity_home>/logs/*.log
    Affected if Tokens exist that were created without explicit administrator action or show unusual creation patterns

The environment is affected if running any TeamCity version prior to 2023.05.2 and authentication tokens are configured, regardless of their assigned permission scope.

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 2023.05.2 or later
Fixed in 2023.05.2
Interim mitigation

Upgrade JetBrains TeamCity to version 2023.05.2 or later to resolve the token authorization bypass. Review existing tokens for potential compromise and rotate them as a precautionary measure.

Recommended fix High confidence

TeamCity 2023.05.2 or later

  1. Back up your TeamCity installation and all data before upgrading
  2. Download TeamCity 2023.05.2 or later from the official JetBrains website (www.jetbrains.com)
  3. Follow the official TeamCity upgrade instructions to install the new version
  4. After upgrade, verify that limited-scope tokens no longer have full account access
  5. Test that authentication and authorization work correctly with the updated version

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

Fix this in Teamcity 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 the upgrade done

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-39173 — 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-39173 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