dbcve.org
TeamcityApplication · Jetbrains

CVE-2020-15830

MEDIUM · 6.1 CVSS v3.1 Published 2020-08-08
Fix available
A fix is available. Upgrade to 2019.2.3 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
JetBrains TeamCity before 2019.2.3 is vulnerable to stored XSS in the administration UI.

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

Stored XSS vulnerability in the administration UI of JetBrains TeamCity versions before 2019.2.3 allows authenticated attackers to inject malicious JavaScript that executes when administrators view the affected interface elements.

MitigationUpgrade TeamCity to version 2019.2.3 or later to remediate the stored XSS vulnerability in the administration UI.

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:< 2019.2.3

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 from web interface
    Log into TeamCity as an administrator and navigate to the Administration > Global Settings page. The current version is displayed at the top of this page.
    Affected if The displayed version number is lower than 2019.2.3 (for example, 2019.2.2, 2019.2.1, 2019.1.x, etc.)
  2. Identify TeamCity version from logs
    Check the teamcity-server.log file located in the <TeamCity_home>/logs directory for a line containing 'TeamCity version' near the start of the file.
    Affected if The logged version is lower than 2019.2.3
  3. Identify TeamCity version from configuration
    Inspect the version.xml file in the <TeamCity_home>/webapps/TeamCity/WEB-INF directory or check the build.properties file in the TeamCity data directory.
    Affected if The version indicated in these files is lower than 2019.2.3
  4. Verify administration UI accessibility
    Confirm access to the TeamCity Administration section by navigating to the root URL and clicking Administration, or accessing /admin/admin.html.
    Affected if The administration interface is accessible and the TeamCity version is below 2019.2.3

You are affected if your TeamCity installation version is 2019.2.2 or any earlier version (2019.2.1, 2019.1.x, etc.) and the administration UI is accessible in your environment.

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.

From vendor data
Upgrade available Upgrade to 2019.2.3 or later
Fixed in 2019.2.3
Interim mitigation

Upgrade TeamCity to version 2019.2.3 or later to remediate the stored XSS vulnerability in the administration UI.

Fix this in Teamcity Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,040
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,664.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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