Intellij Idea
by Jetbrains
CVEs (62)
| CVE | Vendor / Product | Sev | Risk | CVSS | EPSS | KEV | Published | Description |
|---|---|---|---|---|---|---|---|---|
| CVE-2022-29812 | 0.00 | — | 0.00 | Apr 28, 2022 | In JetBrains IntelliJ IDEA before 2022.1 notification mechanisms about using Unicode directionality formatting characters were insufficient | |||
| CVE-2022-28651 | 0.00 | — | 0.00 | Apr 5, 2022 | In JetBrains IntelliJ IDEA before 2021.3.3 it was possible to get passwords from protected fields | |||
| CVE-2021-45977 | 0.00 | — | 0.01 | Feb 25, 2022 | 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… | |||
| CVE-2022-24346 | 0.00 | — | 0.00 | Feb 25, 2022 | In JetBrains IntelliJ IDEA before 2021.3.1, local code execution via RLO (Right-to-Left Override) characters was possible. | |||
| CVE-2022-24345 | 0.00 | — | 0.00 | Feb 25, 2022 | In JetBrains IntelliJ IDEA before 2021.2.4, local code execution (without permission from a user) upon opening a project was possible. | |||
| CVE-2021-30504 | 0.00 | — | 0.02 | May 11, 2021 | In JetBrains IntelliJ IDEA before 2021.1, DoS was possible because of unbounded resource allocation. | |||
| CVE-2021-29263 | 0.00 | — | 0.00 | May 11, 2021 | In JetBrains IntelliJ IDEA 2020.3.3, local code execution was possible because of insufficient checks when getting the project from VCS. | |||
| CVE-2021-30006 | 0.00 | — | 0.01 | May 11, 2021 | In IntelliJ IDEA before 2020.3.3, XXE was possible, leading to information disclosure. | |||
| CVE-2021-25758 | 0.00 | — | 0.01 | Feb 3, 2021 | In JetBrains IntelliJ IDEA before 2020.3, potentially insecure deserialization of the workspace model could lead to local code execution. | |||
| CVE-2021-25756 | 0.00 | — | 0.01 | Feb 3, 2021 | In JetBrains IntelliJ IDEA before 2020.2, HTTP links were used for several remote repositories instead of HTTPS. | |||
| CVE-2020-27622 | 0.00 | — | 0.01 | Nov 16, 2020 | In JetBrains IntelliJ IDEA before 2020.2, the built-in web server could expose information about the IDE version. | |||
| CVE-2020-11690 | 0.00 | — | 0.02 | Apr 22, 2020 | In JetBrains IntelliJ IDEA before 2020.1, the license server could be resolved to an untrusted host in some cases. | |||
| CVE-2020-7914 | 0.00 | — | 0.02 | Jan 31, 2020 | In JetBrains IntelliJ IDEA 2019.2, an XSLT debugger plugin misconfiguration allows arbitrary file read operations over the network. This issue was fixed in 2019.3. | |||
| CVE-2020-7905 | 0.00 | — | 0.01 | Jan 30, 2020 | Ports listened to by JetBrains IntelliJ IDEA before 2019.3 were exposed to the network. | |||
| CVE-2020-7904 | 0.00 | — | 0.01 | Jan 30, 2020 | In JetBrains IntelliJ IDEA before 2019.3, some Maven repositories were accessed via HTTP instead of HTTPS. | |||
| CVE-2019-18361 | 0.00 | — | 0.00 | Oct 31, 2019 | JetBrains IntelliJ IDEA before 2019.2 allows local user privilege escalation, potentially leading to arbitrary code execution. | |||
| CVE-2019-14954 | 0.00 | — | 0.01 | Oct 1, 2019 | JetBrains IntelliJ IDEA before 2019.2 was resolving the markdown plantuml artifact download link via a cleartext http connection. | |||
| CVE-2019-10104 | 0.00 | — | 0.04 | Jul 3, 2019 | In several JetBrains IntelliJ IDEA Ultimate versions, an Application Server run configuration (for Tomcat, Jetty, Resin, or CloudBees) with the default setting allowed a remote attacker to execute code when the configuration is running, because a JMX server listened on all… | |||
| CVE-2019-9873 | 0.00 | — | 0.02 | Jul 3, 2019 | In several versions of JetBrains IntelliJ IDEA Ultimate, creating Task Servers configurations leads to saving a cleartext unencrypted record of the server credentials in the IDE configuration files. The issue has been fixed in the following versions: 2019.1, 2018.3.5, 2018.2.8,… | |||
| CVE-2019-9872 | 0.00 | — | 0.01 | Jul 3, 2019 | In several versions of JetBrains IntelliJ IDEA Ultimate, creating run configurations for cloud application servers leads to saving a cleartext unencrypted record of the server credentials in the IDE configuration files. If the Settings Repository plugin was then used and… |
- CVE-2022-29812Apr 28, 2022risk 0.00cvss —epss 0.00
In JetBrains IntelliJ IDEA before 2022.1 notification mechanisms about using Unicode directionality formatting characters were insufficient
- CVE-2022-28651Apr 5, 2022risk 0.00cvss —epss 0.00
In JetBrains IntelliJ IDEA before 2021.3.3 it was possible to get passwords from protected fields
- CVE-2021-45977Feb 25, 2022risk 0.00cvss —epss 0.01
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…
- CVE-2022-24346Feb 25, 2022risk 0.00cvss —epss 0.00
In JetBrains IntelliJ IDEA before 2021.3.1, local code execution via RLO (Right-to-Left Override) characters was possible.
- CVE-2022-24345Feb 25, 2022risk 0.00cvss —epss 0.00
In JetBrains IntelliJ IDEA before 2021.2.4, local code execution (without permission from a user) upon opening a project was possible.
- CVE-2021-30504May 11, 2021risk 0.00cvss —epss 0.02
In JetBrains IntelliJ IDEA before 2021.1, DoS was possible because of unbounded resource allocation.
- CVE-2021-29263May 11, 2021risk 0.00cvss —epss 0.00
In JetBrains IntelliJ IDEA 2020.3.3, local code execution was possible because of insufficient checks when getting the project from VCS.
- CVE-2021-30006May 11, 2021risk 0.00cvss —epss 0.01
In IntelliJ IDEA before 2020.3.3, XXE was possible, leading to information disclosure.
- CVE-2021-25758Feb 3, 2021risk 0.00cvss —epss 0.01
In JetBrains IntelliJ IDEA before 2020.3, potentially insecure deserialization of the workspace model could lead to local code execution.
- CVE-2021-25756Feb 3, 2021risk 0.00cvss —epss 0.01
In JetBrains IntelliJ IDEA before 2020.2, HTTP links were used for several remote repositories instead of HTTPS.
- CVE-2020-27622Nov 16, 2020risk 0.00cvss —epss 0.01
In JetBrains IntelliJ IDEA before 2020.2, the built-in web server could expose information about the IDE version.
- CVE-2020-11690Apr 22, 2020risk 0.00cvss —epss 0.02
In JetBrains IntelliJ IDEA before 2020.1, the license server could be resolved to an untrusted host in some cases.
- CVE-2020-7914Jan 31, 2020risk 0.00cvss —epss 0.02
In JetBrains IntelliJ IDEA 2019.2, an XSLT debugger plugin misconfiguration allows arbitrary file read operations over the network. This issue was fixed in 2019.3.
- CVE-2020-7905Jan 30, 2020risk 0.00cvss —epss 0.01
Ports listened to by JetBrains IntelliJ IDEA before 2019.3 were exposed to the network.
- CVE-2020-7904Jan 30, 2020risk 0.00cvss —epss 0.01
In JetBrains IntelliJ IDEA before 2019.3, some Maven repositories were accessed via HTTP instead of HTTPS.
- CVE-2019-18361Oct 31, 2019risk 0.00cvss —epss 0.00
JetBrains IntelliJ IDEA before 2019.2 allows local user privilege escalation, potentially leading to arbitrary code execution.
- CVE-2019-14954Oct 1, 2019risk 0.00cvss —epss 0.01
JetBrains IntelliJ IDEA before 2019.2 was resolving the markdown plantuml artifact download link via a cleartext http connection.
- CVE-2019-10104Jul 3, 2019risk 0.00cvss —epss 0.04
In several JetBrains IntelliJ IDEA Ultimate versions, an Application Server run configuration (for Tomcat, Jetty, Resin, or CloudBees) with the default setting allowed a remote attacker to execute code when the configuration is running, because a JMX server listened on all…
- CVE-2019-9873Jul 3, 2019risk 0.00cvss —epss 0.02
In several versions of JetBrains IntelliJ IDEA Ultimate, creating Task Servers configurations leads to saving a cleartext unencrypted record of the server credentials in the IDE configuration files. The issue has been fixed in the following versions: 2019.1, 2018.3.5, 2018.2.8,…
- CVE-2019-9872Jul 3, 2019risk 0.00cvss —epss 0.01
In several versions of JetBrains IntelliJ IDEA Ultimate, creating run configurations for cloud application servers leads to saving a cleartext unencrypted record of the server credentials in the IDE configuration files. If the Settings Repository plugin was then used and…
Page 3 of 4