dbcve.org
UpsourceApplication · Jetbrains

CVE-2019-12156

MEDIUM · 5.3 CVSS v3.1 Published 2019-10-02
Fix available
A fix is available. Upgrade to 2018.2.1290 or later.
See remediation →
62/100
Remediation priority · Elevated
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
Server metadata could be exposed because one of the error messages reflected the whole response back to the client in JetBrains TeamCity versions before 2018.2.5 and UpSource versions before 2018.2 build 1293.

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

Information disclosure vulnerability in JetBrains TeamCity and UpSpeed where error messages reflect the entire server response back to the client, potentially exposing server metadata such as version information, internal paths, or configuration details.

MitigationUpgrade to TeamCity version 2018.2.5 or later, or UpSource version 2018.2 build 1293 or later to eliminate the reflected response behavior in error handling.

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
UpsourceApplication
Affected:< 2018.2.1290

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
Low
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N

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. Confirm UpSource is installed
    Locate UpSource installation directory or check running processes for upsource-related services
    Affected if UpSource server is present in the environment
  2. Identify UpSource version
    Check version file in UpSource installation (typically in version.txt or via /about endpoint if available) or examine startup logs
    Affected if Running version is below 2018.2.1290
  3. Compare version to affected range
    Compare your installed version against the vulnerable range: UpSource < 2018.2.1290
    Affected if Installed version is 2018.2.1290 or any earlier version
  4. Test error response behavior
    Trigger an error condition (such as an invalid request) and inspect the HTTP response body
    Affected if Error responses contain the full server response, version strings, internal paths, or configuration details rather than generic messages

The environment is affected if UpSource is running and its version is earlier than 2018.2.1290 and error responses expose server metadata.

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.

From vendor data
Upgrade available Upgrade to 2018.2.1290 or later
Fixed in 2018.2.1290
Interim mitigation

Upgrade to TeamCity version 2018.2.5 or later, or UpSource version 2018.2 build 1293 or later to eliminate the reflected response behavior in error handling.

Fix this in Upsource Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,040
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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