CVE |
Vendors |
Products |
Updated |
CVSS v3.1 |
JetBrains TeamCity before 2019.2.3 is vulnerable to reflected XSS in the administration UI. |
JetBrains TeamCity before 2019.2.3 is vulnerable to stored XSS in the administration UI. |
In JetBrains TeamCity before 2019.2.3, password parameters could be disclosed via build logs. |
In JetBrains TeamCity before 2020.1.1, project parameter values can be retrieved by a user without appropriate permissions. |
In JetBrains TeamCity before 2020.1, users are able to assign more permissions than they have. |
In JetBrains TeamCity before 2020.1, users with the Modify Group permission can elevate other users' privileges. |
In JetBrains TeamCity 2018.2 through 2019.2.1, a project administrator was able to see scrambled password parameters used in a project. The issue was resolved in 2019.2.2. |
In JetBrains TeamCity before 2019.2.1, a user without appropriate permissions was able to import settings from the settings.kts file. |
In JetBrains TeamCity before 2019.2.1, the application state is kept alive after a user ends his session. |
In JetBrains TeamCity before 2019.2.2, password values were shown in an unmasked format on several pages. |
In JetBrains TeamCity before 2019.1.4, a project administrator was able to retrieve some TeamCity server settings. |
In JetBrains TeamCity before 2019.1.2, a non-destructive operation could be performed by a user without the corresponding permissions. |
In JetBrains TeamCity before 2019.1.2, secure values could be exposed to users with the "View build runtime parameters and data" permission. |
In JetBrains TeamCity before 2019.1.4, reverse tabnabbing was possible on several pages. |
In JetBrains TeamCity before 2019.1.4, insecure Java Deserialization could potentially allow remote code execution. |
In JetBrains TeamCity before 2019.1.2, access could be gained to the history of builds of a deleted build configuration under some circumstances. |
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. |
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. |
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. |
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. |