CVEs (269)
CVE VENDORS PRODUCTS UPDATED PUBLISHED CVSS |
|---|
In the TeamCity IntelliJ plugin before 2020.2.2.85899, DoS was possible. |
Information disclosure in the TeamCity plugin for IntelliJ before 2020.2.2.85899 was possible because a local temporary file had Insecure Permissions. |
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, an ECR token could be exposed in a build's parameters. |
In JetBrains TeamCity before 2020.2.1, the server admin could create and see access tokens for any other users. |
In JetBrains TeamCity before 2020.2.1, a user could get access to the GitHub access token of another user. |
JetBrains TeamCity before 2020.2 was vulnerable to reflected XSS on several pages. |
In JetBrains TeamCity before 2020.2.2, TeamCity server DoS was possible via server integration. |
JetBrains TeamCity Plugin before 2020.2.85695 SSRF. Vulnerability that could potentially expose user credentials. |
JetBrains TeamCity before 2020.1.2 was vulnerable to URL injection. |
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 2020.1.5, the Guest user had access to audit records. |
JetBrains TeamCity before 2019.2.3 is vulnerable to reflected XSS in the administration UI. |
JetBrains TeamCity before 2019.2.3 is vulnerable to stored XSS in the administration UI. |
In JetBrains TeamCity before 2019.2.3, password parameters could be disclosed via build logs. |
In JetBrains TeamCity before 2020.1.1, project parameter values can be retrieved by a user without appropriate permissions. |
In JetBrains TeamCity before 2020.1, users are able to assign more permissions than they have. |
In JetBrains TeamCity before 2020.1, users with the Modify Group permission can elevate other users' privileges. |
In JetBrains TeamCity 2018.2 through 2019.2.1, a project administrator was able to see scrambled password parameters used in a project. The issue was resolved in 2019.2.2. |