| CVE |
Vendors |
Products |
Updated |
CVSS v3.1 |
| In JetBrains TeamCity before 2021.1, passwords in cleartext sometimes could be stored in VCS. |
| In JetBrains TeamCity before 2020.2.4, insufficient checks during file uploading were made. |
| In JetBrains TeamCity before 2021.1, an insecure key generation mechanism for encrypted properties was used. |
| In JetBrains TeamCity before 2021.1.1, insufficient authentication checks for agent requests were made. |
| In JetBrains TeamCity before 2020.2.4, there was an insecure deserialization. |
| In JetBrains TeamCity before 2020.2.3, XSS was possible. |
| In JetBrains TeamCity before 2020.2.4, OS command injection leading to remote code execution was possible. |
| In JetBrains TeamCity before 2020.2.4 on Windows, arbitrary code execution on TeamCity Server was possible. |
| In JetBrains TeamCity before 2020.2.3, insufficient checks of the redirect_uri were made during GitHub SSO token exchange. |
| In JetBrains TeamCity before 2020.2.3, account takeover was potentially possible during a password reset. |
| In JetBrains TeamCity before 2020.2.3, reflected XSS was possible on several pages. |
| In JetBrains TeamCity before 2020.2.3, information disclosure via SSRF was possible. |
| In JetBrains TeamCity before 2020.2.3, argument injection leading to remote code execution was possible. |
| In JetBrains TeamCity before 2020.2.3, stored XSS was possible on several pages. |
| In JetBrains TeamCity before 2020.2.2, permission checks for changing TeamCity plugins were implemented improperly. |
| In JetBrains TeamCity before 2020.2.2, audit logs were not sufficient when an administrator uploaded a file. |
| In JetBrains TeamCity before 2020.2.2, XSS was potentially possible on the test history page. |
| In the TeamCity IntelliJ plugin before 2020.2.2.85899, DoS was possible. |
| Information disclosure in the TeamCity plugin for IntelliJ before 2020.2.2.85899 was possible because a local temporary file had Insecure Permissions. |
| In JetBrains TeamCity before 2020.2.1, permissions during user deletion were checked improperly. |