191 results · Feed
-
Medium 4.6
In JetBrains TeamCity before 2023.05 stored XSS in GitLab Connection page was possible
-
Medium 5.3
In JetBrains TeamCity before 2023.05 authentication checks were missing – 2FA was not checked for some sensitive accoun…
-
Medium 4.6CVE-2023-34225 EPSS 61%
In JetBrains TeamCity before 2023.05 stored XSS in the NuGet feed page was possible
-
Medium 4.6
In JetBrains TeamCity before 2023.05 reflected XSS in the Subscriptions page was possible
-
Medium 5.3
In JetBrains TeamCity before 2023.05 a specific endpoint was vulnerable to brute force attacks
-
Medium 4.3
In JetBrains TeamCity before 2023.05 parameters of the "password" type from build dependencies could be logged in some …
-
Medium 4.8
In JetBrains TeamCity before 2023.05 open redirect during oAuth configuration was possible
-
Medium 4.6
In JetBrains TeamCity before 2023.05 possible XSS in the Plugin Vendor URL was possible
-
Medium 4.6
In JetBrains TeamCity before 2023.05 stored XSS in the Show Connection page was possible
-
Medium 4.3
In JetBrains TeamCity before 2023.05 improper permission checks allowed users without appropriate permissions to edit B…
-
Medium 4.6CVE-2023-34220 EPSS 61%
In JetBrains TeamCity before 2023.05 stored XSS in the Commit Status Publisher window was possible
-
Critical 9.1
In JetBrains TeamCity before 2023.05 bypass of permission checks allowing to perform admin actions was possible
-
Medium 4.6CVE-2022-48428 EPSS 68%
In JetBrains TeamCity before 2022.10.3 stored XSS on the SSH keys page was possible
-
Medium 4.6
In JetBrains TeamCity before 2022.10.3 stored XSS on “Pending changes” and “Changes” tabs was possible
-
Medium 4.6
In JetBrains TeamCity before 2022.10.3 stored XSS in Perforce connection settings was possible
-
Medium 5.4
In JetBrains TeamCity before 2022.10.2 there was an XSS vulnerability in the group creation process.
-
Medium 5.2
In JetBrains TeamCity before 2022.10.2 jVMTI was enabled by default on agents.
-
Medium 5.4CVE-2022-48343 EPSS 59%
In JetBrains TeamCity before 2022.10.2 there was an XSS vulnerability in the user creation process.
-
Medium 6.6
In JetBrains TeamCity between 2022.10 and 2022.10.1 connecting to AWS using the "Default Credential Provider Chain" all…
-
Medium 4.1
In JetBrains TeamCity between 2022.10 and 2022.10.1 a custom STS endpoint allowed internal port scanning.
-
Low 2.7
In JetBrains TeamCity version between 2021.2 and 2022.10 access permissions for secure token health items were excessive
-
Medium 6.5
In JetBrains TeamCity version before 2022.10, Password parameters could be exposed in the build log if they contained s…
-
Medium 6.5
In JetBrains TeamCity version before 2022.10, Project Viewer could see scrambled secure values in the MetaRunner settin…
-
Low 2.2
In JetBrains TeamCity version before 2022.10, no audit items were added upon editing a user's settings
-
Medium 4.4
In JetBrains TeamCity before 2022.04.4 environmental variables of "password" type could be logged when using custom Per…
-
Low 3.2
In JetBrains TeamCity before 2022.04.3 the private SSH key could be written to the server log in some cases
-
Medium 5.4
In JetBrains TeamCity before 2022.04.2 build parameter injection was possible
-
Medium 4.1
In JetBrains TeamCity before 2022.04.2 the private SSH key could be written to the build log in some cases
-
Low 3.7
In JetBrains TeamCity before 2022.04 potential XSS via Referrer header was possible
-
Medium 4.4
In JetBrains TeamCity before 2022.04 leak of secrets in TeamCity agent logs was possible
-
Medium 4.6
In JetBrains TeamCity before 2022.04 reflected XSS on the Build Chain Status page was possible