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

In JetBrains TeamCity before 2024.03 xSS was possible via Agent Distribution settings

In JetBrains TeamCity before 2023.11.2 stored XSS via agent distribution was possible

In JetBrains TeamCity before 2023.05.4 stored XSS was possible during nodes configuration

In JetBrains TeamCity before 2023.05.3 stored XSS was possible during Cloud Profiles configuration

In JetBrains TeamCity before 2023.05.1 stored XSS while viewing the build log was possible

In JetBrains TeamCity before 2023.05.1 stored XSS while running custom builds was possible

In JetBrains TeamCity before 2023.05.1 stored XSS when using a custom theme was possible

In JetBrains TeamCity before 2023.05 stored XSS in GitLab Connection page was possible

In JetBrains TeamCity before 2023.05 stored XSS in the NuGet feed page was possible

In JetBrains TeamCity before 2023.05 stored XSS in the Show Connection page was possible

In JetBrains TeamCity before 2023.05 stored XSS in the Commit Status Publisher window was possible

In JetBrains TeamCity before 2022.10.3 stored XSS on the SSH keys page was possible

In JetBrains TeamCity before 2022.10.3 stored XSS on “Pending changes” and “Changes” tabs was possible

In JetBrains TeamCity before 2022.10.3 stored XSS in Perforce connection settings was possible

JetBrains TeamCity before 2021.2.1 was vulnerable to stored XSS

In JetBrains TeamCity before 2021.1.2, stored XSS is possible

In JetBrains TeamCity before 2020.2.2, stored XSS on a tests page was possible

In JetBrains TeamCity before 2020.2.3, stored XSS was possible on several pages

JetBrains TeamCity before 2019.2 was vulnerable to a stored XSS attack by a user with the developer role

In JetBrains TeamCity before 2025.11 improper access control could expose GitHub App token's metadata

In JetBrains TeamCity before 2024.12 improper access control allowed unauthorized users to modify build logs

In JetBrains TeamCity before 2024.03.3 application token could be exposed in EC2 Cloud Profile settings

In JetBrains TeamCity before 2024.03.3 private key could be exposed via testing GitHub App Connection

In JetBrains TeamCity before 2024.03.2 technical information regarding TeamCity server could be exposed

In JetBrains TeamCity before 2023.11.3 path traversal allowed reading data within JAR archives

In JetBrains TeamCity before 2023.11.2 limited directory traversal was possible in the Kotlin DSL documentation

In JetBrains TeamCity before 2023.11.2 access control at the S3 Artifact Storage plugin endpoint was missed

In JetBrains TeamCity before 2023.05 parameters of the "password" type from build dependencies could be logged in some cases

In JetBrains TeamCity between 2022.10 and 2022.10.1 a custom STS endpoint allowed internal port scanning

In JetBrains TeamCity version before 2022.10, no audit items were added upon editing a user's settings

In JetBrains TeamCity version between 2021.2 and 2022.10 access permissions for secure token health items were excessive

In JetBrains TeamCity before 2022.04.4 environmental variables of "password" type could be logged when using custom Perforce executable

In JetBrains TeamCity before 2022.04.3 the private SSH key could be written to the server log in some cases

In JetBrains TeamCity before 2021.2.1, an unauthenticated attacker can cancel running builds via an XML-RPC request to the TeamCity server

In JetBrains TeamCity before 2021.2.1, the Agent Push feature allowed selection of any private key on the server

In JetBrains TeamCity before 2021.2, a logout action didn't remove a Remember Me cookie

In JetBrains TeamCity before 2021.1.3, a newly created project could take settings from an already deleted project

In JetBrains TeamCity before 2021.1.2, permission checks in the Create Patch functionality are insufficient

In JetBrains TeamCity before 2021.1.2, some HTTP security headers were missing

In JetBrains TeamCity before 2021.1.2, user enumeration was possible

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 2020.2.2, permission checks for changing TeamCity plugins were implemented improperly

In JetBrains TeamCity before 2020.2.1, permissions during user deletion were checked improperly

In JetBrains TeamCity before 2020.2.1, permissions during token removal were checked improperly

In JetBrains TeamCity before 2020.2.2, TeamCity server DoS was possible via server integration

In JetBrains TeamCity before 2020.1.5, secure dependency parameters could be not masked in depending builds when there are no internal artifacts

In JetBrains TeamCity before 2019.2.3, password parameters could be disclosed via build logs

In JetBrains TeamCity before 2019.1.2, a non-destructive operation could be performed by a user without the corresponding permissions