CVE-2021-37547
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.2.4, insufficient checks during file uploading were made.
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 · low confidenceThis vulnerability in JetBrains TeamCity versions prior to 2020.2.4 involves insufficient validation checks during the file upload process. The lack of proper input sanitization and validation could allow attackers to upload files with potentially malicious characteristics or bypass intended upload restrictions.
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.2.4CVSS 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.
-
Identify TeamCity versionLog into the TeamCity web interface as an administrator and navigate to the Administration > Server Administration > Server Information page, or click the 'About' link typically found in the footer of the web UI. Record the exact version number displayed.Affected if The displayed version is any version prior to 2020.2.4 (for example, 2020.2.3, 2020.1.x, 2019.x, or earlier releases).
-
Confirm file upload capability existsCheck if the TeamCity server has any build configurations or projects that allow file uploads, such as artifact uploads, plugin installations, or attachment features. Navigate to a project's settings or a build configuration to see if upload-related options are present.Affected if File upload or artifact upload features are available and enabled on the server.
-
Verify server is accessibleConfirm the TeamCity web interface is reachable over the network and that unauthenticated or low-privilege users can access upload-related endpoints. Test by accessing the server URL directly.Affected if The server is exposed and accessible without immediate patching options.
The server is affected if it runs any version of JetBrains TeamCity prior to 2020.2.4 and has file upload functionality exposed, as the insufficient validation vulnerability can be exploited by attackers to upload potentially malicious files.
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.2.4
Upgrade TeamCity to version 2020.2.4 or later to remediate this vulnerability. If immediate upgrading is not possible, restrict file upload functionality to trusted users and implement additional server-side validation for uploaded files.
- Consultation2.0 h
- Implementation1.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,696.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-37547 — 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-37547 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