Filtered by vendor Jetbrains
Subscriptions
Total
424 CVE
CVE | Vendors | Products | Updated | CVSS v3.1 |
---|---|---|---|---|
CVE-2024-31140 | 1 Jetbrains | 1 Teamcity | 2024-12-16 | 4.1 Medium |
In JetBrains TeamCity before 2024.03 server administrators could remove arbitrary files from the server by installing tools | ||||
CVE-2024-31139 | 1 Jetbrains | 1 Teamcity | 2024-12-16 | 5.9 Medium |
In JetBrains TeamCity before 2024.03 xXE was possible in the Maven build steps detector | ||||
CVE-2024-31136 | 1 Jetbrains | 1 Teamcity | 2024-12-16 | 7.4 High |
In JetBrains TeamCity before 2024.03 2FA could be bypassed by providing a special URL parameter | ||||
CVE-2024-31134 | 1 Jetbrains | 1 Teamcity | 2024-12-16 | 6.5 Medium |
In JetBrains TeamCity before 2024.03 authenticated users without administrative permissions could register other users when self-registration was disabled | ||||
CVE-2024-36366 | 1 Jetbrains | 1 Teamcity | 2024-12-16 | 5.4 Medium |
In JetBrains TeamCity before 2022.04.7, 2022.10.6, 2023.05.6, 2023.11.5 an XSS could be executed via certain report grouping and filtering operations | ||||
CVE-2024-36365 | 1 Jetbrains | 1 Teamcity | 2024-12-16 | 6.8 Medium |
In JetBrains TeamCity before 2022.04.7, 2022.10.6, 2023.05.6, 2023.11.5, 2024.03.2 a third-party agent could impersonate a cloud agent | ||||
CVE-2024-35301 | 1 Jetbrains | 1 Teamcity | 2024-12-16 | 5.5 Medium |
In JetBrains TeamCity before 2024.03.1 commit status publisher didn't check project scope of the GitHub App token | ||||
CVE-2024-35300 | 1 Jetbrains | 1 Teamcity | 2024-12-16 | 3.5 Low |
In JetBrains TeamCity between 2024.03 and 2024.03.1 several stored XSS in the available updates page were possible | ||||
CVE-2024-36370 | 1 Jetbrains | 1 Teamcity | 2024-12-16 | 4.6 Medium |
In JetBrains TeamCity before 2022.04.7, 2022.10.6, 2023.05.6, 2023.11.5 stored XSS via OAuth connection settings was possible | ||||
CVE-2024-35302 | 1 Jetbrains | 1 Teamcity | 2024-12-16 | 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 | 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 | 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 | 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 | 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 | 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 | 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 | 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 | 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 | 5.8 Medium |
In JetBrains TeamCity before 2023.11.4 presigned URL generation requests in S3 Artifact Storage plugin were authorized improperly | ||||
CVE-2024-28228 | 1 Jetbrains | 1 Youtrack | 2024-12-16 | 5.3 Medium |
In JetBrains YouTrack before 2024.1.25893 creation comments on behalf of an arbitrary user in HelpDesk was possible |