Vulnerabilities > Jetbrains > Teamcity > 2018.2.4
DATE | CVE | VULNERABILITY TITLE | RISK |
---|---|---|---|
2020-11-16 | CVE-2020-27628 | Unspecified vulnerability in Jetbrains Teamcity In JetBrains TeamCity before 2020.1.5, the Guest user had access to audit records. | 4.0 |
2020-08-08 | CVE-2020-15831 | Cross-site Scripting vulnerability in Jetbrains Teamcity JetBrains TeamCity before 2019.2.3 is vulnerable to reflected XSS in the administration UI. | 4.3 |
2020-08-08 | CVE-2020-15830 | Cross-site Scripting vulnerability in Jetbrains Teamcity JetBrains TeamCity before 2019.2.3 is vulnerable to stored XSS in the administration UI. | 4.3 |
2020-08-08 | CVE-2020-15829 | Information Exposure vulnerability in Jetbrains Teamcity In JetBrains TeamCity before 2019.2.3, password parameters could be disclosed via build logs. | 5.0 |
2020-08-08 | CVE-2020-15828 | Information Exposure vulnerability in Jetbrains Teamcity In JetBrains TeamCity before 2020.1.1, project parameter values can be retrieved by a user without appropriate permissions. | 4.0 |
2020-08-08 | CVE-2020-15826 | Incorrect Authorization vulnerability in Jetbrains Teamcity In JetBrains TeamCity before 2020.1, users are able to assign more permissions than they have. | 4.0 |
2020-08-08 | CVE-2020-15825 | Improper Privilege Management vulnerability in Jetbrains Teamcity In JetBrains TeamCity before 2020.1, users with the Modify Group permission can elevate other users' privileges. | 6.5 |
2020-04-22 | CVE-2020-11938 | Information Exposure vulnerability in Jetbrains Teamcity In JetBrains TeamCity 2018.2 through 2019.2.1, a project administrator was able to see scrambled password parameters used in a project. | 4.0 |
2020-04-22 | CVE-2020-11689 | Incorrect Default Permissions vulnerability in Jetbrains Teamcity In JetBrains TeamCity before 2019.2.1, a user without appropriate permissions was able to import settings from the settings.kts file. | 4.0 |
2020-04-22 | CVE-2020-11688 | Insufficient Session Expiration vulnerability in Jetbrains Teamcity In JetBrains TeamCity before 2019.2.1, the application state is kept alive after a user ends his session. | 5.0 |