CVE-2020-15829
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 2019.2.3, password parameters could be disclosed via build logs.
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 JetBrains TeamCity versions prior to 2019.2.3, password-type parameters used in build configurations were being written in plain text to build logs. This exposed sensitive credentials to anyone with access to view those 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< 2019.2.3CVSS 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.
-
Check TeamCity versionAccess the TeamCity administration web interface and navigate to 'About' or check the version displayed on the login page. Alternatively, check the version from the server startup logs or the TeamCity installation directory.Affected if The installed version is any version prior to 2019.2.3 (e.g., 2019.2.2, 2019.2.1, 2019.2.0, earlier releases).
-
Identify password-type parameters in build configurationsReview all build configurations in the TeamCity web interface under 'Build Configurations' and inspect parameter definitions. Look for parameters with type 'password' or those explicitly marked as sensitive.Affected if Any build configuration contains password-type parameters that have been used in build steps.
-
Examine build logs for plain text credentialsAccess the build logs for builds that used password-type parameters. Navigate to a specific build run, open the build log, and search for the parameter names or look for visible password strings in the log output.Affected if Build logs contain the actual password values in plain text rather than being masked or hidden.
-
Audit build log visibility settingsCheck who has access to view build logs in TeamCity by examining project and build configuration permissions. Determine if unauthorized or unexpected users can access these logs.Affected if Build logs with exposed credentials are accessible to users beyond those who need to know the credentials.
You are affected if your TeamCity version is prior to 2019.2.3 AND you have build configurations using password-type parameters, as those passwords may have been written in plain text to 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 data2019.2.3
Upgrade TeamCity to version 2019.2.3 or later, and audit existing build logs and configurations to identify and rotate any exposed credentials.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.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 $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-15829 — 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-15829 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