dbcve.org
TeamcityApplication · Jetbrains

CVE-2023-38066

MEDIUM · 6.1 CVSS v3.1 Published 2023-07-12
Fix available
A fix is available. Upgrade to 2023.05.1 or later.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable No privileges

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 reflected XSS via the Referer header was possible during artifact downloads

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

A reflected cross-site scripting (XSS) vulnerability existed in JetBrains TeamCity before version 2023.05.1. The application reflected the HTTP Referer header without proper sanitization or encoding during artifact download functionality, allowing an attacker to inject malicious script content that would execute in a victim's browser when they accessed crafted download links.

MitigationUpgrade to TeamCity version 2023.05.1 or later. As a temporary workaround, implement Web Application Firewall rules to sanitize or block malicious Referer header values targeting artifact download endpoints.

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

CVSS:3.1/AV:N/AC:L/PR:N/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 UI, navigate to 'Server Administration' > 'Server Information', or check the version displayed on the login page. Alternatively, inspect the TeamCity server startup logs for the version string.
    Affected if The displayed version is below 2023.05.1 (for example, 2023.05.0, 2023.03.x, or any earlier release).
  2. Confirm artifact download feature is accessible
    Verify that users or anonymous guests can access the artifact download functionality. This is typically found at URLs matching patterns like /download.html, /repository/download, or /artifacts/metadata. Try accessing a known build's artifacts page.
    Affected if The artifact download endpoints are reachable without additional authentication or are accessible to low-privilege users.
  3. Check Referer header handling in artifact download
    If you have access to logs or can capture HTTP traffic, trigger an artifact download request with a crafted Referer header containing script tags (for example, Referer: http://evil.com/<script>alert(1)</script>) and observe whether the header value is reflected unsanitized in any response or error page.
    Affected if The Referer header value is reflected in the response without encoding or sanitization, indicating the XSS vulnerability exists.

You are affected if your TeamCity version is below 2023.05.1 AND the artifact download feature is accessible to users who could be tricked into clicking a crafted link.

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 to TeamCity version 2023.05.1 or later. As a temporary workaround, implement Web Application Firewall rules to sanitize or block malicious Referer header values targeting artifact download endpoints.

Recommended fix High confidence

2023.05.1 or later

  1. Create a complete backup of the TeamCity server data directory and database
  2. Stop the TeamCity server service
  3. Download TeamCity 2023.05.1 or later from the official JetBrains website (www.jetbrains.com)
  4. Run the installer or extract the new version to replace the existing TeamCity installation
  5. Start the TeamCity server service
  6. Verify the upgrade was successful by accessing the TeamCity web interface and confirming the version displays 2023.05.1 or later
Caveat Review TeamCity 2023.05.1 release notes for any breaking changes or migration requirements 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
  • Implementation3.0 h
  • Testing3.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,750
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,800.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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