dbcve.org
TeamcityApplication · Jetbrains

CVE-2023-34221

MEDIUM · 5.4 CVSS v3.1 Published 2023-05-31
Fix available
A fix is available. Upgrade to 2023.05 or later.
See remediation →
58/100
Remediation priority · Elevated
Remotely reachable

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 stored XSS in the Show Connection page was possible

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

Stored cross-site scripting (XSS) vulnerability in JetBrains TeamCity's Show Connection page affecting versions prior to 2023.05. The vulnerability allows authenticated attackers to inject malicious scripts that persist and execute when other users view the Show Connection page.

MitigationUpgrade to TeamCity version 2023.05 or later which contains the fix for this stored XSS vulnerability.

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

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
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/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. Locate TeamCity server version
    Access TeamCity administration UI: go to Administration > Server Administration > Server Information, or check the buildServer.properties file in the TeamCity data directory for the version property
    Affected if The displayed version number is lower than 2023.05 (for example, 2023.04, 2022.12, etc.)
  2. Confirm version from command line
    Run 'teamcity-server.bat version' or './teamcity-server.sh version' from the TeamCity bin directory, or inspect the startup logs for the version string
    Affected if The reported version is any release prior to 2023.05
  3. Verify Show Connection page exists
    Log in as an authenticated user and navigate to the Show Connection page (typically accessible via the administration or connections section of the web UI)
    Affected if The page loads successfully, indicating the feature is enabled and accessible
  4. Check authentication configuration
    Review the server.xml or authentication configuration to confirm that user authentication is required for accessing TeamCity
    Affected if Anonymous access is permitted, or authentication is otherwise relaxed, but the vulnerability requires at least some authenticated users to exist for exploitation

You are affected if your TeamCity server version is any release prior to 2023.05 and the Show Connection page feature is accessible to authenticated users in your environment.

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

Upgrade to TeamCity version 2023.05 or later which contains the fix for this stored XSS vulnerability.

Recommended fix High confidence

2023.05 or later

  1. Back up the TeamCity server data directory and database before upgrading
  2. Download TeamCity version 2023.05 or later from the official JetBrains website (www.jetbrains.com)
  3. Stop the TeamCity server gracefully
  4. Install the new TeamCity version using the standard upgrade process (run the installer or deploy the new war/zip package)
  5. Start the TeamCity server and verify it starts without errors
  6. Log in to TeamCity and navigate to the Show Connection page to confirm the vulnerability is remediated
  7. Review the TeamCity 2023.05 release notes for any known issues or additional migration steps
Caveat Review release notes for version-specific migration requirements; major version upgrades may introduce breaking changes

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
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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