In JetBrains TeamCity before 2020.2.1, a user could get access to the GitHub access token of another user.
Search vulnerabilities
JetBrains TeamCity before 2020.2 was vulnerable to reflected XSS on several pages.
In JetBrains TeamCity before 2020.2.2, TeamCity server DoS was possible via server integration.
In JetBrains YouTrack before 2020.6.1099, project information could be potentially disclosed.
In JetBrains YouTrack before 2020.5.3123, server-side template injection (SSTI) was possible, which could lead to code execution.
In JetBrains YouTrack before 2020.4.6808, the YouTrack administrator wasn't able to access attachments.
In JetBrains YouTrack before 2020.4.4701, permissions for attachments actions were checked improperly.
In JetBrains YouTrack before 2020.6.1767, an issue's existence could be disclosed via YouTrack command execution.
In JetBrains YouTrack before 2020.4.4701, improper resource access checks were made.
In JetBrains YouTrack before 2020.4.4701, CSRF via attachment upload was possible.
In JetBrains PhpStorm before 2020.3, source code could be added to debug logs.
In JetBrains Ktor before 1.4.2, weak cipher suites were enabled by default.
In JetBrains Ktor before 1.4.3, HTTP Request Smuggling was possible.
In JetBrains Ktor before 1.5.0, a birthday attack on SessionStorage key was possible.
In JetBrains Hub before 2020.1.12669, information disclosure via the public API was possible.
In JetBrains Hub before 2020.1.12629, an authenticated user can delete 2FA settings of any other user.
In JetBrains IntelliJ IDEA before 2020.3, potentially insecure deserialization of the workspace model could lead to local code execution.
In JetBrains Hub before 2020.1.12629, an open redirect was possible.
In JetBrains IntelliJ IDEA before 2020.2, HTTP links were used for several remote repositories instead of HTTPS.
In JetBrains Code With Me before 2020.3, an attacker on the local network, knowing a session ID, could get access to the encrypted traffic.