Filtered by vendor Jetbrains
Subscriptions
Filtered by product Teamcity
Subscriptions
Total
150 CVE
CVE | Vendors | Products | Updated | CVSS v3.1 |
---|---|---|---|---|
CVE-2022-48427 | 1 Jetbrains | 1 Teamcity | 2023-03-31 | 5.4 Medium |
In JetBrains TeamCity before 2022.10.3 stored XSS on “Pending changes” and “Changes” tabs was possible | ||||
CVE-2022-48428 | 1 Jetbrains | 1 Teamcity | 2023-03-31 | 5.4 Medium |
In JetBrains TeamCity before 2022.10.3 stored XSS on the SSH keys page was possible | ||||
CVE-2022-48426 | 1 Jetbrains | 1 Teamcity | 2023-03-30 | 5.4 Medium |
In JetBrains TeamCity before 2022.10.3 stored XSS in Perforce connection settings was possible | ||||
CVE-2022-48342 | 1 Jetbrains | 1 Teamcity | 2023-03-03 | 9.8 Critical |
In JetBrains TeamCity before 2022.10.2 jVMTI was enabled by default on agents. | ||||
CVE-2022-48343 | 1 Jetbrains | 1 Teamcity | 2023-03-03 | 6.1 Medium |
In JetBrains TeamCity before 2022.10.2 there was an XSS vulnerability in the user creation process. | ||||
CVE-2022-48344 | 1 Jetbrains | 1 Teamcity | 2023-03-02 | 6.1 Medium |
In JetBrains TeamCity before 2022.10.2 there was an XSS vulnerability in the group creation process. | ||||
CVE-2022-46830 | 1 Jetbrains | 1 Teamcity | 2022-12-12 | 5.3 Medium |
In JetBrains TeamCity between 2022.10 and 2022.10.1 a custom STS endpoint allowed internal port scanning. | ||||
CVE-2022-46831 | 1 Jetbrains | 1 Teamcity | 2022-12-12 | 4.9 Medium |
In JetBrains TeamCity between 2022.10 and 2022.10.1 connecting to AWS using the "Default Credential Provider Chain" allowed TeamCity project administrators to access AWS resources normally limited to TeamCity system administrators. | ||||
CVE-2022-44622 | 1 Jetbrains | 1 Teamcity | 2022-11-04 | 5.3 Medium |
In JetBrains TeamCity version between 2021.2 and 2022.10 access permissions for secure token health items were excessive | ||||
CVE-2022-44623 | 1 Jetbrains | 1 Teamcity | 2022-11-03 | 7.5 High |
In JetBrains TeamCity version before 2022.10, Project Viewer could see scrambled secure values in the MetaRunner settings | ||||
CVE-2022-44624 | 1 Jetbrains | 1 Teamcity | 2022-11-03 | 7.5 High |
In JetBrains TeamCity version before 2022.10, Password parameters could be exposed in the build log if they contained special characters | ||||
CVE-2022-44646 | 1 Jetbrains | 1 Teamcity | 2022-11-03 | 5.3 Medium |
In JetBrains TeamCity version before 2022.10, no audit items were added upon editing a user's settings | ||||
CVE-2014-10002 | 1 Jetbrains | 1 Teamcity | 2022-10-03 | N/A |
Unspecified vulnerability in JetBrains TeamCity before 8.1 allows remote attackers to obtain sensitive information via unknown vectors. | ||||
CVE-2022-40979 | 1 Jetbrains | 1 Teamcity | 2022-09-26 | 5.3 Medium |
In JetBrains TeamCity before 2022.04.4 environmental variables of "password" type could be logged when using custom Perforce executable | ||||
CVE-2022-38133 | 1 Jetbrains | 1 Teamcity | 2022-08-12 | 5.3 Medium |
In JetBrains TeamCity before 2022.04.3 the private SSH key could be written to the server log in some cases | ||||
CVE-2022-36321 | 1 Jetbrains | 1 Teamcity | 2022-07-27 | 6.5 Medium |
In JetBrains TeamCity before 2022.04.2 the private SSH key could be written to the build log in some cases | ||||
CVE-2022-36322 | 1 Jetbrains | 1 Teamcity | 2022-07-27 | 8.8 High |
In JetBrains TeamCity before 2022.04.2 build parameter injection was possible | ||||
CVE-2021-25778 | 1 Jetbrains | 1 Teamcity | 2022-07-12 | 5.3 Medium |
In JetBrains TeamCity before 2020.2.1, permissions during user deletion were checked improperly. | ||||
CVE-2021-25775 | 1 Jetbrains | 1 Teamcity | 2022-07-12 | 3.8 Low |
In JetBrains TeamCity before 2020.2.1, the server admin could create and see access tokens for any other users. | ||||
CVE-2021-37546 | 1 Jetbrains | 1 Teamcity | 2022-07-12 | 5.3 Medium |
In JetBrains TeamCity before 2021.1, an insecure key generation mechanism for encrypted properties was used. |