CVE-2023-34218
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.05 bypass of permission checks allowing to perform admin actions 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 permission bypass vulnerability in JetBrains TeamCity versions prior to 2023.05 allowed unauthenticated or low-privilege users to bypass authorization checks and perform administrative actions, achieving full administrative control over the TeamCity server.
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.05CVSS 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
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/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.
-
Identify installed TeamCity versionAccess the TeamCity administration web interface and navigate to 'Administration' > 'Server Administration' > 'Server Information', or check the buildServer.properties configuration file in the TeamCity data directory for the version numberAffected if The displayed version number is lower than 2023.05 (for example, 2023.04.x, 2023.03.x, or any earlier release)
-
Verify TeamCity server is reachable over the networkConfirm the TeamCity web interface URL is accessible from the network or internet, or check server listening ports (default 8111) with tools like netstat or ssAffected if The server is network-accessible AND the version is below 2023.05, as unauthenticated attackers could exploit the permission bypass remotely
-
Review server logs for unauthorized administrative actionsExamine TeamCity server logs in the <TeamCity data>/logs directory, specifically looking for administrative actions performed by users who should not have elevated privilegesAffected if Log entries show administrative operations (such as project creation, user management, or build configuration changes) performed by unauthenticated or low-privilege accounts
If the TeamCity version is below 2023.05 and the server is network-accessible, the environment is vulnerable to the permission bypass described in this CVE.
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.05
Upgrade TeamCity to version 2023.05 or later to apply the permission check fix.
2023.05
- Back up your TeamCity database and configuration files before upgrading
- Download TeamCity version 2023.05 or later from the official JetBrains website
- Stop the TeamCity server
- Follow the official TeamCity upgrade instructions for your deployment method
- Start the upgraded TeamCity server
- Verify the upgrade was successful by checking the version in the UI and confirming admin actions require proper authorization
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.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,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-34218 — 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-34218 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