dbcve.org
TeamcityApplication · Jetbrains

CVE-2020-7911

MEDIUM · 6.1 CVSS v3.1 Published 2020-01-30
Fix available
A fix is available. Upgrade to 2019.2.0 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 2019.2, several user-level pages were vulnerable to XSS.

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

Cross-site scripting (XSS) vulnerability in JetBrains TeamCity affecting multiple user-level pages in versions prior to 2019.2. The vulnerability allows injection of malicious scripts through unsanitized user inputs displayed in user-level pages.

MitigationUpgrade TeamCity to version 2019.2 or later to receive the security patch for this XSS vulnerability.

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

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. Check TeamCity server version
    Log into the TeamCity web interface as an administrator and navigate to the Administration > Server Administration > Server Configuration page. The version number is displayed at the top of this page.
    Affected if The displayed version is any version prior to 2019.2.0 (for example, 2019.1.x, 2018.x, or earlier)
  2. Verify version via startup logs
    Inspect the TeamCity server startup logs (typically found in the TeamCity logs directory). The first few lines of the main log file usually contain the TeamCity version and build number.
    Affected if The logged version shows a build number earlier than 2019.2.0
  3. Check for patch version
    If the version appears to be 2019.2.x, verify the exact patch version in Administration > Server Administration > Server Configuration, or check the changelog/release notes for the specific patch level.
    Affected if The version is 2019.2.0 (the initial release without the security fix) or any 2019.1.x and earlier release

A user is affected if their TeamCity installation shows a version number below 2019.2.0, as this XSS vulnerability exists in all versions prior to that release.

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.0 or later
Fixed in 2019.2.0
Interim mitigation

Upgrade TeamCity to version 2019.2 or later to receive the security patch for this XSS vulnerability.

Fix this in Teamcity Scoped from the published advisory
  • Consultation2.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
13.0 hours of engineering $2,290
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,664.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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