Vulnerabilidades
Resumen — últimos 7 días
Vulnerabilidades nuevas2737▼ 486 respecto a la semana anterior
Críticas / altas1302▼ 188 respecto a la semana anterior
Nueva explotación activa (KEV)3▼ 5 respecto a la semana anterior
Sin puntuar (sin CVSS)227▼ 275 respecto a la semana anterior
693 resultados, ordenados por fecha de publicación (más recientes primero)
| CVE | Estado | Severidad | EPSS | Explotación activa | Tecnologías afectadas | Publicada ▼ | Modificada | Descripción |
|---|---|---|---|---|---|---|---|---|
| Modificada | Media (5.3) | 0.36% | — | Jetbrains Youtrack | 18/6/2024 | 17/6/2026 | In JetBrains YouTrack before 2024.2.34646 the Guest User Account was enabled for attaching files to articles | |
| Modificada | Alta (7.5) | 4.9% | 💥 PoC | Jetbrains AquaJetbrains ClionJetbrains DatagripJetbrains Dataspell+9 | 10/6/2024 | 17/6/2026 | GitHub access token could be exposed to third-party sites in JetBrains IDEs after version 2023.1 and less than: IntelliJ IDEA 2023.1.7, 2023.2.7, 2023.3.7, 2024.1.3, 2024.2 EAP3; Aqua 2024.1.2; CLion 2023.1.7, 2023.2.4, 2023.3.5, 2024.1.3, 2024.2 EAP2; DataGrip 2023.1.3, 2023.2.4, 2023.3.5, 2024.1.4; DataSpell… | |
| Analizada | Crítica (9.8) | 0.46% | — | Jetbrains Teamcity | 29/5/2024 | 17/6/2026 | In JetBrains TeamCity before 2022.04.7, 2022.10.6, 2023.05.6, 2023.11.5 authentication bypass was possible in specific edge cases | |
| Analizada | Alta (7.5) | 0.38% | — | Jetbrains Teamcity | 29/5/2024 | 17/6/2026 | In JetBrains TeamCity before 2024.03.2 server was susceptible to DoS attacks with incorrect auth tokens | |
| Analizada | Alta (8.1) | 0.33% | — | Jetbrains Teamcity | 29/5/2024 | 17/6/2026 | In JetBrains TeamCity before 2024.03.2 certain TeamCity API endpoints did not check user permissions | |
| Analizada | Alta (8.1) | 0.33% | — | Jetbrains Teamcity | 29/5/2024 | 17/6/2026 | In JetBrains TeamCity before 2024.03.2 users could perform actions that should not be available to them based on their permissions | |
| Analizada | Media (5.3) | 0.34% | — | Jetbrains Teamcity | 29/5/2024 | 17/6/2026 | In JetBrains TeamCity before 2024.03.2 technical information regarding TeamCity server could be exposed | |
| Analizada | Media (5.4) | 0.27% | — | Jetbrains Teamcity | 29/5/2024 | 17/6/2026 | In JetBrains TeamCity before 2024.03.2 stored XSS via build step settings was possible | |
| Analizada | Media (5.4) | 0.27% | — | Jetbrains Teamcity | 29/5/2024 | 17/6/2026 | In JetBrains TeamCity before 2024.03.2 several stored XSS in untrusted builds settings were possible | |
| Analizada | Media (6.1) | 0.27% | — | Jetbrains Teamcity | 29/5/2024 | 17/6/2026 | In JetBrains TeamCity before 2023.05.6 reflected XSS on the subscriptions page was possible | |
| Analizada | Media (5.4) | 0.26% | — | Jetbrains Teamcity | 29/5/2024 | 17/6/2026 | In JetBrains TeamCity before 2023.05.6, 2023.11.5 stored XSS in Commit status publisher was possible | |
| Analizada | Media (5.4) | 0.27% | — | Jetbrains Teamcity | 29/5/2024 | 17/6/2026 | In JetBrains TeamCity before 2022.04.7, 2022.10.6, 2023.05.6, 2023.11.5 stored XSS via OAuth connection settings was possible | |
| Analizada | Media (5.4) | 0.27% | — | Jetbrains Teamcity | 29/5/2024 | 17/6/2026 | In JetBrains TeamCity before 2022.04.7, 2022.10.6, 2023.05.6, 2023.11.5 stored XSS via issue tracker integration was possible | |
| Analizada | Media (5.4) | 0.27% | — | Jetbrains Teamcity | 29/5/2024 | 17/6/2026 | In JetBrains TeamCity before 2022.04.7, 2022.10.6, 2023.05.6, 2023.11.5 reflected XSS via OAuth provider configuration was possible | |
| Analizada | Media (6.1) | 0.27% | — | Jetbrains Teamcity | 29/5/2024 | 17/6/2026 | In JetBrains TeamCity before 2022.04.7, 2022.10.6, 2023.05.6, 2023.11.5 stored XSS via third-party reports was possible | |
| Analizada | Media (6.1) | 0.28% | — | Jetbrains Teamcity | 29/5/2024 | 17/6/2026 | In JetBrains TeamCity before 2022.04.7, 2022.10.6, 2023.05.6, 2023.11.5 an XSS could be executed via certain report grouping and filtering operations | |
| Analizada | Alta (8.1) | 0.28% | — | Jetbrains Teamcity | 29/5/2024 | 17/6/2026 | In JetBrains TeamCity before 2022.04.7, 2022.10.6, 2023.05.6, 2023.11.5, 2024.03.2 a third-party agent could impersonate a cloud agent | |
| Analizada | Media (6.5) | 0.33% | — | Jetbrains Teamcity | 29/5/2024 | 17/6/2026 | In JetBrains TeamCity before 2022.04.7, 2022.10.6, 2023.05.6, 2023.11.5 improper access control in Pull Requests and Commit status publisher build features was possible | |
| Analizada | Media (5.4) | 0.27% | — | Jetbrains Teamcity | 29/5/2024 | 17/6/2026 | In JetBrains TeamCity before 2022.04.7, 2022.10.6, 2023.05.6, 2023.11.5 several Stored XSS in code inspection reports were possible | |
| Analizada | Media (6.5) | 0.50% | — | Jetbrains Teamcity | 29/5/2024 | 17/6/2026 | In JetBrains TeamCity before 2022.04.7, 2022.10.6, 2023.05.6, 2023.11.5, 2024.03.2 path traversal allowing to read files from server was possible | |
| Analizada | Media (6.1) | 0.27% | — | Jetbrains Teamcity | 16/5/2024 | 17/6/2026 | In JetBrains TeamCity before 2023.11 stored XSS during restore from backup was possible | |
| Analizada | Media (5.5) | 0.27% | — | Jetbrains Teamcity | 16/5/2024 | 17/6/2026 | In JetBrains TeamCity before 2024.03.1 commit status publisher didn't check project scope of the GitHub App token | |
| Analizada | Media (6.1) | 0.29% | — | Jetbrains Teamcity | 16/5/2024 | 17/6/2026 | In JetBrains TeamCity between 2024.03 and 2024.03.1 several stored XSS in the available updates page were possible | |
| Analizada | Alta (7.5) | 0.27% | — | Jetbrains Youtrack | 16/5/2024 | 17/6/2026 | In JetBrains YouTrack before 2024.1.29548 the SMTPS protocol communication lacked proper certificate hostname validation | |
| Analizada | Media (4.9) | 0.43% | — | Jetbrains Teamcity | 28/3/2024 | 17/6/2026 | In JetBrains TeamCity before 2024.03 server administrators could remove arbitrary files from the server by installing tools |