| CVE-2020-7909 | ALTO7.5 | In JetBrains TeamCity before 2019.1.5, some server-stored passwords could be shown via the web UI. | 30/01/2020 |
| CVE-2020-7908 | MÉDIO4.3 | In JetBrains TeamCity before 2019.1.5, reverse tabnabbing was possible on several pages. | 30/01/2020 |
| CVE-2019-18367 | MÉDIO5.3 | In JetBrains TeamCity before 2019.1.2, a non-destructive operation could be performed by a user without the corresponding permissions. | 31/10/2019 |
| CVE-2019-18366 | MÉDIO5.3 | In JetBrains TeamCity before 2019.1.2, secure values could be exposed to users with the "View build runtime parameters and data" permission. | 31/10/2019 |
| CVE-2019-18365 | MÉDIO4.3 | In JetBrains TeamCity before 2019.1.4, reverse tabnabbing was possible on several pages. | 31/10/2019 |
| CVE-2019-18364 | CRÍTICO9.8 | In JetBrains TeamCity before 2019.1.4, insecure Java Deserialization could potentially allow remote code execution. | 31/10/2019 |
| CVE-2019-18363 | MÉDIO5.3 | In JetBrains TeamCity before 2019.1.2, access could be gained to the history of builds of a deleted build configuration under some circumstances. | 31/10/2019 |
| CVE-2019-15037 | MÉDIO6.1 | An issue was discovered in JetBrains TeamCity 2018.2.4. It had several XSS vulnerabilities on the settings pages. The issues were fixed in TeamCity 2019.1. | 02/10/2019 |
| CVE-2019-15036 | ALTO7.2 | An issue was discovered in JetBrains TeamCity 2018.2.4. A TeamCity Project administrator could execute any command on the server machine. The issue was fixed in TeamCity 2018.2.5 and 2019.1. | 02/10/2019 |
| CVE-2019-12157 | CRÍTICO9.8 | In JetBrains UpSource versions before 2018.2 build 1293, there is credential disclosure via RPC commands. | 02/10/2019 |
| CVE-2019-15035 | MÉDIO4.9 | An issue was discovered in JetBrains TeamCity 2018.2.4. A TeamCity Project administrator could get access to potentially confidential server-level data. The issue was fixed in TeamCity 2018.2.5 and 2019.1. | 01/10/2019 |
| CVE-2019-15042 | ALTO7.5 | An issue was discovered in JetBrains TeamCity 2018.2.4. It had no SSL certificate validation for some external https connections. This was fixed in TeamCity 2019.1. | 01/10/2019 |
| CVE-2019-15038 | ALTO7.5 | An issue was discovered in JetBrains TeamCity 2018.2.4. The TeamCity server was not using some security-related HTTP headers. The issue was fixed in TeamCity 2019.1. | 01/10/2019 |
| CVE-2019-15039 | CRÍTICO9.8 | An issue was discovered in JetBrains TeamCity 2018.2.4. It had a possible remote code execution issue. This was fixed in TeamCity 2019.1. | 01/10/2019 |
| CVE-2019-15848 | MÉDIO6.1 | JetBrains TeamCity 2019.1 and 2019.1.1 allows cross-site scripting (XSS), potentially making it possible to send an arbitrary HTTP request to a TeamCity server under the name of the currently logged-in user. | 05/09/2019 |
| CVE-2019-12846 | MÉDIO4.3 | A user without the required permissions could gain access to some JetBrains TeamCity settings. The issue was fixed in TeamCity 2018.2.2. | 03/07/2019 |
| CVE-2019-12845 | MÉDIO5.3 | The generated Kotlin DSL settings allowed usage of an unencrypted connection for resolving artifacts. The issue was fixed in JetBrains TeamCity 2018.2.3. | 03/07/2019 |
| CVE-2019-12844 | MÉDIO6.1 | A possible stored JavaScript injection was detected on one of the JetBrains TeamCity pages. The issue was fixed in TeamCity 2018.2.3. | 03/07/2019 |
| CVE-2019-12843 | MÉDIO6.1 | A possible stored JavaScript injection requiring a deliberate server administrator action was detected. The issue was fixed in JetBrains TeamCity 2018.2.3. | 03/07/2019 |
| CVE-2019-12842 | MÉDIO6.1 | A reflected XSS on a user page was detected on one of the JetBrains TeamCity pages. The issue was fixed in TeamCity 2018.2.2. | 03/07/2019 |