Jetbrains
jetbrains
602 CVEs • 38 products
Products (38)
Click to collapseToggle
Products (38)
Click to collapse
CVEs (602)
CVE VENDORS PRODUCTS UPDATED PUBLISHED CVSS |
|---|
In JetBrains IntelliJ IDEA before 2022.3 the built-in web server leaked information about open projects. |
In JetBrains IntelliJ IDEA before 2022.2.4 a buffer overflow in the fsnotifier daemon on macOS was possible. |
In JetBrains Hub before 2022.3.15181 Throttling was missed when sending emails to a particular email address |
In JetBrains TeamCity version before 2022.10, no audit items were added upon editing a user's settings |
In JetBrains TeamCity version before 2022.10, Password parameters could be exposed in the build log if they contained special characters |
In JetBrains TeamCity version before 2022.10, Project Viewer could see scrambled secure values in the MetaRunner settings |
In JetBrains TeamCity version between 2021.2 and 2022.10 access permissions for secure token health items were excessive |
In JetBrains TeamCity before 2022.04.4 environmental variables of "password" type could be logged when using custom Perforce executable |
The installer of JetBrains IntelliJ IDEA before 2022.2.2 was vulnerable to EXE search order hijacking |
In JetBrains Ktor before 2.1.0 the wrong authentication provider could be selected in some cases |
JetBrains Ktor before 2.1.0 was vulnerable to the Reflect File Download attack |
In JetBrains TeamCity before 2022.04.3 the private SSH key could be written to the server log in some cases |
In JetBrains Rider before 2022.2 Trust and Open Project dialog could be bypassed, leading to local code execution |
In JetBrains IntelliJ IDEA before 2022.2 email address validation in the "Git User Name Is Not Defined" dialog was missed |
In JetBrains IntelliJ IDEA before 2022.2 local code execution via a Vagrant executable was possible |
In JetBrains TeamCity before 2022.04.2 build parameter injection was possible |
In JetBrains TeamCity before 2022.04.2 the private SSH key could be written to the build log in some cases |
In JetBrains Hub before 2022.2.14799, insufficient access control allowed the hijacking of untrusted services |
SHA1 implementation in JetBrains Ktor Native 2.0.0 was returning the same value. The issue was fixed in Ktor version 2.0.1. |
In JetBrains TeamCity before 2022.04 potential XSS via Referrer header was possible |