Vulnerabilities > Jetbrains > Teamcity
DATE | CVE | VULNERABILITY TITLE | RISK |
---|---|---|---|
2023-08-25 | CVE-2023-41248 | Cross-site Scripting vulnerability in Jetbrains Teamcity In JetBrains TeamCity before 2023.05.3 stored XSS was possible during Cloud Profiles configuration | 5.4 |
2023-08-25 | CVE-2023-41249 | Cross-site Scripting vulnerability in Jetbrains Teamcity In JetBrains TeamCity before 2023.05.3 reflected XSS was possible during copying Build Step | 6.1 |
2023-08-25 | CVE-2023-41250 | Cross-site Scripting vulnerability in Jetbrains Teamcity In JetBrains TeamCity before 2023.05.3 reflected XSS was possible during user registration | 6.1 |
2023-07-25 | CVE-2023-39173 | Incorrect Privilege Assignment vulnerability in Jetbrains Teamcity In JetBrains TeamCity before 2023.05.2 a token with limited permissions could be used to gain full account access | 8.8 |
2023-07-25 | CVE-2023-39174 | Unspecified vulnerability in Jetbrains Teamcity In JetBrains TeamCity before 2023.05.2 a ReDoS attack was possible via integration with issue trackers | 7.5 |
2023-07-25 | CVE-2023-39175 | Cross-site Scripting vulnerability in Jetbrains Teamcity In JetBrains TeamCity before 2023.05.2 reflected XSS via GitHub integration was possible | 6.1 |
2023-07-12 | CVE-2023-38061 | Cross-site Scripting vulnerability in Jetbrains Teamcity In JetBrains TeamCity before 2023.05.1 stored XSS when using a custom theme was possible | 5.4 |
2023-07-12 | CVE-2023-38062 | Unspecified vulnerability in Jetbrains Teamcity In JetBrains TeamCity before 2023.05.1 parameters of the "password" type could be shown in the UI in certain composite build configurations | 6.5 |
2023-07-12 | CVE-2023-38063 | Cross-site Scripting vulnerability in Jetbrains Teamcity In JetBrains TeamCity before 2023.05.1 stored XSS while running custom builds was possible | 5.4 |
2023-07-12 | CVE-2023-38064 | Information Exposure Through Log Files vulnerability in Jetbrains Teamcity In JetBrains TeamCity before 2023.05.1 build chain parameters of the "password" type could be written to the agent log | 6.5 |