Teamcity
Sign in to watchby Jetbrains
Source repositories
CVEs (166)
| CVE | Sev | Risk | CVSS | EPSS | KEV | Published | Description |
|---|---|---|---|---|---|---|---|
| CVE-2023-34222 | 0.00 | — | 0.00 | May 31, 2023 | In JetBrains TeamCity before 2023.05 possible XSS in the Plugin Vendor URL was possible | ||
| CVE-2023-34221 | 0.00 | — | 0.00 | May 31, 2023 | In JetBrains TeamCity before 2023.05 stored XSS in the Show Connection page was possible | ||
| CVE-2023-34220 | 0.00 | — | 0.05 | May 31, 2023 | In JetBrains TeamCity before 2023.05 stored XSS in the Commit Status Publisher window was possible | ||
| CVE-2023-34219 | 0.00 | — | 0.00 | May 31, 2023 | In JetBrains TeamCity before 2023.05 improper permission checks allowed users without appropriate permissions to edit Build Configuration settings via REST API | ||
| CVE-2023-34218 | 0.00 | — | 0.00 | May 31, 2023 | In JetBrains TeamCity before 2023.05 bypass of permission checks allowing to perform admin actions was possible | ||
| CVE-2022-48428 | 0.00 | — | 0.01 | Mar 27, 2023 | In JetBrains TeamCity before 2022.10.3 stored XSS on the SSH keys page was possible | ||
| CVE-2022-48427 | 0.00 | — | 0.00 | Mar 27, 2023 | In JetBrains TeamCity before 2022.10.3 stored XSS on “Pending changes” and “Changes” tabs was possible | ||
| CVE-2022-48426 | 0.00 | — | 0.00 | Mar 27, 2023 | In JetBrains TeamCity before 2022.10.3 stored XSS in Perforce connection settings was possible | ||
| CVE-2022-48344 | 0.00 | — | 0.00 | Feb 23, 2023 | In JetBrains TeamCity before 2022.10.2 there was an XSS vulnerability in the group creation process. | ||
| CVE-2022-48343 | 0.00 | — | 0.01 | Feb 23, 2023 | In JetBrains TeamCity before 2022.10.2 there was an XSS vulnerability in the user creation process. | ||
| CVE-2022-48342 | 0.00 | — | 0.00 | Feb 23, 2023 | In JetBrains TeamCity before 2022.10.2 jVMTI was enabled by default on agents. | ||
| CVE-2022-46831 | 0.00 | — | 0.00 | Dec 8, 2022 | 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-46830 | 0.00 | — | 0.00 | Dec 8, 2022 | In JetBrains TeamCity between 2022.10 and 2022.10.1 a custom STS endpoint allowed internal port scanning. | ||
| CVE-2022-44622 | 0.00 | — | 0.00 | Nov 3, 2022 | In JetBrains TeamCity version between 2021.2 and 2022.10 access permissions for secure token health items were excessive | ||
| CVE-2022-44646 | 0.00 | — | 0.00 | Nov 3, 2022 | In JetBrains TeamCity version before 2022.10, no audit items were added upon editing a user's settings | ||
| CVE-2022-44624 | 0.00 | — | 0.00 | Nov 3, 2022 | In JetBrains TeamCity version before 2022.10, Password parameters could be exposed in the build log if they contained special characters | ||
| CVE-2022-44623 | 0.00 | — | 0.00 | Nov 3, 2022 | In JetBrains TeamCity version before 2022.10, Project Viewer could see scrambled secure values in the MetaRunner settings | ||
| CVE-2022-40979 | 0.00 | — | 0.00 | Sep 23, 2022 | In JetBrains TeamCity before 2022.04.4 environmental variables of "password" type could be logged when using custom Perforce executable | ||
| CVE-2022-38133 | 0.00 | — | 0.00 | Aug 10, 2022 | In JetBrains TeamCity before 2022.04.3 the private SSH key could be written to the server log in some cases | ||
| CVE-2022-36322 | 0.00 | — | 0.00 | Jul 20, 2022 | In JetBrains TeamCity before 2022.04.2 build parameter injection was possible |
Page 8 of 9