Skip to content
OpenAdvisories

Product · JetBrains

TeamCity

191 known vulnerabilities.

191 results · Feed

  • 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.3
    CVE-2024-56348 Public exploit

    In JetBrains TeamCity before 2024.12 improper access control allowed viewing details of unauthorized agents

  • Low 3.5

    In JetBrains TeamCity before 2024.07.3 stored XSS was possible via server global settings

  • Low 3.5

    In JetBrains TeamCity before 2024.07.3 stored XSS was possible in Backup configuration settings

  • Medium 4.9
    CVE-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

  • Low 3.5

    In JetBrains TeamCity before 2024.07.1 reflected XSS was possible on the agentPushPreset page

  • Low 3.7

    In JetBrains TeamCity before 2024.07.1 self XSS was possible in the HashiCorp Vault plugin

  • Medium 4.6

    In JetBrains TeamCity before 2024.07.1 multiple stored XSS was possible on Clouds page

  • High 7.5

    In JetBrains TeamCity before 2024.07.1 possible privilege escalation due to incorrect directory permissions

  • Low 3.5

    In JetBrains TeamCity before 2024.07 an OAuth code for JetBrains Space could be stolen via Space Application connection

  • High 7.4

    In JetBrains TeamCity before 2024.07 access tokens could continue working after deletion or expiration

  • Low 2.6

    In JetBrains TeamCity before 2024.07 comparison of authorization tokens took non-constant time

  • Medium 4.6

    In JetBrains TeamCity before 2024.07 stored XSS was possible on the Code Inspection tab

  • Low 3.5

    In JetBrains TeamCity before 2024.07 stored XSS was possible on Show Connection page

  • 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

  • High 8.1

    In JetBrains TeamCity before 2022.04.7, 2022.10.6, 2023.05.6, 2023.11.5 authentication bypass was possible in specific …

  • 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…