dbcve.org
TeamcityApplication · Jetbrains

CVE-2023-34229

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 GitLab 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 XSS vulnerability in the GitLab Connection page of JetBrains TeamCity versions before 2023.05 allows attackers to inject malicious JavaScript that persists on the server and executes when users view the GitLab integration settings.

MitigationUpgrade TeamCity to version 2023.05 or later. Review and sanitize any existing GitLab connection configurations that may have been compromised during the vulnerability window.

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. Check TeamCity version
    Navigate to Administration > Server Administration > Server Configuration, or check the version via the login page footer and Administration > Diagnostics. Compare the installed version against the affected range: versions before 2023.05 are vulnerable.
    Affected if Installed version is earlier than 2023.05 (e.g., 2023.04.x, 2022.x, earlier)
  2. Verify GitLab integration is configured
    Navigate to Administration > Integrations > GitLab. Check if any GitLab connections exist. Look for the presence of GitLab integration settings pages.
    Affected if GitLab integration has been configured with one or more connections
  3. Inspect GitLab connection settings for malicious scripts
    In Administration > Integrations > GitLab, examine each GitLab connection's settings fields (Server URL, API token name, or description fields). Look for unexpected script tags, javascript: URIs, or encoded payloads in any text input.
    Affected if Any text field in GitLab connection settings contains <script>, javascript:, onload, onerror, or other JavaScript event handlers
  4. Review audit logs for GitLab configuration changes
    Check TeamCity audit logs in Administration > Audit for recent changes to GitLab integration settings. Look for entries from unknown users or unexpected modification times.
    Affected if Audit log shows unauthorized or unexpected modifications to GitLab connections

A user is affected if their TeamCity version is earlier than 2023.05 AND GitLab integration is enabled, with potential malicious payloads present in GitLab connection 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. Review and sanitize any existing GitLab connection configurations that may have been compromised during the vulnerability window.

Recommended fix High confidence

TeamCity 2023.05 or later

  1. 1. Back up your TeamCity data directory and database before upgrading
  2. 2. Download TeamCity 2023.05 or later from the official JetBrains website (www.jetbrains.com/teamcity/download)
  3. 3. Stop the TeamCity server
  4. 4. Install the new version following the standard TeamCity upgrade procedure
  5. 5. Start the TeamCity server and verify the GitLab Connection page is accessible
  6. 6. Re-create or verify existing GitLab connections to confirm functionality
Caveat Review JetBrains release notes for 2023.05 for any configuration or feature changes before upgrading

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

Fix this in Teamcity Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,390
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,224.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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