dbcve.org
TeamcityApplication · Jetbrains

CVE-2021-37542

MEDIUM · 6.1 CVSS v3.1 Published 2021-08-06
Fix available
A fix is available. Upgrade to 2020.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
In JetBrains TeamCity before 2020.2.3, XSS 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 · moderate confidence

Cross-site scripting (XSS) vulnerability in JetBrains TeamCity versions prior to 2020.2.3 allows attackers to inject malicious scripts into the application. The specific injection point and attack vector are not detailed in the available description.

MitigationUpgrade JetBrains TeamCity to version 2020.2.3 or later to remediate this vulnerability. If immediate upgrade is not possible, implement output encoding and input validation as compensating controls.

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.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. Check TeamCity version in web interface
    Log into the TeamCity web UI and look at the footer of any page, or navigate to Administration > Diagnostics > Version. The version number is displayed there.
    Affected if The displayed version is any version prior to 2020.2.3 (e.g., 2020.2.2, 2020.1.x, 10.x, etc.)
  2. Check TeamCity version from logs
    Examine the TeamCity server logs located in <TeamCity_data_directory>/logs/teamcity-server.log. The version is logged at server startup.
    Affected if The version logged at startup is prior to 2020.2.3
  3. Check version from buildConfig.xml or internal properties
    Look for version information in the TeamCity data directory, typically in the config directory or in the TeamCity server startup scripts that may log or display the version.
    Affected if The version found is lower than 2020.2.3
  4. Confirm the TeamCity edition and build
    In Administration > Diagnostics > Version, note both the version number and the build number. Compare the full version string against the 2020.2.3 release.
    Affected if The version/build is older than the 2020.2.3 release

If the installed TeamCity version is any release prior to 2020.2.3, 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.

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

Upgrade JetBrains TeamCity to version 2020.2.3 or later to remediate this vulnerability. If immediate upgrade is not possible, implement output encoding and input validation as compensating controls.

Fix this in Teamcity Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA1.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-2021-37542 — 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-37542 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