| CVE-2021-30006 | ALTO7.5 | In IntelliJ IDEA before 2020.3.3, XXE was possible, leading to information disclosure. | 11/05/2021 |
| CVE-2021-29263 | ALTO7.8 | In JetBrains IntelliJ IDEA 2020.3.3, local code execution was possible because of insufficient checks when getting the project from VCS. | 11/05/2021 |
| CVE-2021-25758 | ALTO7.8 | In JetBrains IntelliJ IDEA before 2020.3, potentially insecure deserialization of the workspace model could lead to local code execution. | 03/02/2021 |
| CVE-2021-25756 | MEDIO5.3 | In JetBrains IntelliJ IDEA before 2020.2, HTTP links were used for several remote repositories instead of HTTPS. | 03/02/2021 |
| CVE-2020-27622 | MEDIO5.3 | In JetBrains IntelliJ IDEA before 2020.2, the built-in web server could expose information about the IDE version. | 16/11/2020 |
| CVE-2020-11690 | CRÍTICO9.8 | In JetBrains IntelliJ IDEA before 2020.1, the license server could be resolved to an untrusted host in some cases. | 22/04/2020 |
| CVE-2020-7914 | ALTO7.5 | 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. | 31/01/2020 |
| CVE-2020-7905 | ALTO7.5 | Ports listened to by JetBrains IntelliJ IDEA before 2019.3 were exposed to the network. | 30/01/2020 |
| CVE-2020-7904 | ALTO7.4 | In JetBrains IntelliJ IDEA before 2019.3, some Maven repositories were accessed via HTTP instead of HTTPS. | 30/01/2020 |
| CVE-2019-18361 | MEDIO5.3 | JetBrains IntelliJ IDEA before 2019.2 allows local user privilege escalation, potentially leading to arbitrary code execution. | 31/10/2019 |
| CVE-2019-14954 | MEDIO5.9 | JetBrains IntelliJ IDEA before 2019.2 was resolving the markdown plantuml artifact download link via a cleartext http connection. | 01/10/2019 |
| CVE-2019-9873 | CRÍTICO9.8 | 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, and 2018.1.8. | 03/07/2019 |
| CVE-2019-9872 | ALTO8.1 | 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 configured to synchronize IDE settings using a p | 03/07/2019 |
| CVE-2019-9823 | CRÍTICO9.8 | In several JetBrains IntelliJ IDEA versions, creating remote run configurations of JavaEE application servers leads to saving a cleartext record of the server credentials in the IDE configuration files. The issue has been fixed in the following versions: 2018.3.5, 2018.2.8, 2018.1.8. | 03/07/2019 |
| CVE-2019-9186 | CRÍTICO9.8 | In several JetBrains IntelliJ IDEA versions, a Spring Boot run configuration with the default setting allowed remote attackers to execute code when the configuration is running, because a JMX server listens on all interfaces (instead of listening on only the localhost interface). This issue has been fixed in the follow | 03/07/2019 |
| CVE-2019-10104 | CRÍTICO9.8 | 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 interfaces instead of localhost only. The issu | 03/07/2019 |
| CVE-2017-8316 | ALTO7.5 | IntelliJ IDEA XML parser was found vulnerable to XML External Entity attack, an attacker can exploit the vulnerability by implementing malicious code on both Androidmanifest.xml. | 03/08/2018 |