CVE-2021-43196
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, information disclosure via the Docker Registry connection dialog is possible.
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 confidenceIn JetBrains TeamCity versions prior to 2021.1, the Docker Registry connection dialog contained an information disclosure vulnerability that could expose sensitive data, likely including credentials, authentication tokens, or configuration details used when connecting to Docker registries.
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.
-
Check TeamCity versionNavigate to Administration > Server Administration > Server Configuration or check the footer of any TeamCity page for the version numberAffected if The version displayed is earlier than 2021.1 (for example, 2020.2, 2020.1, 10.x, etc.)
-
Identify Docker Registry connectionsGo to Administration > Docker > Registry connections (or navigate to project settings and look for Docker registry or container registry configurations)Affected if Any Docker Registry connections exist in the TeamCity instance
-
Check for stored credentials in Docker settingsReview the Docker registry connection settings for any fields containing passwords, tokens, or authentication credentials that may have been savedAffected if Credentials or tokens were saved in the Docker Registry connection dialog and are visible or accessible through the UI
-
Audit user access to Docker settingsReview user permissions for who can access the Docker Registry connection configuration pagesAffected if Multiple users have administrative access to view Docker registry configurations where credentials may be exposed
You are affected if your TeamCity version is earlier than 2021.1 AND you have configured Docker Registry connections in TeamCity, as the vulnerability lies in the Docker Registry connection dialog.
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.
dbcve · scoped2021.1
Upgrade TeamCity to version 2021.1 or later to obtain the security fix. Review and rotate any credentials that may have been transmitted through the vulnerable Docker Registry connection dialog.
TeamCity 2021.1 or later (recommend latest stable release)
- 1. Back up your TeamCity data directory and database before proceeding with any upgrade
- 2. Download TeamCity 2021.1 or a later stable version from the official JetBrains website (www.jetbrains.com/teamcity/download/)
- 3. Stop the TeamCity server service
- 4. Install the new TeamCity version following the official upgrade documentation
- 5. Start the TeamCity server and verify all services are running correctly
- 6. Test that the Docker Registry connection functionality works as expected
- 7. Verify that the vulnerability is no longer present by checking that sensitive information is not disclosed in the Docker Registry connection dialog
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation1.0 h
- Implementation2.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 $1,664.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-43196 — 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-43196 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