Jetbrains
jetbrains
564 CVEs • 38 products
Products (38)
Click to collapseToggle
Products (38)
Click to collapse
CVEs (564)
CVE VENDORS PRODUCTS UPDATED PUBLISHED CVSS |
|---|
In JetBrains TeamCity before 2024.07 an OAuth code for JetBrains Space could be stolen via Space Application connection |
In JetBrains TeamCity before 2024.07 comparison of authorization tokens took non-constant time |
In JetBrains TeamCity before 2024.07 access tokens could continue working after deletion or expiration |
In JetBrains TeamCity before 2024.07 stored XSS was possible on Show Connection page |
In JetBrains TeamCity before 2024.07 stored XSS was possible on the Code Inspection tab |
In JetBrains TeamCity before 2024.07 parameters of the "password" type could leak into the build log in some specific cases |
In JetBrains TeamCity before 2024.03.3 application token could be exposed in EC2 Cloud Profile settings |
In JetBrains TeamCity before 2024.03.3 private key could be exposed via testing GitHub App Connection |
In JetBrains Hub before 2024.2.34646 stored XSS via project description was possible |
In JetBrains YouTrack before 2024.2.34646 user without appropriate permissions could enable the auto-attach option for workflows |
In JetBrains YouTrack before 2024.2.34646 user access token was sent to the third-party site |
In JetBrains YouTrack before 2024.2.34646 the Guest User Account was enabled for attaching files to articles |
1Jetbrains 13Aqua ClionDatagrip+10 moreNov 21, 2024 Jun 10, 2024 N/A· v4 7.5 HIGH· v3 N/A· v2 GitHub access token could be exposed to third-party sites in JetBrains IDEs after version 2023.1 and less than: IntelliJ IDEA 2023.1.7, 2023.2.7, 2023.3.7, 2024.1.3, 2024.2 EAP3; Aqua 2024.1.2; CLion 2023.1.7, 2023.2.4,...Show more |
In JetBrains TeamCity before 2022.04.7, 2022.10.6, 2023.05.6, 2023.11.5 authentication bypass was possible in specific edge cases |
In JetBrains TeamCity before 2024.03.2 server was susceptible to DoS attacks with incorrect auth tokens |
In JetBrains TeamCity before 2024.03.2 certain TeamCity API endpoints did not check user permissions |
In JetBrains TeamCity before 2024.03.2 users could perform actions that should not be available to them based on their permissions |
In JetBrains TeamCity before 2024.03.2 technical information regarding TeamCity server could be exposed |
In JetBrains TeamCity before 2024.03.2 stored XSS via build step settings was possible |
In JetBrains TeamCity before 2024.03.2 several stored XSS in untrusted builds settings were possible |