JetBrains vulnerabilities
545 CVEs and advisories name JetBrains as an affected vendor, 4 of them on CISA's Known Exploited Vulnerabilities catalog, newest first. Follow it as a feed.
- CVE-2022-44624In JetBrains TeamCity version before 2022.10, Password parameters could be exposed in the build log if they contained special characters
- CVE-2022-44623In JetBrains TeamCity version before 2022.10, Project Viewer could see scrambled secure values in the MetaRunner settings
- CVE-2022-44622In JetBrains TeamCity version between 2021.2 and 2022.10 access permissions for secure token health items were excessive
- CVE-2022-40979In JetBrains TeamCity before 2022.04.4 environmental variables of "password" type could be logged when using custom Perforce executable
- CVE-2022-40978The installer of JetBrains IntelliJ IDEA before 2022.2.2 was vulnerable to EXE search order hijacking
- CVE-2022-38180In JetBrains Ktor before 2.1.0 the wrong authentication provider could be selected in some cases
- CVE-2022-38179JetBrains Ktor before 2.1.0 was vulnerable to the Reflect File Download attack
- CVE-2022-38133In JetBrains TeamCity before 2022.04.3 the private SSH key could be written to the server log in some cases
- CVE-2022-37396In JetBrains Rider before 2022.2 Trust and Open Project dialog could be bypassed, leading to local code execution
- CVE-2022-37010In JetBrains IntelliJ IDEA before 2022.2 email address validation in the "Git User Name Is Not Defined" dialog was missed
- CVE-2022-37009In JetBrains IntelliJ IDEA before 2022.2 local code execution via a Vagrant executable was possible
- CVE-2022-36322In JetBrains TeamCity before 2022.04.2 build parameter injection was possible
- CVE-2022-36321In JetBrains TeamCity before 2022.04.2 the private SSH key could be written to the build log in some cases
- CVE-2022-34894In JetBrains Hub before 2022.2.14799, insufficient access control allowed the hijacking of untrusted services
- CVE-2022-29930SHA1 implementation in JetBrains Ktor Native 2.0.0 was returning the same value.
- CVE-2022-29929In JetBrains TeamCity before 2022.04 potential XSS via Referrer header was possible
- CVE-2022-29928In JetBrains TeamCity before 2022.04 leak of secrets in TeamCity agent logs was possible
- CVE-2022-29927In JetBrains TeamCity before 2022.04 reflected XSS on the Build Chain Status page was possible
- CVE-2022-29821In JetBrains Rider before 2022.1 local code execution via links in ReSharper Quick Documentation was possible
- CVE-2022-29820In JetBrains PyCharm before 2022.1 exposure of the debugger port to the internal network was possible
- CVE-2022-29819In JetBrains IntelliJ IDEA before 2022.1 local code execution via links in Quick Documentation was possible
- CVE-2022-29818In JetBrains IntelliJ IDEA before 2022.1 origin checks in the internal web server were flawed
- CVE-2022-29817In JetBrains IntelliJ IDEA before 2022.1 reflected XSS via error messages in internal web server was possible
- CVE-2022-29816In JetBrains IntelliJ IDEA before 2022.1 HTML injection into IDE messages was possible
- CVE-2022-29815In JetBrains IntelliJ IDEA before 2022.1 local code execution via workspace settings was possible
- CVE-2022-29814In JetBrains IntelliJ IDEA before 2022.1 local code execution via HTML descriptions in custom JSON schemas was possible
- CVE-2022-29813In JetBrains IntelliJ IDEA before 2022.1 local code execution via custom Pandoc path was possible
- CVE-2022-29812In JetBrains IntelliJ IDEA before 2022.1 notification mechanisms about using Unicode directionality formatting characters were insufficient
- CVE-2022-29811In JetBrains Hub before 2022.1.14638 stored XSS via project icon was possible.
- CVE-2022-29035In JetBrains Ktor Native before version 2.0.0 random values used for nonce generation weren't using SecureRandom implementations