| CVE |
Vendors |
Products |
Updated |
CVSS v3.1 |
| In JetBrains IntelliJ IDEA before 2022.3.1 the "Validate JSP File" action used the HTTP protocol to download required JAR files. |
| In JetBrains IntelliJ IDEA before 2022.3.1 code Templates were vulnerable to SSTI attacks. |
| Cross-site scripting (XSS) vulnerability in JetBrains TeamCity before 8.1 allows remote attackers to inject arbitrary web script or HTML via the cameFromUrl parameter to feed/generateFeedUrl.html. |
| Unspecified vulnerability in JetBrains TeamCity before 8.1 allows remote attackers to obtain sensitive information via unknown vectors. |
| In JetBrains TeamCity before 2022.10.2 jVMTI was enabled by default on agents. |
| In JetBrains TeamCity before 2022.10.2 there was an XSS vulnerability in the group creation process. |
| In JetBrains TeamCity before 2022.10.2 there was an XSS vulnerability in the user creation process. |
| In JetBrains TeamCity before 2022.10.3 stored XSS in Perforce connection settings was possible |
| In JetBrains Hub before 2022.3.15573, 2022.2.15572, 2022.1.15583 reflected XSS in dashboards was possible
|
| In JetBrains TeamCity before 2022.10.3 stored XSS on the SSH keys page was possible |
| In JetBrains TeamCity before 2022.10.3 stored XSS on “Pending changes” and “Changes” tabs was possible |
| In JetBrains IntelliJ IDEA before 2023.1 file content could be disclosed via an external stylesheet path in Markdown preview. |
| In JetBrains IntelliJ IDEA before 2023.1 in some cases, Gradle and Maven projects could be imported without the “Trust Project” confirmation. |
| In JetBrains IntelliJ IDEA before 2023.1 the bundled version of Chromium wasn't sandboxed. |
| 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. |
| In JetBrains PhpStorm before 2023.1 source code could be logged in the local idea.log file |
| In JetBrains TeamCity before 2023.05.6, 2023.11.5 stored XSS in Commit status publisher was possible |
| In JetBrains TeamCity before 2022.04.7, 2022.10.6, 2023.05.6, 2023.11.5 authentication bypass was possible in specific edge cases |
| In JetBrains Ktor before 2.3.0 path traversal in the `resolveResource` method was possible
|
| In JetBrains Hub before 2023.1.15725 SSRF protection in Auth Module integration was missing
|