dbcve.org
TeamcityApplication · Jetbrains

CVE-2020-7909

HIGH · 7.5 CVSS v3.1 Published 2020-01-30
Fix available
A fix is available. Upgrade to 2019.1.5 or later.
See remediation →
84/100
Remediation priority · High
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 2019.1.5, some server-stored passwords could be shown via the web UI.

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

In JetBrains TeamCity versions prior to 2019.1.5, an information disclosure vulnerability existed where certain server-stored passwords were rendered visible through the web UI, potentially exposing sensitive authentication credentials to unauthorized users.

MitigationUpgrade TeamCity to version 2019.1.5 or later to remediate the password exposure 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.1.5

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
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/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 TeamCity version
    Access the TeamCity web UI and navigate to Administration > Server Administration > Server Information, or check the version.txt file in the TeamCity data directory
    Affected if The displayed version is any version prior to 2019.1.5 (e.g., 2019.1.4, 2019.1.3, 2019.0.x, etc.)
  2. Verify password storage is in use
    Check if any authentication credentials are stored in TeamCity by reviewing the authentication settings under Administration > Authentication
    Affected if Any user passwords, API tokens, or connection credentials are stored within TeamCity's internal storage
  3. Confirm web UI access exists
    Determine whether the TeamCity web interface is accessible to users beyond the system administrator account
    Affected if Multiple user accounts or anonymous access is enabled and the web UI is reachable on the network
  4. Check for unauthorized user accounts
    Review the user list under Administration > Users to identify all accounts with access to the TeamCity server
    Affected if There are user accounts other than the primary administrator who could potentially view the exposed passwords through the web UI

You are affected if your TeamCity version is below 2019.1.5 and you have passwords or credentials stored in TeamCity accessible through the web UI to any users beyond the administrator.

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.1.5 or later
Fixed in 2019.1.5
Interim mitigation

Upgrade TeamCity to version 2019.1.5 or later to remediate the password exposure vulnerability.

Fix this in Teamcity Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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