dbcve.org
TeamcityApplication · Jetbrains

CVE-2023-39175

MEDIUM · 6.1 CVSS v3.1 Published 2023-07-25
Fix available
A fix is available. Upgrade to 2023.05.2 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.2 reflected XSS via GitHub integration 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

A reflected cross-site scripting (XSS) vulnerability exists in JetBrains TeamCity's GitHub integration. Attackers can inject malicious scripts through unsanitized input parameters in the GitHub integration feature. This is a stored/reflected XSS flaw allowing execution of arbitrary JavaScript in the context of a victim's browser session.

MitigationUpgrade TeamCity to version 2023.05.2 or later to obtain the security patch. If immediate upgrade is not feasible, implement output encoding and input validation on GitHub integration parameters 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.2

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. Confirm TeamCity installation
    Access the TeamCity web interface or check for TeamCity services/processes running on the server. The version is typically displayed on the login page or in Administration > Diagnostics > Server Information.
    Affected if TeamCity is running and accessible
  2. Identify TeamCity version
    Navigate to Administration > Diagnostics > Server Information in the web UI, or check the startup logs for the version string. Compare the version number to 2023.05.2.
    Affected if Version is below 2023.05.2 (e.g., 2023.05.1, 2023.03.x, earlier versions)
  3. Verify GitHub integration is configured
    Navigate to Administration > GitHub in the TeamCity web UI. Check if any GitHub connections, repositories, or OAuth settings are configured.
    Affected if GitHub integration features are enabled or configured in TeamCity
  4. Inspect for signs of XSS exploitation
    Review TeamCity server logs (in <TeamCityHome>/logs directory) for unusual script tags, unexpected JavaScript executions, or suspicious request patterns in GitHub integration endpoints. Check user activity logs for unauthorized actions performed via injected scripts.
    Affected if Log entries show unexpected script content or indicators of malicious payload injection in GitHub-related requests

If TeamCity version is below 2023.05.2 AND the GitHub integration feature is enabled or configured, the environment is affected by this XSS vulnerability.

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.2 or later
Fixed in 2023.05.2
Interim mitigation

Upgrade TeamCity to version 2023.05.2 or later to obtain the security patch. If immediate upgrade is not feasible, implement output encoding and input validation on GitHub integration parameters as a compensating control.

Recommended fix High confidence

TeamCity 2023.05.2 or later

  1. Review TeamCity upgrade documentation at www.jetbrains.com/teamcity/docs
  2. Backup your existing TeamCity data and configuration
  3. Download TeamCity 2023.05.2 or later from the official JetBrains website
  4. Stop the current TeamCity server instance
  5. Install the new version following standard TeamCity upgrade procedures
  6. Start the upgraded TeamCity server
  7. Verify the GitHub integration functionality works correctly
  8. Confirm the XSS vulnerability is resolved by testing the GitHub integration
Caveat Review TeamCity release notes for any breaking changes between your current version and 2023.05.2 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
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,080
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,328.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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