dbcve.org
TeamcityApplication · Jetbrains

CVE-2019-18364

CRITICAL · 9.8 CVSS v3.1 Published 2019-10-31
Fix available
A fix is available. Upgrade to 2019.1.4 or later.
See remediation →
100/100
Remediation priority · Urgent
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 2019.1.4, insecure Java Deserialization could potentially allow remote code execution.

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 confidence

JetBrains TeamCity before version 2019.1.4 is vulnerable to insecure Java deserialization, which could allow an unauthenticated attacker to execute arbitrary code remotely by sending maliciously crafted serialized objects to the application.

MitigationUpgrade TeamCity to version 2019.1.4 or later. If immediate upgrade is not possible, restrict network access to the TeamCity server and disable any exposed deserialization endpoints.

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:< 2019.1.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. Check TeamCity version in web interface
    Log into TeamCity as an administrator and navigate to Administration > Server Administration. The version number is displayed on this page.
    Affected if Version shown is earlier than 2019.1.4
  2. Check TeamCity version in server logs
    Locate the TeamCity server logs in the logs directory (typically <TeamCityHome>/logs/teamcity-server.log). Open the most recent log file and search for a line containing 'Server version' or the build number.
    Affected if Log shows a version earlier than 2019.1.4
  3. Check TeamCity version from build number file
    Access the TeamCity server file system and open the build.txt file located in the TeamCity installation root directory. This file contains the exact build version number.
    Affected if Build number is lower than the 2019.1.4 release
  4. Confirm server is running and accessible
    Attempt to access the TeamCity web interface via HTTP/HTTPS on the configured port (default 8111). If the login page or dashboard loads, the server is running and the vulnerable deserialization endpoint is active.
    Affected if Server responds to requests and the web interface is reachable

The environment is affected if the installed TeamCity version is before 2019.1.4 and the server is operational and network-accessible.

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 2019.1.4 or later
Fixed in 2019.1.4
Interim mitigation

Upgrade TeamCity to version 2019.1.4 or later. If immediate upgrade is not possible, restrict network access to the TeamCity server and disable any exposed deserialization endpoints.

Recommended fix High confidence

2019.1.4

  1. Back up the TeamCity data directory and database before proceeding with the upgrade
  2. Download TeamCity version 2019.1.4 or later from the official JetBrains website (www.jetbrains.com/teamcity/download)
  3. Stop the TeamCity server service
  4. Run the installer for the new TeamCity version
  5. When prompted, specify the existing TeamCity data directory to preserve configuration and build history
  6. Complete the installation wizard and start the TeamCity server
  7. Log in to the TeamCity web interface and verify all projects and builds are accessible
  8. Confirm the TeamCity version shows 2019.1.4 or later in the Administration > Diagnostics section

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

Fix this in Teamcity Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing6.0 h
  • Review / QA3.0 h
16.0 hours of engineering $2,760
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2019-18364 — 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-2019-18364 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