CVE-2023-50870
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 2023.11.1 a CSRF on login 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 · moderate confidenceA Cross-Site Request Forgery (CSRF) vulnerability in the TeamCity login mechanism allowed attackers to potentially force users to authenticate using the attacker's credentials, which could lead to session hijacking or unauthorized access to the victim's TeamCity account.
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< 2023.11.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
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
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.
-
Locate TeamCity version informationAccess the TeamCity server administration interface and navigate to 'Administration' > 'Server Administration' > 'Server Information', or check the 'version.txt' file in the TeamCity data directory (typically at <TeamCityDataDir>/config/version.txt)Affected if The displayed version number is less than 2023.11.1 (for example, 2023.11.0, 2023.05.4, etc.)
-
Confirm TeamCity web interface is accessibleVerify that the TeamCity web login page is reachable at the standard URL (typically /login.html or /)Affected if The login page is accessible to users over the network (this is the default configuration and required for the vulnerability to be exploitable)
-
Check for recent security updatesIn the TeamCity Administration panel, review the 'Server Health' section or check the 'Diagnostics' > 'Logs' for any mentions of security updates or CSRF-related fixesAffected if No security fix for CVE-2023-50870 is listed or the server log shows the version is still unpatched
You are affected if your TeamCity installation version is below 2023.11.1 and the web login interface is accessible to users or attackers.
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 · scoped2023.11.1
Upgrade JetBrains TeamCity to version 2023.11.1 or later to obtain the security fix.
2023.11.1
- Backup your TeamCity data directory and database before upgrading
- Stop the TeamCity server
- Download TeamCity 2023.11.1 or later from the official JetBrains website (www.jetbrains.com)
- Install the upgrade following the standard TeamCity upgrade procedure
- Start the TeamCity server and verify the login functionality works correctly
- Verify that the CSRF protection is now properly enforced on login endpoints
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,656.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-50870 — 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-2023-50870 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