Filtered by vendor Jetbrains
Subscriptions
Filtered by product Teamcity
Subscriptions
Total
173 CVE
CVE | Vendors | Products | Updated | CVSS v3.1 |
---|---|---|---|---|
CVE-2021-37544 | 1 Jetbrains | 1 Teamcity | 2024-11-21 | 9.8 Critical |
In JetBrains TeamCity before 2020.2.4, there was an insecure deserialization. | ||||
CVE-2021-37542 | 1 Jetbrains | 1 Teamcity | 2024-11-21 | 6.1 Medium |
In JetBrains TeamCity before 2020.2.3, XSS was possible. | ||||
CVE-2021-31915 | 1 Jetbrains | 1 Teamcity | 2024-11-21 | 9.8 Critical |
In JetBrains TeamCity before 2020.2.4, OS command injection leading to remote code execution was possible. | ||||
CVE-2021-31914 | 2 Jetbrains, Microsoft | 2 Teamcity, Windows | 2024-11-21 | 9.8 Critical |
In JetBrains TeamCity before 2020.2.4 on Windows, arbitrary code execution on TeamCity Server was possible. | ||||
CVE-2021-31913 | 1 Jetbrains | 1 Teamcity | 2024-11-21 | 7.5 High |
In JetBrains TeamCity before 2020.2.3, insufficient checks of the redirect_uri were made during GitHub SSO token exchange. | ||||
CVE-2021-31912 | 1 Jetbrains | 1 Teamcity | 2024-11-21 | 8.8 High |
In JetBrains TeamCity before 2020.2.3, account takeover was potentially possible during a password reset. | ||||
CVE-2021-31911 | 1 Jetbrains | 1 Teamcity | 2024-11-21 | 6.1 Medium |
In JetBrains TeamCity before 2020.2.3, reflected XSS was possible on several pages. | ||||
CVE-2021-31910 | 1 Jetbrains | 1 Teamcity | 2024-11-21 | 7.5 High |
In JetBrains TeamCity before 2020.2.3, information disclosure via SSRF was possible. | ||||
CVE-2021-31909 | 1 Jetbrains | 1 Teamcity | 2024-11-21 | 9.8 Critical |
In JetBrains TeamCity before 2020.2.3, argument injection leading to remote code execution was possible. | ||||
CVE-2021-31908 | 1 Jetbrains | 1 Teamcity | 2024-11-21 | 5.4 Medium |
In JetBrains TeamCity before 2020.2.3, stored XSS was possible on several pages. | ||||
CVE-2021-31907 | 1 Jetbrains | 1 Teamcity | 2024-11-21 | 5.3 Medium |
In JetBrains TeamCity before 2020.2.2, permission checks for changing TeamCity plugins were implemented improperly. | ||||
CVE-2021-31906 | 1 Jetbrains | 1 Teamcity | 2024-11-21 | 2.7 Low |
In JetBrains TeamCity before 2020.2.2, audit logs were not sufficient when an administrator uploaded a file. | ||||
CVE-2021-31904 | 1 Jetbrains | 1 Teamcity | 2024-11-21 | 6.1 Medium |
In JetBrains TeamCity before 2020.2.2, XSS was potentially possible on the test history page. | ||||
CVE-2021-26310 | 1 Jetbrains | 1 Teamcity | 2024-11-21 | 7.5 High |
In the TeamCity IntelliJ plugin before 2020.2.2.85899, DoS was possible. | ||||
CVE-2021-26309 | 1 Jetbrains | 1 Teamcity | 2024-11-21 | 3.3 Low |
Information disclosure in the TeamCity plugin for IntelliJ before 2020.2.2.85899 was possible because a local temporary file had Insecure Permissions. | ||||
CVE-2021-25778 | 1 Jetbrains | 1 Teamcity | 2024-11-21 | 5.3 Medium |
In JetBrains TeamCity before 2020.2.1, permissions during user deletion were checked improperly. | ||||
CVE-2021-25777 | 1 Jetbrains | 1 Teamcity | 2024-11-21 | 5.3 Medium |
In JetBrains TeamCity before 2020.2.1, permissions during token removal were checked improperly. | ||||
CVE-2021-25776 | 1 Jetbrains | 1 Teamcity | 2024-11-21 | 7.5 High |
In JetBrains TeamCity before 2020.2, an ECR token could be exposed in a build's parameters. | ||||
CVE-2021-25775 | 1 Jetbrains | 1 Teamcity | 2024-11-21 | 3.8 Low |
In JetBrains TeamCity before 2020.2.1, the server admin could create and see access tokens for any other users. | ||||
CVE-2021-25774 | 1 Jetbrains | 1 Teamcity | 2024-11-21 | 4.3 Medium |
In JetBrains TeamCity before 2020.2.1, a user could get access to the GitHub access token of another user. |