Vulnerabilities > Jetbrains
| DATE | CVE | VULNERABILITY TITLE | RISK |
|---|---|---|---|
| 2020-08-08 | CVE-2020-15819 | Server-Side Request Forgery (SSRF) vulnerability in Jetbrains Youtrack JetBrains YouTrack before 2020.2.10643 was vulnerable to SSRF that allowed scanning internal ports. | 5.3 |
| 2020-08-08 | CVE-2020-15818 | Unspecified vulnerability in Jetbrains Youtrack In JetBrains YouTrack before 2020.2.8527, the subtasks workflow could disclose issue existence. | 5.3 |
| 2020-08-08 | CVE-2020-15817 | Unspecified vulnerability in Jetbrains Youtrack In JetBrains YouTrack before 2020.1.1331, an external user could execute commands against arbitrary issues. | 8.8 |
| 2020-08-08 | CVE-2019-19704 | Unspecified vulnerability in Jetbrains Upsource In JetBrains Upsource before 2020.1, information disclosure is possible because of an incorrect user matching algorithm. | 7.5 |
| 2020-04-22 | CVE-2020-11938 | Unspecified vulnerability in Jetbrains Teamcity In JetBrains TeamCity 2018.2 through 2019.2.1, a project administrator was able to see scrambled password parameters used in a project. | 4.9 |
| 2020-04-22 | CVE-2020-11796 | Improper Authentication vulnerability in Jetbrains Space In JetBrains Space through 2020-04-22, the password authentication implementation was insecure. | 9.8 |
| 2020-04-22 | CVE-2020-11795 | Insufficient Session Expiration vulnerability in Jetbrains Space In JetBrains Space through 2020-04-22, the session timeout period was configured improperly. | 7.5 |
| 2020-04-22 | CVE-2020-11693 | Unspecified vulnerability in Jetbrains Youtrack JetBrains YouTrack before 2020.1.659 was vulnerable to DoS that could be caused by attaching a malformed TIFF file to an issue. | 7.5 |
| 2020-04-22 | CVE-2020-11692 | Incorrect Default Permissions vulnerability in Jetbrains Youtrack In JetBrains YouTrack before 2020.1.659, DB export was accessible to read-only administrators. | 2.7 |
| 2020-04-22 | CVE-2020-11691 | Unspecified vulnerability in Jetbrains HUB In JetBrains Hub before 2020.1.12099, content spoofing in the Hub OAuth error message was possible. | 7.5 |