CVE-2021-43199
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.2, permission checks in the Create Patch functionality are insufficient.
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.2, the Create Patch functionality lacked proper permission checks, allowing users to potentially create patches for builds or projects they should not have access to, constituting an insecure direct object reference (IDOR) or authorization bypass 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< 2021.1.2.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
- None
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/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 installed TeamCity versionNavigate to Administration > Troubleshooting > About TeamCity or access /about.html page to view the exact version numberAffected if The displayed version is lower than 2021.1.2 (e.g., 2021.1, 2021.1.1, 2020.x, etc.)
-
Verify Create Patch feature existsCheck if the 'Create Patch' option is available in the web UI under Build Configuration settings or via the patch creation endpointAffected if The Create Patch functionality is present and enabled in the TeamCity installation
-
Review user permissions on projectsNavigate to Administration > Users and Groups > select a user with limited project access > verify which projects/builds they are authorized to viewAffected if Users exist with restricted project access permissions
-
Test unauthorized patch access (if permissions allow)Using a user account with limited access, attempt to access the Create Patch feature for a build/project outside their granted permissions via URL or API endpointAffected if A user can successfully create or download a patch for a build/project they were not explicitly granted access to, indicating the authorization bypass is present
You are affected if your TeamCity version is below 2021.1.2 and users with limited permissions can access the Create Patch feature for builds or projects outside their authorized scope.
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.2.
Upgrade TeamCity to version 2021.1.2 or later to obtain the patched permission validation logic for the Create Patch feature.
TeamCity 2021.1.2 or later
- 1. Back up your current TeamCity data and configuration.
- 2. Download TeamCity 2021.1.2 or a later stable version from the official JetBrains website.
- 3. Stop the TeamCity server.
- 4. Install the upgraded version following the standard TeamCity upgrade documentation.
- 5. Start the TeamCity server and verify the Create Patch functionality works correctly.
- 6. Verify that unauthorized users can no longer access the Create Patch functionality without proper permissions.
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-43199 — 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-43199 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