CPE Details
JetBrains IntelliJ IDEA 2021.3.1 Release Candidate
2021.3.1
2022-03-07
16h08 +00:00
16h08 +00:00
2022-03-08
11h36 +00:00
11h36 +00:00
Alerte pour un CPE
Stay informed of any changes for a specific CPE.
CPE Name: cpe:2.3:a:jetbrains:intellij_idea:2021.3.1:rc:*:*:*:*:*:*
Informations
Vendor
jetbrainsProduct
intellij_ideaVersion
2021.3.1Update
rcRelated CVE
| CVE ID | Published | Description | Score | Severity |
|---|---|---|---|---|
| In JetBrains IntelliJ IDEA before 2024.1 hTML injection via the project name was possible | 6.1 |
Medium |
||
| GitHub access token could be exposed to third-party sites in JetBrains IDEs after version 2023.1 and less than: IntelliJ IDEA 2023.1.7, 2023.2.7, 2023.3.7, 2024.1.3, 2024.2 EAP3; Aqua 2024.1.2; CLion 2023.1.7, 2023.2.4, 2023.3.5, 2024.1.3, 2024.2 EAP2; DataGrip 2023.1.3, 2023.2.4, 2023.3.5, 2024.1.4; DataSpell 2023.1.6, 2023.2.7, 2023.3.6, 2024.1.2, 2024.2 EAP1; GoLand 2023.1.6, 2023.2.7, 2023.3.7, 2024.1.3, 2024.2 EAP3; MPS 2023.2.1, 2023.3.1, 2024.1 EAP2; PhpStorm 2023.1.6, 2023.2.6, 2023.3.7, 2024.1.3, 2024.2 EAP3; PyCharm 2023.1.6, 2023.2.7, 2023.3.6, 2024.1.3, 2024.2 EAP2; Rider 2023.1.7, 2023.2.5, 2023.3.6, 2024.1.3; RubyMine 2023.1.7, 2023.2.7, 2023.3.7, 2024.1.3, 2024.2 EAP4; RustRover 2024.1.1; WebStorm 2023.1.6, 2023.2.7, 2023.3.7, 2024.1.4 | 9.3 |
Critical |
||
| In JetBrains IntelliJ IDEA before 2023.3.3 a plugin for JetBrains Space was able to send an authentication token to an inappropriate URL | 6.1 |
Medium |
||
| In JetBrains IntelliJ IDEA before 2023.3.3 path traversal was possible when unpacking archives | 4.3 |
Medium |
||
| In JetBrains IntelliJ IDEA before 2023.3.2 code execution was possible in Untrusted Project mode via a malicious plugin repository specified in the project configuration | 9.8 |
Critical |
||
| In JetBrains IntelliJ IDEA before 2023.2 plugin for Space was requesting excessive permissions | 7.8 |
High |
||
| In JetBrains IntelliJ IDEA before 2023.1.4 license dialog could be suppressed in certain cases | 3.3 |
Low |
||
| 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. | 7.5 |
High |
||
| In JetBrains IntelliJ IDEA before 2023.1 the bundled version of Chromium wasn't sandboxed. | 8.8 |
High |
||
| In JetBrains IntelliJ IDEA before 2023.1 in some cases, Gradle and Maven projects could be imported without the “Trust Project” confirmation. | 7.8 |
High |
||
| In JetBrains IntelliJ IDEA before 2023.1 file content could be disclosed via an external stylesheet path in Markdown preview. | 7.5 |
High |
||
| In JetBrains IntelliJ IDEA before 2022.3.1 code Templates were vulnerable to SSTI attacks. | 7.8 |
High |
||
| In JetBrains IntelliJ IDEA before 2022.3.1 the "Validate JSP File" action used the HTTP protocol to download required JAR files. | 7.5 |
High |
||
| In JetBrains IntelliJ IDEA before 2022.3 a DYLIB injection on macOS was possible. | 7.8 |
High |
||
| In JetBrains IntelliJ IDEA before 2022.3 an XXE attack leading to SSRF via requests to custom plugin repositories was possible. | 5.5 |
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. | 6.2 |
Medium |
||
| In JetBrains IntelliJ IDEA before 2022.3 the built-in web server leaked information about open projects. | 4 |
Medium |
||
| In JetBrains IntelliJ IDEA before 2022.2.4 a buffer overflow in the fsnotifier daemon on macOS was possible. | 7.8 |
High |
||
| The installer of JetBrains IntelliJ IDEA before 2022.2.2 was vulnerable to EXE search order hijacking | 7.8 |
High |
||
| In JetBrains IntelliJ IDEA before 2022.2 email address validation in the "Git User Name Is Not Defined" dialog was missed | 3.6 |
Low |
||
| In JetBrains IntelliJ IDEA before 2022.2 local code execution via a Vagrant executable was possible | 7.8 |
High |
||
| In JetBrains IntelliJ IDEA before 2022.1 local code execution via links in Quick Documentation was possible | 7.7 |
High |
||
| In JetBrains IntelliJ IDEA before 2022.1 origin checks in the internal web server were flawed | 7.1 |
High |
||
| In JetBrains IntelliJ IDEA before 2022.1 reflected XSS via error messages in internal web server was possible | 6.1 |
Medium |
||
| In JetBrains IntelliJ IDEA before 2022.1 HTML injection into IDE messages was possible | 3.2 |
Low |
||
| In JetBrains IntelliJ IDEA before 2022.1 local code execution via workspace settings was possible | 6.9 |
Medium |
||
| In JetBrains IntelliJ IDEA before 2022.1 local code execution via HTML descriptions in custom JSON schemas was possible | 7.7 |
High |
||
| In JetBrains IntelliJ IDEA before 2022.1 local code execution via custom Pandoc path was possible | 6.9 |
Medium |
||
| In JetBrains IntelliJ IDEA before 2022.1 notification mechanisms about using Unicode directionality formatting characters were insufficient | 2.3 |
Low |
||
| In JetBrains IntelliJ IDEA before 2021.3.3 it was possible to get passwords from protected fields | 8.4 |
High |
||
| JetBrains IntelliJ IDEA 2021.3.1 Preview, IntelliJ IDEA 2021.3.1 RC, PyCharm Professional 2021.3.1 RC, GoLand 2021.3.1, PhpStorm 2021.3.1 Preview, PhpStorm 2021.3.1 RC, RubyMine 2021.3.1 Preview, RubyMine 2021.3.1 RC, CLion 2021.3.1, WebStorm 2021.3.1 Preview, and WebStorm 2021.3.1 RC (used as Remote Development backend IDEs) bind to the 0.0.0.0 IP address. The fixed versions are: IntelliJ IDEA 2021.3.1, PyCharm Professional 2021.3.1, GoLand 2021.3.2, PhpStorm 2021.3.1 (213.6461.83), RubyMine 2021.3.1, CLion 2021.3.2, and WebStorm 2021.3.1. | 9.8 |
Critical |
2025©
tesweb SA
