Filtered by vendor Jetbrains
Subscriptions
Total
359 CVE
CVE | Vendors | Products | Updated | CVSS v3.1 |
---|---|---|---|---|
CVE-2019-12737 | 1 Jetbrains | 1 Ktor | 2019-10-08 | 5.3 Medium |
UserHashedTableAuth in JetBrains Ktor framework before 1.2.0-rc uses a One-Way Hash with a Predictable Salt for storing user credentials. | ||||
CVE-2019-14955 | 1 Jetbrains | 1 Hub | 2019-10-08 | 5.3 Medium |
In JetBrains Hub versions earlier than 2018.4.11436, there was no option to force a user to change the password and no password expiration policy was implemented. | ||||
CVE-2019-14960 | 1 Jetbrains | 1 Rider | 2019-10-08 | 7.8 High |
JetBrains Rider before 2019.1.2 was using an unsigned JetBrains.Rider.Unity.Editor.Plugin.Repacked.dll file. | ||||
CVE-2019-15042 | 1 Jetbrains | 1 Teamcity | 2019-10-07 | 7.5 High |
An issue was discovered in JetBrains TeamCity 2018.2.4. It had no SSL certificate validation for some external https connections. This was fixed in TeamCity 2019.1. | ||||
CVE-2019-15036 | 1 Jetbrains | 1 Teamcity | 2019-10-03 | 7.2 High |
An issue was discovered in JetBrains TeamCity 2018.2.4. A TeamCity Project administrator could execute any command on the server machine. The issue was fixed in TeamCity 2018.2.5 and 2019.1. | ||||
CVE-2019-14956 | 1 Jetbrains | 1 Youtrack | 2019-10-03 | 4.3 Medium |
JetBrains YouTrack before 2019.2.53938 was using incorrect settings, allowing a user without necessary permissions to get other project names. | ||||
CVE-2019-16171 | 1 Jetbrains | 1 Youtrack | 2019-10-03 | 6.1 Medium |
In JetBrains YouTrack through 2019.2.56594, stored XSS was found on the issue page. | ||||
CVE-2019-15040 | 1 Jetbrains | 1 Youtrack | 2019-10-03 | 8.8 High |
JetBrains YouTrack versions before 2019.1 had a CSRF vulnerability on the settings page. | ||||
CVE-2019-15037 | 1 Jetbrains | 1 Teamcity | 2019-10-03 | 6.1 Medium |
An issue was discovered in JetBrains TeamCity 2018.2.4. It had several XSS vulnerabilities on the settings pages. The issues were fixed in TeamCity 2019.1. | ||||
CVE-2019-14952 | 1 Jetbrains | 1 Youtrack | 2019-10-02 | 6.1 Medium |
JetBrains YouTrack versions before 2019.1.52584 had a possible XSS in the issue titles. | ||||
CVE-2019-14953 | 2 Jetbrains, Mozilla | 2 Youtrack, Firefox | 2019-10-02 | 6.1 Medium |
JetBrains YouTrack versions before 2019.2.53938 had a possible XSS through issue attachments when using the Firefox browser. | ||||
CVE-2019-14961 | 1 Jetbrains | 1 Upsource | 2019-10-02 | 6.1 Medium |
JetBrains Upsource before 2019.1.1412 was not properly escaping HTML tags in a code block comments, leading to XSS. | ||||
CVE-2019-12852 | 1 Jetbrains | 1 Youtrack | 2019-07-10 | N/A |
An SSRF attack was possible on a JetBrains YouTrack server. The issue (1 of 2) was fixed in JetBrains YouTrack 2018.4.49168. | ||||
CVE-2019-12850 | 1 Jetbrains | 1 Youtrack | 2019-07-10 | N/A |
A query injection was possible in JetBrains YouTrack. The issue was fixed in YouTrack 2018.4.49168. | ||||
CVE-2019-12851 | 1 Jetbrains | 1 Youtrack | 2019-07-10 | N/A |
A CSRF vulnerability was detected in one of the admin endpoints of JetBrains YouTrack. The issue was fixed in YouTrack 2018.4.49852. | ||||
CVE-2019-12841 | 1 Jetbrains | 1 Teamcity | 2019-07-09 | N/A |
Incorrect handling of user input in ZIP extraction was detected in JetBrains TeamCity. The issue was fixed in TeamCity 2018.2.2. | ||||
CVE-2019-12842 | 1 Jetbrains | 1 Teamcity | 2019-07-05 | N/A |
A reflected XSS on a user page was detected on one of the JetBrains TeamCity pages. The issue was fixed in TeamCity 2018.2.2. | ||||
CVE-2018-14878 | 1 Jetbrains | 2 Dotpeek, Resharper Ultimate | 2018-10-12 | N/A |
JetBrains dotPeek before 2018.2 and ReSharper Ultimate before 2018.1.4 allow attackers to execute code by decompiling a compiled .NET object (such as a DLL or EXE file) with a specific file, because of Deserialization of Untrusted Data. | ||||
CVE-2014-10036 | 1 Jetbrains | 1 Teamcity | 2017-09-08 | N/A |
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. |