dbcve.org
TeamcityApplication · Jetbrains

CVE-2021-3315

MEDIUM · 5.4 CVSS v3.1 Published 2021-05-11
Fix available
A fix is available. Upgrade to 2020.2.2 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 2020.2.2, stored XSS on a tests page 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

Stored cross-site scripting (XSS) vulnerability in JetBrains TeamCity's tests page allows attackers to inject malicious scripts that persist and execute when other users view the affected test pages, due to insufficient input sanitization on the tests functionality.

MitigationUpgrade TeamCity to version 2020.2.2 or later, which contains the fix for this stored 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:< 2020.2.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
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. Identify installed TeamCity version
    Navigate to the TeamCity administration dashboard and locate the 'About' page (typically at /about.html) or check the buildAgent.properties file on the server. The version number is displayed in the format like '2020.1.3' or similar.
    Affected if The displayed version is any version prior to 2020.2.2 (for example, 2020.2.1, 2020.1.x, 2019.x, etc.)
  2. Verify tests functionality is accessible
    Check if the 'Tests' tab or test-related pages are accessible within TeamCity projects. This is typically found under project build configurations or test reports. Inspect whether regular users or anonymous users can access test result pages.
    Affected if The tests functionality is enabled and accessible to users who can view build configurations or test reports.
  3. Confirm user access to test reports
    Review TeamCity user roles and permissions to determine which users can access the tests page. Check if users with limited privileges (such as project viewers or guests) can open test-related pages.
    Affected if Users other than administrators can view test pages, as the XSS executes when these users access the affected test pages.

Your environment is affected if the installed TeamCity version is any release prior to 2020.2.2 and the tests functionality is accessible to users beyond administrators.

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 2020.2.2 or later
Fixed in 2020.2.2
Interim mitigation

Upgrade TeamCity to version 2020.2.2 or later, which contains the fix for this stored XSS vulnerability.

Fix this in Teamcity Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing6.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,580
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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