Vulnerabilities > Jetbrains
| DATE | CVE | VULNERABILITY TITLE | RISK |
|---|---|---|---|
| 2022-07-28 | CVE-2022-37010 | Improper Input Validation vulnerability in Jetbrains Intellij Idea In JetBrains IntelliJ IDEA before 2022.2 email address validation in the "Git User Name Is Not Defined" dialog was missed | 3.3 |
| 2022-07-20 | CVE-2022-36321 | Information Exposure Through Log Files vulnerability in Jetbrains Teamcity In JetBrains TeamCity before 2022.04.2 the private SSH key could be written to the build log in some cases | 6.5 |
| 2022-07-20 | CVE-2022-36322 | Argument Injection or Modification vulnerability in Jetbrains Teamcity In JetBrains TeamCity before 2022.04.2 build parameter injection was possible | 8.8 |
| 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.3 |
| 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 | 6.1 |
| 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.9 |
| 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 | 6.1 |
| 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. | 4.8 |
| 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.3 |