dbcve.org
Actively exploited in the wild. This CVE is on the CISA Known Exploited Vulnerabilities list — treat remediation as urgent. Federal remediation due by 25 Oct 2023. Known ransomware use
TeamcityApplication · Jetbrains

CVE-2023-42793

CRITICAL · 9.8 CVSS v3.1 Published 2023-09-19
Fix available
A fix is available. Upgrade to 2023.05.4 or later.
See remediation →
100/100
Remediation priority · Urgent
In the wild Ransomware High EPSS Public exploit Remotely reachable No privileges Zero-click

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 · unedited
In JetBrains TeamCity before 2023.05.4 authentication bypass leading to RCE on TeamCity Server 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 confidence

JetBrains TeamCity servers before version 2023.05.4 contain an authentication bypass vulnerability that allows unauthenticated attackers to execute arbitrary code on the server. The flaw enables complete compromise of the TeamCity instance without valid credentials.

MitigationUpgrade TeamCity to version 2023.05.4 or later. If immediate patching is not possible, restrict network access to the TeamCity management interfaces and review logs for indicators of compromise.

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
TeamcityApplication
Affected:< 2023.05.4

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
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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify TeamCity installation and version
    Access the TeamCity web interface and navigate to the 'About' page (typically at /about.html) or check the version displayed in the server startup logs. The version is also visible in the footer of the TeamCity web pages.
    Affected if The displayed version is any version prior to 2023.05.4 (for example, 2023.05.3, 2023.04.x, earlier releases).
  2. Locate TeamCity version file
    On the server hosting TeamCity, locate the version information file typically found at <TeamCity_home>/webapps/TeamCity/version.txt or check the buildAgent/conf/buildAgent.properties for version references.
    Affected if The version.txt or configuration file contains a version number lower than 2023.05.4.
  3. Verify TeamCity service is running and exposed
    Confirm the TeamCity web service is actively running and accessible over network. Check if ports (default 8111) are listening and the server responds to HTTP/HTTPS requests without authentication.
    Affected if The TeamCity server is running and network-accessible on any port while running an affected version.
  4. Confirm authentication is enabled
    Review the TeamCity authentication configuration in the <TeamCity_home>/conf/internal.properties or through the Administration > Authentication page in the web UI. The vulnerability bypasses authentication mechanisms, so verify that authentication is the active security control.
    Affected if TeamCity authentication is enabled and the server runs an affected version below 2023.05.4.

Your environment is affected if the TeamCity server version is lower than 2023.05.4 and the web interface is network-accessible, regardless of authentication configuration, because the flaw allows bypassing those authentication mechanisms.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 2023.05.4 or later
Fixed in 2023.05.4
Interim mitigation

Upgrade TeamCity to version 2023.05.4 or later. If immediate patching is not possible, restrict network access to the TeamCity management interfaces and review logs for indicators of compromise.

Recommended fix High confidence

2023.05.4 or later

  1. Back up the TeamCity server data directory and configuration files before proceeding
  2. Stop the TeamCity server service
  3. Download TeamCity version 2023.05.4 or later from the official JetBrains website (www.jetbrains.com/teamcity/download)
  4. Install the new TeamCity version following the standard upgrade procedure
  5. After installation, start the TeamCity server service
  6. Verify the server starts successfully and the web interface is accessible
  7. Confirm the TeamCity version displayed in the administration area matches 2023.05.4 or later
Caveat Review TeamCity release notes for any breaking changes between your current version and 2023.05.4; major version upgrades may have configuration or plugin compatibility considerations

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Teamcity Exploited in the wild — priority engagement
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get it fixed fast

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-42793 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2023-42793 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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