dbcve.org
TeamcityApplication · Jetbrains

CVE-2023-38063

MEDIUM · 5.4 CVSS v3.1 Published 2023-07-12
Fix available
A fix is available. Upgrade to 2023.05.1 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.1 stored XSS while running custom builds 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 JetBrains TeamCity versions prior to 2023.05.1. The vulnerability allows execution of malicious scripts through the custom builds functionality, where user-supplied input is not properly sanitized before being stored and rendered to other users.

MitigationUpgrade TeamCity to version 2023.05.1 or later. If immediate upgrading is not feasible, restrict or disable the custom builds feature and implement input validation as a compensating control.

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.1

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
    Access the TeamCity administration interface and navigate to 'About' or use the /admin/about.html endpoint to view the installed version number
    Affected if The installed version is any release prior to 2023.05.1 (for example, 2023.04.x, 2023.03.x, earlier releases)
  2. Identify if custom builds feature is enabled
    Navigate to the TeamCity administration settings and locate the custom builds or custom run parameters configuration under project or build configuration settings
    Affected if The custom builds feature is enabled and accessible to users who can create or modify build configurations
  3. Verify user access to custom build input fields
    Review user roles and permissions in the TeamCity administration panel under 'Users' and 'Roles' to determine which users can supply custom build parameters or labels
    Affected if Users other than trusted administrators have permission to define or modify custom build fields that accept user input
  4. Inspect custom build parameters for suspicious content
    Examine existing build configurations, custom build runs, or build parameters stored in the TeamCity database or visible in the web interface for unsanitized script tags, JavaScript event handlers, or encoded payloads
    Affected if Any custom build parameters contain unescaped HTML tags, script elements, or javascript: URLs

You are affected if your TeamCity version is earlier than 2023.05.1 AND the custom builds feature is accessible to users who can inject unsanitized script content into build parameter fields.

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.1 or later
Fixed in 2023.05.1
Interim mitigation

Upgrade TeamCity to version 2023.05.1 or later. If immediate upgrading is not feasible, restrict or disable the custom builds feature and implement input validation as a compensating control.

Recommended fix High confidence

TeamCity 2023.05.1

  1. Backup your TeamCity data directory and database before upgrading
  2. Download TeamCity 2023.05.1 or a later stable version from the official JetBrains website
  3. Stop the running TeamCity server
  4. Follow the official TeamCity upgrade instructions for your installation method
  5. Start the upgraded TeamCity server
  6. Verify the XSS vulnerability is resolved by checking that custom builds no longer execute arbitrary JavaScript
Caveat Review JetBrains release notes for 2023.05.x for any configuration or feature changes that may affect your setup

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
  • Testing4.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,720
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,752.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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