Filtered by vendor Jetbrains
Subscriptions
Filtered by product Teamcity
Subscriptions
Total
221 CVE
CVE | Vendors | Products | Updated | CVSS v3.1 |
---|---|---|---|---|
CVE-2020-27627 | 1 Jetbrains | 1 Teamcity | 2024-11-21 | 6.1 Medium |
JetBrains TeamCity before 2020.1.2 was vulnerable to URL injection. | ||||
CVE-2020-15831 | 1 Jetbrains | 1 Teamcity | 2024-11-21 | 6.1 Medium |
JetBrains TeamCity before 2019.2.3 is vulnerable to reflected XSS in the administration UI. | ||||
CVE-2020-15830 | 1 Jetbrains | 1 Teamcity | 2024-11-21 | 6.1 Medium |
JetBrains TeamCity before 2019.2.3 is vulnerable to stored XSS in the administration UI. | ||||
CVE-2020-15829 | 1 Jetbrains | 1 Teamcity | 2024-11-21 | 5.3 Medium |
In JetBrains TeamCity before 2019.2.3, password parameters could be disclosed via build logs. | ||||
CVE-2020-15828 | 1 Jetbrains | 1 Teamcity | 2024-11-21 | 6.5 Medium |
In JetBrains TeamCity before 2020.1.1, project parameter values can be retrieved by a user without appropriate permissions. | ||||
CVE-2020-15826 | 1 Jetbrains | 1 Teamcity | 2024-11-21 | 4.3 Medium |
In JetBrains TeamCity before 2020.1, users are able to assign more permissions than they have. | ||||
CVE-2020-15825 | 1 Jetbrains | 1 Teamcity | 2024-11-21 | 8.8 High |
In JetBrains TeamCity before 2020.1, users with the Modify Group permission can elevate other users' privileges. | ||||
CVE-2020-11938 | 1 Jetbrains | 1 Teamcity | 2024-11-21 | 4.9 Medium |
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. | ||||
CVE-2020-11689 | 1 Jetbrains | 1 Teamcity | 2024-11-21 | 6.5 Medium |
In JetBrains TeamCity before 2019.2.1, a user without appropriate permissions was able to import settings from the settings.kts file. | ||||
CVE-2020-11688 | 1 Jetbrains | 1 Teamcity | 2024-11-21 | 7.5 High |
In JetBrains TeamCity before 2019.2.1, the application state is kept alive after a user ends his session. | ||||
CVE-2020-11687 | 1 Jetbrains | 1 Teamcity | 2024-11-21 | 7.5 High |
In JetBrains TeamCity before 2019.2.2, password values were shown in an unmasked format on several pages. | ||||
CVE-2020-11686 | 1 Jetbrains | 1 Teamcity | 2024-11-21 | 2.7 Low |
In JetBrains TeamCity before 2019.1.4, a project administrator was able to retrieve some TeamCity server settings. | ||||
CVE-2019-18367 | 1 Jetbrains | 1 Teamcity | 2024-11-21 | 5.3 Medium |
In JetBrains TeamCity before 2019.1.2, a non-destructive operation could be performed by a user without the corresponding permissions. | ||||
CVE-2019-18366 | 1 Jetbrains | 1 Teamcity | 2024-11-21 | 5.3 Medium |
In JetBrains TeamCity before 2019.1.2, secure values could be exposed to users with the "View build runtime parameters and data" permission. | ||||
CVE-2019-18365 | 1 Jetbrains | 1 Teamcity | 2024-11-21 | 4.3 Medium |
In JetBrains TeamCity before 2019.1.4, reverse tabnabbing was possible on several pages. | ||||
CVE-2019-18364 | 1 Jetbrains | 1 Teamcity | 2024-11-21 | 9.8 Critical |
In JetBrains TeamCity before 2019.1.4, insecure Java Deserialization could potentially allow remote code execution. | ||||
CVE-2019-18363 | 1 Jetbrains | 1 Teamcity | 2024-11-21 | 5.3 Medium |
In JetBrains TeamCity before 2019.1.2, access could be gained to the history of builds of a deleted build configuration under some circumstances. | ||||
CVE-2019-15848 | 1 Jetbrains | 1 Teamcity | 2024-11-21 | N/A |
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. | ||||
CVE-2019-15042 | 1 Jetbrains | 1 Teamcity | 2024-11-21 | 7.5 High |
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. | ||||
CVE-2019-15039 | 1 Jetbrains | 1 Teamcity | 2024-11-21 | 9.8 Critical |
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. |