dbcve.org
TeamcityApplication · Jetbrains

CVE-2023-34220

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
High EPSS 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 Commit Status Publisher window 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 · moderate confidence

A stored cross-site scripting (XSS) vulnerability exists in the Commit Status Publisher feature of JetBrains TeamCity versions prior to 2023.05. Attackers can inject malicious JavaScript code into the Commit Status Publisher configuration, which is then stored and executed when other users view or interact with the affected interface, potentially leading to session hijacking or credential theft.

MitigationUpgrade TeamCity to version 2023.05 or later to receive the security patch. If immediate upgrade is not feasible, restrict administrative access to the Commit Status Publisher configuration and implement Content Security Policy headers.

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. Identify TeamCity version
    Access the TeamCity administration interface and navigate to the 'About' page, or check the version banner typically displayed in the footer of the web UI. Alternatively, check the TeamCity server logs or installation directory for version metadata.
    Affected if The installed version is any release prior to 2023.05 (e.g., 2023.04, 2022.12, earlier).
  2. Locate Commit Status Publisher configuration
    In the TeamCity web UI, go to Administration > Server Configuration > Commit Status Publisher. If this menu item exists and the feature is accessible, it is configured in the environment.
    Affected if The Commit Status Publisher feature is present and accessible in the administration interface, indicating it may be in use.
  3. Inspect stored configuration for suspicious content
    Examine each configured publisher in the Commit Status Publisher settings. Look for unexpected or encoded characters in fields such as publisher name, repository URL, or custom parameters. Check for script tags, event handlers (onload, onerror, onclick), or javascript: URIs within any text fields.
    Affected if Any configuration field contains JavaScript code, HTML tags, or unusual encoded strings that were not intentionally configured by an administrator.

A user is affected if their TeamCity version is below 2023.05 AND the Commit Status Publisher feature is configured with malicious script content injected into its settings.

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 TeamCity to version 2023.05 or later to receive the security patch. If immediate upgrade is not feasible, restrict administrative access to the Commit Status Publisher configuration and implement Content Security Policy headers.

Recommended fix High confidence

TeamCity 2023.05 or later

  1. 1. Back up your TeamCity server data directory and database before upgrading
  2. 2. Download TeamCity 2023.05 or a later stable version from the official JetBrains website (www.jetbrains.com/teamcity/download)
  3. 3. Follow the official TeamCity upgrade instructions for your installation method
  4. 4. After upgrade, verify the Commit Status Publisher functionality works correctly
  5. 5. Confirm the stored XSS vulnerability in the Commit Status Publisher window is resolved by testing with legitimate input
Caveat Review TeamCity 2023.05 release notes for any breaking changes or migration requirements specific to your configuration

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