Vulnerabilities > Jetbrains
DATE | CVE | VULNERABILITY TITLE | RISK |
---|---|---|---|
2024-10-28 | CVE-2024-50573 | Missing Authorization vulnerability in Jetbrains HUB In JetBrains Hub before 2024.3.47707 improper access control allowed users to generate permanent tokens for unauthorized services | 5.4 |
2024-10-28 | CVE-2024-50574 | Unspecified vulnerability in Jetbrains Youtrack In JetBrains YouTrack before 2024.3.47707 potential ReDoS exploit was possible via email header parsing in Helpdesk functionality | 7.5 |
2024-10-28 | CVE-2024-50575 | Cross-site Scripting vulnerability in Jetbrains Youtrack In JetBrains YouTrack before 2024.3.47707 reflected XSS was possible in Widget API | 6.1 |
2024-10-28 | CVE-2024-50576 | Cross-site Scripting vulnerability in Jetbrains Youtrack In JetBrains YouTrack before 2024.3.47707 stored XSS was possible via vendor URL in App manifest | 5.4 |
2024-10-28 | CVE-2024-50577 | Cross-site Scripting vulnerability in Jetbrains Youtrack In JetBrains YouTrack before 2024.3.47707 stored XSS was possible via Angular template injection in Hub settings | 5.4 |
2024-10-28 | CVE-2024-50578 | Cross-site Scripting vulnerability in Jetbrains Youtrack In JetBrains YouTrack before 2024.3.47707 stored XSS was possible via sprint value on agile boards page | 5.4 |
2024-10-28 | CVE-2024-50579 | Cross-site Scripting vulnerability in Jetbrains Youtrack In JetBrains YouTrack before 2024.3.47707 reflected XSS due to insecure link sanitization was possible | 6.1 |
2024-10-28 | CVE-2024-50580 | Cross-site Scripting vulnerability in Jetbrains Youtrack In JetBrains YouTrack before 2024.3.47707 multiple XSS were possible due to insecure markdown parsing and custom rendering rule | 5.4 |
2024-10-28 | CVE-2024-50581 | Cross-site Scripting vulnerability in Jetbrains Youtrack In JetBrains YouTrack before 2024.3.47707 improper HTML sanitization could lead to XSS attack via comment tag | 5.4 |
2024-10-28 | CVE-2024-50582 | Cross-site Scripting vulnerability in Jetbrains Youtrack In JetBrains YouTrack before 2024.3.47707 stored XSS was possible due to improper HTML sanitization in markdown elements | 5.4 |