dbcve.org
TeamcityApplication · Jetbrains

CVE-2020-35667

HIGH · 7.5 CVSS v3.1 Published 2021-02-03
Fix available
A fix is available. Upgrade to 2020.2.85695 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
JetBrains TeamCity Plugin before 2020.2.85695 SSRF. Vulnerability that could potentially expose user credentials.

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

An SSRF (Server-Side Request Forgery) vulnerability in JetBrains TeamCity Plugin versions prior to 2020.2.85695 allows attackers to make the server perform arbitrary requests to internal or external resources, potentially exposing sensitive user credentials stored in the TeamCity environment.

MitigationUpgrade the TeamCity Plugin to version 2020.2.85695 or later to remediate the SSRF 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.85695

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. Check TeamCity version
    Log in to TeamCity as administrator and navigate to Administration > Server Administration > Server Information, or check the buildServer.properties configuration file in the TeamCity data directory
    Affected if The displayed version is less than 2020.2.85695 (e.g., 2020.2, 2020.1, 10.x, etc.)
  2. Identify installed plugins
    Navigate to Administration > Plugins List in the TeamCity web UI, or inspect the plugins directory under <TeamCity_data_dir>/plugins
    Affected if The TeamCity plugin in question (the vulnerable plugin component) is present and its version is below 2020.2.85695
  3. Check plugin version details
    Click on the specific plugin in the Plugins List to view its version information, or examine the plugin's manifest file (plugin.xml or version.xml) within its directory in the plugins folder
    Affected if The plugin version shown is earlier than 2020.2.85695 or no version is displayed alongside an older TeamCity server version

You are affected if your TeamCity server version or the specific plugin version is below 2020.2.85695, as this indicates the vulnerable version of the TeamCity plugin is installed.

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.85695 or later
Fixed in 2020.2.85695
Interim mitigation

Upgrade the TeamCity Plugin to version 2020.2.85695 or later to remediate the SSRF vulnerability.

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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