CVE-2020-27629
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 · uneditedIn JetBrains TeamCity before 2020.1.5, secure dependency parameters could be not masked in depending builds when there are no internal artifacts.
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 confidenceIn TeamCity versions before 2020.1.5, secure dependency parameters (such as passwords or tokens used in build configurations) were not properly masked in the output of depending builds when the dependency build produced no internal artifacts. This could result in sensitive credentials being exposed in build logs.
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< 2020.1.5CVSS 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
- Low
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/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 checksWork through these to decide whether this CVE applies to you.
-
Determine your TeamCity server versionLog into the TeamCity web interface as administrator and navigate to Administration > Server Administration > Server Configuration, or use the REST API endpoint /app/rest/server/version to retrieve the version number.Affected if The installed version is earlier than 2020.1.5 (for example, 2020.1.4, 2020.1.3, etc.)
-
Identify build configurations with snapshot dependencies using secure parametersReview your build configurations in the TeamCity UI. For each configuration, examine the Dependencies > Snapshot Dependencies section. Check if any dependency parameters are set as secure (password or token type) in the dependency settings.Affected if There are build configurations that have snapshot dependencies with secure parameters configured
-
Check for dependency builds that produced no internal artifactsIn the TeamCity web interface, locate builds in your dependency chains and verify if the dependency builds have zero artifacts. This can be done by viewing the Artifacts tab of each dependency build.Affected if Any builds that your configurations depend on have produced zero internal artifacts
-
Audit build logs of dependent builds for exposed credentialsNavigate to the build results of builds that depend on builds with no artifacts. Open the build log (View logs) and search for any occurrences of your secure parameter names. Look for unmasked values that appear in plain text rather than being shown as '********' or similar masked format.Affected if Build logs contain unmasked values of secure dependency parameters (passwords, tokens) that should have been hidden
You are affected if your TeamCity version is earlier than 2020.1.5 AND you have build configurations with snapshot dependencies that use secure parameters where the dependency builds produced no artifacts, resulting in exposed credentials in dependent build logs.
Generated from the published advisory. Verify against your own configuration.
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 data2020.1.5
Upgrade TeamCity to version 2020.1.5 or later, which properly masks secure dependency parameters regardless of artifact status. Audit existing build logs for potential credential exposure.
- Consultation3.0 h
- Implementation6.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-27629 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2020-27629 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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