Server metadata could be exposed because one of the error messages reflected the whole response back to the client in JetBrains TeamCity ve…

published 2019-10-02 7y ago modified 2026-06-17 4mo ago also EUVD-2019-3805

cvss: 5.3; version 3.1, NVD
cisa kev: Not listed; not in CISA's catalog
epss: 0.9%; EPSS 0.9% chance of exploitation in 30 days, percentile 60%
public exploits: 0; none known

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.

Patch / fix

fixed in 1

jetbrains upsource 2018.2.1290

Is CVE-2019-12156 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Exploit prediction

0.90% chance of exploitation in the next 30 days, higher than 60% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by	version	score	vector
NVD	3.1	5.3	CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
NVD	2.0	5.0	AV:N/AC:L/Au:N/C:P/I:N/A:N

Classification

Weakness

CWE-209 Generation of Error Message Containing Sensitive Information

References

blog.jetbrains.com /blog/2019/09/26/jetbrains-security-bulletin-q2-2019/
vendor-advisory

Sources

CVE List CVE-2019-12156
NVD CVE-2019-12156

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.