CPE Details
Alerte pour un CPE
Restez informé de toutes modifications pour un CPE spécifique.
CPE Name: cpe:2.3:a:jetbrains:teamcity:2024.07:*:*:*:*:*:*:*
Informations
Vendor
jetbrainsProduct
teamcityVersion
2024.07Related CVE
| CVE ID | Publié | Description | Score | Gravité |
|---|---|---|---|---|
| In JetBrains TeamCity before 2025.03.3 reflected XSS in the NPM Registry integration was possible | 4.8 |
Moyen |
||
| In JetBrains TeamCity before 2025.03.3 usernames were exposed to the users without proper permissions | 4.3 |
Moyen |
||
| In JetBrains TeamCity before 2025.03.3 reflected XSS on diskUsageBuildsStats page was possible | 4.8 |
Moyen |
||
| In JetBrains TeamCity before 2025.03.3 reflected XSS on the favoriteIcon page was possible | 5.4 |
Moyen |
||
| In JetBrains TeamCity before 2025.03.3 a DOM-based XSS at the Performance Monitor page was possible | 5.4 |
Moyen |
||
| In JetBrains TeamCity before 2025.03.2 open redirect was possible on editing VCS Root page | 6.1 |
Moyen |
||
| In JetBrains TeamCity before 2025.03.2 stored XSS via Jira integration was possible | 5.4 |
Moyen |
||
| In JetBrains TeamCity before 2025.03.2 stored XSS via YouTrack integration was possible | 5.4 |
Moyen |
||
| In JetBrains TeamCity before 2025.03.2 stored XSS via GitHub Checks Webhook was possible | 5.4 |
Moyen |
||
| In JetBrains TeamCity before 2025.03.1 stored XSS was possible on Data Directory tab | 6.1 |
Moyen |
||
| In JetBrains TeamCity before 2025.03.1 improper path validation in loggingPreset parameter was possible | 9.8 |
Critique |
||
| In JetBrains TeamCity before 2025.03.1 base64-encoded credentials could be exposed in build logs | 6.5 |
Moyen |
||
| In JetBrains TeamCity before 2025.03 exception could lead to credential leakage on Cloud Profiles page | 7.5 |
Haute |
||
| In JetBrains TeamCity before 2025.03 stored XSS was possible on Cloud Profiles page | 6.1 |
Moyen |
||
| In JetBrains TeamCity before 2025.03 base64 encoded password could be exposed in build log | 6.5 |
Moyen |
||
| In JetBrains TeamCity before 2024.12.2 improper Kubernetes connection settings could expose sensitive resources | 9.1 |
Critique |
||
| In JetBrains TeamCity before 2024.12.2 several DOM-based XSS were possible on the Code Inspection Report tab | 6.1 |
Moyen |
||
| In JetBrains TeamCity before 2024.12.1 improper access control allowed to see Projects’ names in the agent pool | 4.3 |
Moyen |
||
| In JetBrains TeamCity before 2024.12.1 reflected XSS was possible on the Vault Connection page | 6.1 |
Moyen |
||
| In JetBrains TeamCity before 2024.12 insecure XMLParser configuration could lead to potential XXE attack | 7.1 |
Haute |
||
| In JetBrains TeamCity before 2024.12 missing Content-Type header in RemoteBuildLogController response could lead to XSS | 5.4 |
Moyen |
||
| In JetBrains TeamCity before 2024.12 password field value were accessible to users with view settings permission | 5.5 |
Moyen |
||
| In JetBrains TeamCity before 2024.12 backup file exposed user credentials and session cookies | 6.5 |
Moyen |
||
| In JetBrains TeamCity before 2024.12 stored XSS was possible via image name on the agent details page | 5.4 |
Moyen |
||
| In JetBrains TeamCity before 2024.12 access tokens were not revoked after removing user roles | 8.8 |
Haute |
||
| In JetBrains TeamCity before 2024.12 build credentials allowed unauthorized viewing of projects | 4.3 |
Moyen |
||
| In JetBrains TeamCity before 2024.12 improper access control allowed unauthorized users to modify build logs | 5.3 |
Moyen |
||
| In JetBrains TeamCity before 2024.12 improper access control allowed viewing details of unauthorized agents | 4.3 |
Moyen |
||
| In JetBrains TeamCity before 2024.07.3 stored XSS was possible via server global settings | 5.4 |
Moyen |
||
| In JetBrains TeamCity before 2024.07.3 stored XSS was possible in Backup configuration settings | 5.4 |
Moyen |
||
| In JetBrains TeamCity before 2024.07.3 path traversal allowed backup file write to arbitrary location | 7.5 |
Haute |
||
| In JetBrains TeamCity before 2024.07.3 path traversal leading to information disclosure was possible via server backups | 7.5 |
Haute |
||
| In JetBrains TeamCity before 2024.07.3 password could be exposed via Sonar runner REST API | 6.5 |
Moyen |
||
| In JetBrains TeamCity before 2024.07.1 reflected XSS was possible in the AWS Core plugin | 5.4 |
Moyen |
||
| In JetBrains TeamCity before 2024.07.1 reflected XSS was possible on the agentPushPreset page | 6.1 |
Moyen |
||
| In JetBrains TeamCity before 2024.07.1 self XSS was possible in the HashiCorp Vault plugin | 5.4 |
Moyen |
||
| In JetBrains TeamCity before 2024.07.1 multiple stored XSS was possible on Clouds page | 5.4 |
Moyen |
||
| In JetBrains TeamCity before 2024.07.1 possible privilege escalation due to incorrect directory permissions | 7.8 |
Haute |
