dbcve.org
TeamcityApplication · Jetbrains

CVE-2020-15828

MEDIUM · 6.5 CVSS v3.1 Published 2020-08-08
Fix available
A fix is available. Upgrade to 2020.1.1 or later.
See remediation →
71/100
Remediation priority · Elevated
Remotely reachable 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.1.1, project parameter values can be retrieved by a user without appropriate permissions.

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.1.1, an authorization flaw allows users to retrieve project parameter values (which may contain sensitive information like API keys, credentials, or secrets) without having the appropriate permissions, leading to information disclosure.

MitigationUpgrade TeamCity to version 2020.1.1 or later to address the unauthorized parameter access 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.1.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
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/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 installation
    Check if TeamCity is running by looking for the process (teamcity-server, teamcity) or by accessing the web UI on the default port (typically 8111)
    Affected if TeamCity is not found or not accessible on expected ports
  2. Determine installed TeamCity version
    Access the TeamCity web interface and navigate to the 'About' page (typically at /about.html) or check the version.txt file in the TeamCity data directory
    Affected if The version cannot be determined or the TeamCity instance is not accessible
  3. Compare version against vulnerable range
    Compare the installed version number to 2020.1.1 - versions below this (e.g., 2020.1, 2019.x, 2018.x, etc.) are affected
    Affected if Installed version is less than 2020.1.1 (for example, 2020.1.0, 2019.2.2, 2019.1.4, etc.)
  4. Verify parameter access authorization (optional)
    As a user with limited permissions, attempt to access project parameters via the API endpoint /app/rest/projects/<projectId>/parameters or through the web UI settings
    Affected if A user without 'View project parameters' permission can retrieve sensitive parameter values

You are affected if your TeamCity installation version is less than 2020.1.1 and users without proper permissions can access project parameter values.

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.1.1 or later
Fixed in 2020.1.1
Interim mitigation

Upgrade TeamCity to version 2020.1.1 or later to address the unauthorized parameter access vulnerability.

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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