Total
51 CVE
CVE | Vendors | Products | Updated | CVSS v2 | CVSS v3 |
---|---|---|---|---|---|
CVE-2022-48433 | 1 Jetbrains | 1 Intellij Idea | 2024-11-21 | N/A | 6.1 MEDIUM |
In JetBrains IntelliJ IDEA before 2023.1 the NTLM hash could leak through an API method used in the IntelliJ IDEA built-in web server. | |||||
CVE-2022-48432 | 1 Jetbrains | 1 Intellij Idea | 2024-11-21 | N/A | 5.2 MEDIUM |
In JetBrains IntelliJ IDEA before 2023.1 the bundled version of Chromium wasn't sandboxed. | |||||
CVE-2022-48431 | 1 Jetbrains | 1 Intellij Idea | 2024-11-21 | N/A | 4.5 MEDIUM |
In JetBrains IntelliJ IDEA before 2023.1 in some cases, Gradle and Maven projects could be imported without the “Trust Project” confirmation. | |||||
CVE-2022-48430 | 1 Jetbrains | 1 Intellij Idea | 2024-11-21 | N/A | 5.5 MEDIUM |
In JetBrains IntelliJ IDEA before 2023.1 file content could be disclosed via an external stylesheet path in Markdown preview. | |||||
CVE-2022-47896 | 1 Jetbrains | 1 Intellij Idea | 2024-11-21 | N/A | 5.0 MEDIUM |
In JetBrains IntelliJ IDEA before 2022.3.1 code Templates were vulnerable to SSTI attacks. | |||||
CVE-2022-47895 | 1 Jetbrains | 1 Intellij Idea | 2024-11-21 | N/A | 4.7 MEDIUM |
In JetBrains IntelliJ IDEA before 2022.3.1 the "Validate JSP File" action used the HTTP protocol to download required JAR files. | |||||
CVE-2022-46828 | 2 Apple, Jetbrains | 2 Macos, Intellij Idea | 2024-11-21 | N/A | 5.2 MEDIUM |
In JetBrains IntelliJ IDEA before 2022.3 a DYLIB injection on macOS was possible. | |||||
CVE-2022-46827 | 1 Jetbrains | 1 Intellij Idea | 2024-11-21 | N/A | 3.9 LOW |
In JetBrains IntelliJ IDEA before 2022.3 an XXE attack leading to SSRF via requests to custom plugin repositories was possible. | |||||
CVE-2022-46826 | 1 Jetbrains | 1 Intellij Idea | 2024-11-21 | N/A | 6.2 MEDIUM |
In JetBrains IntelliJ IDEA before 2022.3 the built-in web server allowed an arbitrary file to be read by exploiting a path traversal vulnerability. | |||||
CVE-2022-46825 | 1 Jetbrains | 1 Intellij Idea | 2024-11-21 | N/A | 4.0 MEDIUM |
In JetBrains IntelliJ IDEA before 2022.3 the built-in web server leaked information about open projects. | |||||
CVE-2022-46824 | 2 Apple, Jetbrains | 2 Macos, Intellij Idea | 2024-11-21 | N/A | 5.6 MEDIUM |
In JetBrains IntelliJ IDEA before 2022.2.4 a buffer overflow in the fsnotifier daemon on macOS was possible. | |||||
CVE-2022-40978 | 1 Jetbrains | 1 Intellij Idea | 2024-11-21 | N/A | 7.5 HIGH |
The installer of JetBrains IntelliJ IDEA before 2022.2.2 was vulnerable to EXE search order hijacking | |||||
CVE-2022-37010 | 1 Jetbrains | 1 Intellij Idea | 2024-11-21 | N/A | 3.6 LOW |
In JetBrains IntelliJ IDEA before 2022.2 email address validation in the "Git User Name Is Not Defined" dialog was missed | |||||
CVE-2022-37009 | 1 Jetbrains | 1 Intellij Idea | 2024-11-21 | N/A | 3.9 LOW |
In JetBrains IntelliJ IDEA before 2022.2 local code execution via a Vagrant executable was possible | |||||
CVE-2022-29819 | 1 Jetbrains | 1 Intellij Idea | 2024-11-21 | 4.4 MEDIUM | 6.9 MEDIUM |
In JetBrains IntelliJ IDEA before 2022.1 local code execution via links in Quick Documentation was possible | |||||
CVE-2022-29818 | 1 Jetbrains | 1 Intellij Idea | 2024-11-21 | 3.6 LOW | 3.9 LOW |
In JetBrains IntelliJ IDEA before 2022.1 origin checks in the internal web server were flawed | |||||
CVE-2022-29817 | 1 Jetbrains | 1 Intellij Idea | 2024-11-21 | 4.3 MEDIUM | 3.9 LOW |
In JetBrains IntelliJ IDEA before 2022.1 reflected XSS via error messages in internal web server was possible | |||||
CVE-2022-29816 | 1 Jetbrains | 1 Intellij Idea | 2024-11-21 | 2.1 LOW | 2.8 LOW |
In JetBrains IntelliJ IDEA before 2022.1 HTML injection into IDE messages was possible | |||||
CVE-2022-29815 | 1 Jetbrains | 1 Intellij Idea | 2024-11-21 | 4.6 MEDIUM | 6.9 MEDIUM |
In JetBrains IntelliJ IDEA before 2022.1 local code execution via workspace settings was possible | |||||
CVE-2022-29814 | 1 Jetbrains | 1 Intellij Idea | 2024-11-21 | 4.4 MEDIUM | 6.9 MEDIUM |
In JetBrains IntelliJ IDEA before 2022.1 local code execution via HTML descriptions in custom JSON schemas was possible |