dbcve.org
TeamcityApplication · Jetbrains

CVE-2021-31907

MEDIUM · 5.3 CVSS v3.1 Published 2021-05-11
Fix available
A fix is available. Upgrade to 2020.2.2 or later.
See remediation →
62/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click

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, permission checks for changing TeamCity plugins were implemented improperly.

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

JetBrains TeamCity before 2020.2.2 has an improper authorization vulnerability where permission checks for modifying TeamCity plugins were incorrectly implemented, potentially allowing unauthorized users to change plugins.

MitigationUpgrade TeamCity to version 2020.2.2 or later to remediate the improper permission check 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
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/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. Locate TeamCity installation directory
    Check common installation paths such as /opt/teamcity, C:\TeamCity, or the directory where TeamCity was installed. Look for the /webapps/root directory containing TeamCity files.
    Affected if TeamCity is found installed on the system
  2. Identify installed TeamCity version
    Check the version file typically located in the TeamCity root directory, or access the TeamCity server web interface and look for the version number displayed on the login page or in the Administration > Diagnostics section.
    Affected if The version displayed is lower than 2020.2.2 (for example, 2020.1.x, 2019.x, or earlier)
  3. Confirm plugin modification capability
    Log into the TeamCity web interface and navigate to Administration > Plugins List. Verify if you can access the plugin management area without proper administrative authorization.
    Affected if The web interface is accessible and the version is below 2020.2.2

If TeamCity is installed and the version is any release prior to 2020.2.2, the environment is affected by this improper authorization vulnerability in plugin modification permissions.

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 to remediate the improper permission check vulnerability.

Fix this in Teamcity Scoped from the published advisory
  • Consultation4.0 h
  • Implementation12.0 h
  • Testing6.0 h
  • Review / QA3.0 h
25.0 hours of engineering $4,400
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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