CVE-2021-31910
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.3, information disclosure via SSRF was 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 · high confidenceIn JetBrains TeamCity before version 2020.2.3, a Server-Side Request Forgery (SSRF) vulnerability allowed attackers to induce the server to make arbitrary HTTP requests to internal or external resources, potentially exposing sensitive internal information and enabling further network-based attacks.
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.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
- 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.
-
Confirm TeamCity installationIdentify if JetBrains TeamCity is running on the system by checking for TeamCity processes or listening on common TeamCity ports (default 8111).Affected if TeamCity is installed and running
-
Determine installed TeamCity versionAccess the TeamCity web interface and navigate to the Administration > Server Administration page, or check the version.py or buildServer.properties file in the TeamCity data directory.Affected if The installed version cannot be determined or is visible
-
Compare version to affected rangeReview the detected version against the affected range: any version prior to 2020.2.3 is vulnerable.Affected if The installed version is lower than 2020.2.3 (for example, 2020.2.2, 2020.2.1, 2020.2.0, 2020.1.x, or earlier)
-
Check for external HTTP request capabilityReview if the server has outbound network access or if features that make HTTP requests (such as issue tracker integration, webhook endpoints, or external artifact storage) are configured.Affected if The server can make outbound HTTP requests and the TeamCity version is below 2020.2.3
If the installed TeamCity version is 2020.2.2 or any earlier version, the server is vulnerable to SSRF attacks via features that trigger HTTP requests.
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.3
Upgrade JetBrains TeamCity to version 2020.2.3 or later. Additionally, apply network segmentation and restrict outbound access from the TeamCity server to minimize the impact of SSRF exploitation.
- Consultation4.0 h
- Implementation2.0 h
- Testing6.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 $3,872.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-31910 — 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-31910 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