CVE-2021-37548
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 2021.1, passwords in cleartext sometimes could be stored in VCS.
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 before version 2021.1, a vulnerability existed where user passwords could occasionally be stored in cleartext within VCS (Version Control System) repositories instead of being properly hashed or encrypted, exposing credentials to anyone with repository access.
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< 2021.1CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify installed TeamCity versionNavigate to the TeamCity administration dashboard and locate the version number typically displayed on the login page or in the 'Administration > Server Administration' section, or check the buildServer.properties file in the TeamCity data directory for the version propertyAffected if The installed version is any release prior to 2021.1 (e.g., 2020.x, 2019.x, etc.)
-
Determine if VCS repositories are configuredIn the TeamCity administration interface, navigate to 'Version Control Settings' under each project or check the server configuration for VCS roots. Look for any VCS (Git, Subversion, Perforce, etc.) integrations listed in the administration consoleAffected if Any VCS repositories are connected to TeamCity and were in use during the affected version timeframe
-
Audit VCS commit history for cleartext credentialsClone or access the connected VCS repositories and search commit messages, diffs, or file contents for patterns resembling passwords (e.g., grep for strings like 'password=', 'pwd=', or perform a search for any stored password fields from TeamCity configuration files that may have been committed)Affected if Any commits, branches, or repository files contain plaintext passwords, authentication tokens, or credential strings that match TeamCity user accounts
-
Inspect VCS root configurations in TeamCityReview each VCS root configuration in TeamCity (Administration > VCS Roots) to check if any VCS credentials were stored and whether they may have been inadvertently exposed in repository metadata or commit logsAffected if VCS roots contain stored credentials that could have been logged or cached in plaintext form
A user is affected if their TeamCity installation version is below 2021.1 AND they have configured VCS repositories, as the cleartext password storage vulnerability could have exposed credentials to anyone with repository access.
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 data2021.1
Upgrade to TeamCity 2021.1 or later, then audit VCS repositories and history for any exposed cleartext passwords and rotate all potentially compromised credentials.
- Consultation2.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-37548 — 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-2021-37548 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