dbcve.org
TeamcityApplication · Jetbrains

CVE-2019-12157

CRITICAL · 9.8 CVSS v3.1 Published 2019-10-02
Fix available
A fix is available. Upgrade to 2018.2.5 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 UpSource versions before 2018.2 build 1293, there is credential disclosure via RPC commands.

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 UpSource versions before 2018.2 build 1293 contain a vulnerability that allows credential disclosure through RPC commands. The vulnerability is exploitable remotely without authentication, allowing attackers to potentially obtain sensitive credentials used by the UpSource application.

MitigationUpgrade JetBrains UpSource to version 2018.2 build 1293 or later. If upgrading is not immediately possible, restrict network access to the UpSource RPC interface and ensure proper network segmentation.

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:< 2018.2.5
UpsourceApplication
Affected:<= 2018.2= 2018.2

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. Detect if JetBrains UpSource is installed
    Look for UpSource installation directories (commonly /opt/upsource or C:\Program Files\JetBrains\UpSource) or check for upsource-related processes running on the system
    Affected if UpSource software is found running on the system
  2. Determine the installed UpSource version
    Check the version information in the UpSource installation directory, typically found in a version file or About page within the UpSource web interface. Note the build number if available.
    Affected if version is 2018.2 or any version less than 2018.2 (the build number would be below 1293)
  3. Verify the RPC interface is network-accessible
    Check network configuration to determine if the UpSource RPC endpoint (typically port 9090 or configured RPC port) is exposed to the network or internet without authentication restrictions
    Affected if RPC interface is accessible without authentication from network
  4. Confirm version falls within affected range
    Compare the detected version and build number against the affected range: versions <= 2018.2 or exactly 2018.2 are vulnerable. Versions 2018.2 with build 1293 or later are fixed.
    Affected if installed version is 2018.2 or earlier, or build number is below 1293

The environment is affected if JetBrains UpSource is installed with version 2018.2 or earlier (build below 1293) and the RPC interface is network-accessible without authentication.

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

Upgrade JetBrains UpSource to version 2018.2 build 1293 or later. If upgrading is not immediately possible, restrict network access to the UpSource RPC interface and ensure proper network segmentation.

Recommended fix High confidence

UpSource 2018.2 build 1293 or later

  1. Back up the UpSource installation directory and database before upgrading
  2. Stop the UpSource service
  3. Download UpSource 2018.2 build 1293 or later from the official JetBrains website (jetbrains.com/upsource/download)
  4. Install the upgrade following JetBrains standard upgrade procedures
  5. Start the UpSource service
  6. Verify the upgrade was successful by checking the UpSource web interface and confirming the build version

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

Fix this in Teamcity Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,750
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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