Total
217 CVE
| CVE | Vendors | Products | Updated | CVSS v2 | CVSS v3 |
|---|---|---|---|---|---|
| CVE-2024-35302 | 1 Jetbrains | 1 Teamcity | 2024-12-16 | N/A | 5.4 MEDIUM |
| In JetBrains TeamCity before 2023.11 stored XSS during restore from backup was possible | |||||
| CVE-2024-36362 | 1 Jetbrains | 1 Teamcity | 2024-12-16 | N/A | 6.5 MEDIUM |
| In JetBrains TeamCity before 2022.04.7, 2022.10.6, 2023.05.6, 2023.11.5, 2024.03.2 path traversal allowing to read files from server was possible | |||||
| CVE-2024-36363 | 1 Jetbrains | 1 Teamcity | 2024-12-16 | N/A | 4.6 MEDIUM |
| In JetBrains TeamCity before 2022.04.7, 2022.10.6, 2023.05.6, 2023.11.5 several Stored XSS in code inspection reports were possible | |||||
| CVE-2024-36364 | 1 Jetbrains | 1 Teamcity | 2024-12-16 | N/A | 6.5 MEDIUM |
| In JetBrains TeamCity before 2022.04.7, 2022.10.6, 2023.05.6, 2023.11.5 improper access control in Pull Requests and Commit status publisher build features was possible | |||||
| CVE-2024-29880 | 1 Jetbrains | 1 Teamcity | 2024-12-16 | N/A | 4.2 MEDIUM |
| In JetBrains TeamCity before 2023.11 users with access to the agent machine might obtain permissions of the user running the agent process | |||||
| CVE-2024-36367 | 1 Jetbrains | 1 Teamcity | 2024-12-16 | N/A | 4.6 MEDIUM |
| In JetBrains TeamCity before 2022.04.7, 2022.10.6, 2023.05.6, 2023.11.5 stored XSS via third-party reports was possible | |||||
| CVE-2024-36368 | 1 Jetbrains | 1 Teamcity | 2024-12-16 | N/A | 4.6 MEDIUM |
| In JetBrains TeamCity before 2022.04.7, 2022.10.6, 2023.05.6, 2023.11.5 reflected XSS via OAuth provider configuration was possible | |||||
| CVE-2024-36369 | 1 Jetbrains | 1 Teamcity | 2024-12-16 | N/A | 4.6 MEDIUM |
| In JetBrains TeamCity before 2022.04.7, 2022.10.6, 2023.05.6, 2023.11.5 stored XSS via issue tracker integration was possible | |||||
| CVE-2024-28173 | 1 Jetbrains | 1 Teamcity | 2024-12-16 | N/A | 4.3 MEDIUM |
| In JetBrains TeamCity between 2023.11 and 2023.11.4 custom build parameters of the "password" type could be disclosed | |||||
| CVE-2024-28174 | 1 Jetbrains | 1 Teamcity | 2024-12-16 | N/A | 5.8 MEDIUM |
| In JetBrains TeamCity before 2023.11.4 presigned URL generation requests in S3 Artifact Storage plugin were authorized improperly | |||||
| CVE-2024-27199 | 1 Jetbrains | 1 Teamcity | 2024-12-16 | N/A | 7.3 HIGH |
| In JetBrains TeamCity before 2023.11.4 path traversal allowing to perform limited admin actions was possible | |||||
| CVE-2023-42793 | 1 Jetbrains | 1 Teamcity | 2024-12-16 | N/A | 9.8 CRITICAL |
| In JetBrains TeamCity before 2023.05.4 authentication bypass leading to RCE on TeamCity Server was possible | |||||
| CVE-2024-27198 | 1 Jetbrains | 1 Teamcity | 2024-11-29 | N/A | 9.8 CRITICAL |
| In JetBrains TeamCity before 2023.11.4 authentication bypass allowing to perform admin actions was possible | |||||
| CVE-2024-41829 | 1 Jetbrains | 1 Teamcity | 2024-11-21 | N/A | 3.5 LOW |
| In JetBrains TeamCity before 2024.07 an OAuth code for JetBrains Space could be stolen via Space Application connection | |||||
| CVE-2024-41828 | 1 Jetbrains | 1 Teamcity | 2024-11-21 | N/A | 2.6 LOW |
| In JetBrains TeamCity before 2024.07 comparison of authorization tokens took non-constant time | |||||
| CVE-2024-41827 | 1 Jetbrains | 1 Teamcity | 2024-11-21 | N/A | 7.4 HIGH |
| In JetBrains TeamCity before 2024.07 access tokens could continue working after deletion or expiration | |||||
| CVE-2024-41826 | 1 Jetbrains | 1 Teamcity | 2024-11-21 | N/A | 3.5 LOW |
| In JetBrains TeamCity before 2024.07 stored XSS was possible on Show Connection page | |||||
| CVE-2024-41825 | 1 Jetbrains | 1 Teamcity | 2024-11-21 | N/A | 4.6 MEDIUM |
| In JetBrains TeamCity before 2024.07 stored XSS was possible on the Code Inspection tab | |||||
| CVE-2024-41824 | 1 Jetbrains | 1 Teamcity | 2024-11-21 | N/A | 6.4 MEDIUM |
| In JetBrains TeamCity before 2024.07 parameters of the "password" type could leak into the build log in some specific cases | |||||
| CVE-2024-39879 | 1 Jetbrains | 1 Teamcity | 2024-11-21 | N/A | 5.0 MEDIUM |
| In JetBrains TeamCity before 2024.03.3 application token could be exposed in EC2 Cloud Profile settings | |||||