Vulnerabilities > Jetbrains
| DATE | CVE | VULNERABILITY TITLE | RISK |
|---|---|---|---|
| 2022-11-03 | CVE-2022-44623 | Unspecified vulnerability in Jetbrains Teamcity In JetBrains TeamCity version before 2022.10, Project Viewer could see scrambled secure values in the MetaRunner settings | 7.5 |
| 2022-11-03 | CVE-2022-44624 | Information Exposure Through Log Files vulnerability in Jetbrains Teamcity In JetBrains TeamCity version before 2022.10, Password parameters could be exposed in the build log if they contained special characters | 7.5 |
| 2022-11-03 | CVE-2022-44646 | Unspecified vulnerability in Jetbrains Teamcity In JetBrains TeamCity version before 2022.10, no audit items were added upon editing a user's settings | 5.3 |
| 2022-07-01 | CVE-2022-34894 | Unspecified vulnerability in Jetbrains HUB In JetBrains Hub before 2022.2.14799, insufficient access control allowed the hijacking of untrusted services | 5.0 |
| 2022-05-12 | CVE-2022-29927 | Cross-site Scripting vulnerability in Jetbrains Teamcity In JetBrains TeamCity before 2022.04 reflected XSS on the Build Chain Status page was possible | 4.3 |
| 2022-05-12 | CVE-2022-29928 | Information Exposure Through Log Files vulnerability in Jetbrains Teamcity In JetBrains TeamCity before 2022.04 leak of secrets in TeamCity agent logs was possible | 4.0 |
| 2022-05-12 | CVE-2022-29929 | Cross-site Scripting vulnerability in Jetbrains Teamcity In JetBrains TeamCity before 2022.04 potential XSS via Referrer header was possible | 4.3 |
| 2022-05-12 | CVE-2022-29930 | Use of Insufficiently Random Values vulnerability in Jetbrains Ktor 2.0.0 SHA1 implementation in JetBrains Ktor Native 2.0.0 was returning the same value. | 4.9 |
| 2022-04-28 | CVE-2022-29811 | Cross-site Scripting vulnerability in Jetbrains HUB In JetBrains Hub before 2022.1.14638 stored XSS via project icon was possible. | 3.5 |
| 2022-04-28 | CVE-2022-29812 | Unspecified vulnerability in Jetbrains Intellij Idea In JetBrains IntelliJ IDEA before 2022.1 notification mechanisms about using Unicode directionality formatting characters were insufficient | 2.1 |