132 results · Clear filters · Feed
-
Medium 4.3
In JetBrains TeamCity before 2024.12.1 improper access control allowed to see Projects’ names in the agent pool
-
Medium 6.5
In JetBrains TeamCity before 2024.12.1 decryption of connection secrets without proper permissions was possible via Tes…
-
Medium 4.6
In JetBrains TeamCity before 2024.12.1 reflected XSS was possible on the Vault Connection page
-
Medium 5.9
In JetBrains TeamCity before 2024.12 insecure XMLParser configuration could lead to potential XXE attack
-
Medium 4.6
In JetBrains TeamCity before 2024.12 missing Content-Type header in RemoteBuildLogController response could lead to XSS
-
Medium 5.5
In JetBrains TeamCity before 2024.12 password field value were accessible to users with view settings permission
-
Medium 5.5
In JetBrains TeamCity before 2024.12 backup file exposed user credentials and session cookies
-
Medium 6.3
In JetBrains TeamCity before 2024.12 access tokens were not revoked after removing user roles
-
Medium 4.6
In JetBrains TeamCity before 2024.12 stored XSS was possible via image name on the agent details page
-
Medium 5.3
In JetBrains TeamCity before 2024.12 improper access control allowed unauthorized users to modify build logs
-
Medium 4.3
In JetBrains TeamCity before 2024.12 build credentials allowed unauthorized viewing of projects
-
Medium 4.3CVE-2024-56348 Public exploit
In JetBrains TeamCity before 2024.12 improper access control allowed viewing details of unauthorized agents
-
Medium 4.9CVE-2024-47949 EPSS 32%
In JetBrains TeamCity before 2024.07.3 path traversal allowed backup file write to arbitrary location
-
Medium 4.9
In JetBrains TeamCity before 2024.07.3 path traversal leading to information disclosure was possible via server backups
-
Medium 4.3
In JetBrains TeamCity before 2024.07.3 password could be exposed via Sonar runner REST API
-
Medium 4.6
In JetBrains TeamCity before 2024.07.1 reflected XSS was possible in the AWS Core plugin
-
Medium 4.6
In JetBrains TeamCity before 2024.07.1 multiple stored XSS was possible on Clouds page
-
Medium 4.6
In JetBrains TeamCity before 2024.07 stored XSS was possible on the Code Inspection tab
-
Medium 6.4
In JetBrains TeamCity before 2024.07 parameters of the "password" type could leak into the build log in some specific c…
-
Medium 5.0
In JetBrains TeamCity before 2024.03.3 application token could be exposed in EC2 Cloud Profile settings
-
Medium 4.1
In JetBrains TeamCity before 2024.03.3 private key could be exposed via testing GitHub App Connection
-
Medium 5.9
In JetBrains TeamCity before 2024.03.2 server was susceptible to DoS attacks with incorrect auth tokens
-
Medium 6.5
In JetBrains TeamCity before 2024.03.2 certain TeamCity API endpoints did not check user permissions
-
Medium 6.5
In JetBrains TeamCity before 2024.03.2 users could perform actions that should not be available to them based on their …
-
Medium 5.3
In JetBrains TeamCity before 2024.03.2 technical information regarding TeamCity server could be exposed
-
Medium 4.6
In JetBrains TeamCity before 2024.03.2 stored XSS via build step settings was possible
-
Medium 4.6
In JetBrains TeamCity before 2024.03.2 several stored XSS in untrusted builds settings were possible
-
Medium 4.6
In JetBrains TeamCity before 2023.05.6, 2023.11.5 stored XSS in Commit status publisher was possible
-
Medium 4.6
In JetBrains TeamCity before 2023.05.6 reflected XSS on the subscriptions page was possible
-
Medium 4.6
In JetBrains TeamCity before 2022.04.7, 2022.10.6, 2023.05.6, 2023.11.5 stored XSS via OAuth connection settings was po…
-
Medium 4.6
In JetBrains TeamCity before 2022.04.7, 2022.10.6, 2023.05.6, 2023.11.5 reflected XSS via OAuth provider configuration …
-
Medium 4.6
In JetBrains TeamCity before 2022.04.7, 2022.10.6, 2023.05.6, 2023.11.5 stored XSS via issue tracker integration was po…
-
Medium 4.6
In JetBrains TeamCity before 2022.04.7, 2022.10.6, 2023.05.6, 2023.11.5 stored XSS via third-party reports was possible
-
Medium 6.8
In JetBrains TeamCity before 2022.04.7, 2022.10.6, 2023.05.6, 2023.11.5, 2024.03.2 a third-party agent could impersonat…
-
Medium 5.4
In JetBrains TeamCity before 2022.04.7, 2022.10.6, 2023.05.6, 2023.11.5 an XSS could be executed via certain report gro…
-
Medium 4.6
In JetBrains TeamCity before 2022.04.7, 2022.10.6, 2023.05.6, 2023.11.5 several Stored XSS in code inspection reports w…
-
Medium 6.5
In JetBrains TeamCity before 2022.04.7, 2022.10.6, 2023.05.6, 2023.11.5 improper access control in Pull Requests and Co…
-
Medium 6.5
In JetBrains TeamCity before 2022.04.7, 2022.10.6, 2023.05.6, 2023.11.5, 2024.03.2 path traversal allowing to read file…
-
Medium 5.4
In JetBrains TeamCity before 2023.11 stored XSS during restore from backup was possible
-
Medium 5.5
In JetBrains TeamCity before 2024.03.1 commit status publisher didn't check project scope of the GitHub App token