dbcve.org
TeamcityApplication · Jetbrains

CVE-2021-25778

MEDIUM · 5.3 CVSS v3.1 Published 2021-02-03
Fix available
A fix is available. Upgrade to 2020.2.1 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.1, permissions during user deletion were checked 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 · high confidence

In JetBrains TeamCity before version 2020.2.1, the permission check logic during user deletion was flawed, potentially allowing unauthorized users to delete other users due to improper authorization validation in the user management functionality.

MitigationUpgrade JetBrains TeamCity to version 2020.2.1 or later to address the improper permission checking during user deletion.

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

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. Identify installed TeamCity version
    Navigate to the TeamCity administration page, typically at /admin/admin.html?item=about, or check the buildServer.properties file for the version number
    Affected if The version is lower than 2020.2.1 (for example, 2020.2.0, 2020.1.x, or earlier)
  2. Verify user management module is accessible
    Log in as a standard user and attempt to access the user management section at /admin/admin.html?item=users or check if user management links are visible in the administration area
    Affected if Non-administrator or unauthorized users can access the user management interface
  3. Confirm multiple user accounts exist
    Navigate to the Users page in TeamCity administration and list existing user accounts
    Affected if More than one user account exists in the system, making the deletion vulnerability exploitable
  4. Check for proper authorization enforcement
    Using a non-administrator account, attempt to delete a different user account through the UI or API endpoint for user deletion
    Affected if The deletion request succeeds or is processed without proper authorization error

A TeamCity installation is affected if it runs version 2020.2.0 or earlier and has user management functionality accessible to users who should not have deletion 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.1 or later
Fixed in 2020.2.1
Interim mitigation

Upgrade JetBrains TeamCity to version 2020.2.1 or later to address the improper permission checking during user deletion.

Fix this in Teamcity Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing3.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,570
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,512.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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