CPE Details
Alerte pour un CPE
Restez informé de toutes modifications pour un CPE spécifique.
CPE Name: cpe:2.3:a:jetbrains:teamcity:8.0.2:*:*:*:*:*:*:*
Informations
Vendor
jetbrainsProduct
teamcityVersion
8.0.2Related CVE
| CVE ID | Publié | Description | Score | Gravité |
|---|---|---|---|---|
| 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 |
||
| In JetBrains TeamCity before 2024.07 an OAuth code for JetBrains Space could be stolen via Space Application connection | 7.5 |
Haute |
||
| In JetBrains TeamCity before 2024.07 comparison of authorization tokens took non-constant time | 6.5 |
Moyen |
||
| In JetBrains TeamCity before 2024.07 access tokens could continue working after deletion or expiration | 9.8 |
Critique |
||
| In JetBrains TeamCity before 2024.07 stored XSS was possible on Show Connection page | 4.8 |
Moyen |
||
| In JetBrains TeamCity before 2024.07 stored XSS was possible on the Code Inspection tab | 5.4 |
Moyen |
||
| In JetBrains TeamCity before 2024.07 parameters of the "password" type could leak into the build log in some specific cases | 6.5 |
Moyen |
||
| In JetBrains TeamCity before 2024.03.3 application token could be exposed in EC2 Cloud Profile settings | 5.3 |
Moyen |
||
| In JetBrains TeamCity before 2024.03.3 private key could be exposed via testing GitHub App Connection | 5.3 |
Moyen |
||
| In JetBrains TeamCity before 2022.04.7, 2022.10.6, 2023.05.6, 2023.11.5 authentication bypass was possible in specific edge cases | 9.8 |
Critique |
||
| In JetBrains TeamCity before 2024.03.2 server was susceptible to DoS attacks with incorrect auth tokens | 7.5 |
Haute |
||
| In JetBrains TeamCity before 2024.03.2 certain TeamCity API endpoints did not check user permissions | 8.1 |
Haute |
||
| In JetBrains TeamCity before 2024.03.2 users could perform actions that should not be available to them based on their permissions | 8.1 |
Haute |
||
| In JetBrains TeamCity before 2024.03.2 technical information regarding TeamCity server could be exposed | 5.3 |
Moyen |
||
| In JetBrains TeamCity before 2024.03.2 stored XSS via build step settings was possible | 5.4 |
Moyen |
||
| In JetBrains TeamCity before 2024.03.2 several stored XSS in untrusted builds settings were possible | 5.4 |
Moyen |
||
| In JetBrains TeamCity before 2023.05.6 reflected XSS on the subscriptions page was possible | 6.1 |
Moyen |
||
| In JetBrains TeamCity before 2023.05.6, 2023.11.5 stored XSS in Commit status publisher was possible | 5.4 |
Moyen |
||
| In JetBrains TeamCity before 2022.04.7, 2022.10.6, 2023.05.6, 2023.11.5 stored XSS via OAuth connection settings was possible | 5.4 |
Moyen |
||
| In JetBrains TeamCity before 2022.04.7, 2022.10.6, 2023.05.6, 2023.11.5 stored XSS via issue tracker integration was possible | 5.4 |
Moyen |
||
| In JetBrains TeamCity before 2022.04.7, 2022.10.6, 2023.05.6, 2023.11.5 reflected XSS via OAuth provider configuration was possible | 5.4 |
Moyen |
||
| In JetBrains TeamCity before 2022.04.7, 2022.10.6, 2023.05.6, 2023.11.5 stored XSS via third-party reports was possible | 6.1 |
Moyen |
||
| 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 | 6.1 |
Moyen |
||
| 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 | 8.1 |
Haute |
||
| 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 | 6.5 |
Moyen |
||
| 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 | 5.4 |
Moyen |
||
| 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 | 6.5 |
Moyen |
||
| In JetBrains TeamCity before 2023.11 stored XSS during restore from backup was possible | 6.1 |
Moyen |
||
| In JetBrains TeamCity before 2024.03.1 commit status publisher didn't check project scope of the GitHub App token | 5.5 |
Moyen |
||
| In JetBrains TeamCity before 2024.03 server administrators could remove arbitrary files from the server by installing tools | 4.9 |
Moyen |
||
| In JetBrains TeamCity before 2024.03 xXE was possible in the Maven build steps detector | 8.1 |
Haute |
||
| In JetBrains TeamCity before 2024.03 xSS was possible via Agent Distribution settings | 5.4 |
Moyen |
||
| In JetBrains TeamCity before 2024.03 reflected XSS was possible via Space connection configuration | 6.8 |
Moyen |
||
| In JetBrains TeamCity before 2024.03 2FA could be bypassed by providing a special URL parameter | 7.4 |
Haute |
||
| In JetBrains TeamCity before 2024.03 open redirect was possible on the login page | 6.1 |
Moyen |
||
| In JetBrains TeamCity before 2024.03 authenticated users without administrative permissions could register other users when self-registration was disabled | 6.5 |
Moyen |
||
| In JetBrains TeamCity before 2023.11 users with access to the agent machine might obtain permissions of the user running the agent process | 7.8 |
Haute |
||
| In JetBrains TeamCity before 2023.11.4 presigned URL generation requests in S3 Artifact Storage plugin were authorized improperly | 5.8 |
Moyen |
||
| In JetBrains TeamCity before 2023.11.4 path traversal allowing to perform limited admin actions was possible | 7.3 |
Haute |
||
| In JetBrains TeamCity before 2023.11.4 authentication bypass allowing to perform admin actions was possible | 9.8 |
Critique |
||
| In JetBrains TeamCity before 2023.11.3 authentication bypass leading to RCE was possible | 9.8 |
Critique |
||
| In JetBrains TeamCity before 2023.11.3 path traversal allowed reading data within JAR archives | 5.3 |
Moyen |
||
| In JetBrains TeamCity before 2023.11.2 limited directory traversal was possible in the Kotlin DSL documentation | 5.3 |
Moyen |
||
| In JetBrains TeamCity before 2023.11.2 stored XSS via agent distribution was possible | 5.4 |
Moyen |
||
| In JetBrains TeamCity before 2023.11.2 access control at the S3 Artifact Storage plugin endpoint was missed | 5.3 |
Moyen |
||
| In JetBrains TeamCity before 2023.11.1 a CSRF on login was possible | 8.8 |
Haute |
||
| In JetBrains TeamCity before 2023.05.4 stored XSS was possible during nodes configuration | 5.4 |
Moyen |
||
| In JetBrains TeamCity before 2023.05.4 authentication bypass leading to RCE on TeamCity Server was possible | 9.8 |
Critique |
||
| In JetBrains TeamCity before 2023.05.3 reflected XSS was possible during user registration | 6.1 |
Moyen |
||
| In JetBrains TeamCity before 2023.05.3 reflected XSS was possible during copying Build Step | 6.1 |
Moyen |
||
| In JetBrains TeamCity before 2023.05.3 stored XSS was possible during Cloud Profiles configuration | 5.4 |
Moyen |
||
| In JetBrains TeamCity before 2023.05.2 reflected XSS via GitHub integration was possible | 6.1 |
Moyen |
||
| In JetBrains TeamCity before 2023.05.2 a ReDoS attack was possible via integration with issue trackers | 7.5 |
Haute |
||
| In JetBrains TeamCity before 2023.05.2 a token with limited permissions could be used to gain full account access | 8.8 |
Haute |
||
| In JetBrains TeamCity before 2023.05.1 build parameters of the "password" type could be written to the agent log | 6.5 |
Moyen |
||
| In JetBrains TeamCity before 2023.05.1 reflected XSS via the Referer header was possible during artifact downloads | 6.1 |
Moyen |
||
| In JetBrains TeamCity before 2023.05.1 stored XSS while viewing the build log was possible | 5.4 |
Moyen |
||
| In JetBrains TeamCity before 2023.05.1 build chain parameters of the "password" type could be written to the agent log | 6.5 |
Moyen |
||
| In JetBrains TeamCity before 2023.05.1 stored XSS while running custom builds was possible | 5.4 |
Moyen |
||
| In JetBrains TeamCity before 2023.05.1 parameters of the "password" type could be shown in the UI in certain composite build configurations | 6.5 |
Moyen |
||
| In JetBrains TeamCity before 2023.05.1 stored XSS when using a custom theme was possible | 5.4 |
Moyen |
||
| JetBrains TeamCity 8 and 9 before 9.0.2 allows bypass of account-creation restrictions via a crafted request because the required request data can be deduced by reading HTML and JavaScript files that are returned to the web browser after an initial unauthenticated request. | 6.5 |
Moyen |
||
| In JetBrains TeamCity before 2023.05 stored XSS in GitLab Connection page was possible | 5.4 |
Moyen |
||
| In JetBrains TeamCity before 2023.05 authentication checks were missing – 2FA was not checked for some sensitive account actions | 6.5 |
Moyen |
||
| In JetBrains TeamCity before 2023.05 a specific endpoint was vulnerable to brute force attacks | 7.5 |
Haute |
||
| In JetBrains TeamCity before 2023.05 reflected XSS in the Subscriptions page was possible | 6.1 |
Moyen |
||
| In JetBrains TeamCity before 2023.05 stored XSS in the NuGet feed page was possible | 5.4 |
Moyen |
||
| In JetBrains TeamCity before 2023.05 open redirect during oAuth configuration was possible | 4.8 |
Moyen |
||
| In JetBrains TeamCity before 2023.05 parameters of the "password" type from build dependencies could be logged in some cases | 5.3 |
Moyen |
||
| In JetBrains TeamCity before 2023.05 possible XSS in the Plugin Vendor URL was possible | 6.1 |
Moyen |
||
| In JetBrains TeamCity before 2023.05 stored XSS in the Show Connection page was possible | 5.4 |
Moyen |
||
| In JetBrains TeamCity before 2023.05 stored XSS in the Commit Status Publisher window was possible | 5.4 |
Moyen |
||
| In JetBrains TeamCity before 2023.05 improper permission checks allowed users without appropriate permissions to edit Build Configuration settings via REST API | 4.3 |
Moyen |
||
| In JetBrains TeamCity before 2023.05 bypass of permission checks allowing to perform admin actions was possible | 9.8 |
Critique |
||
| In JetBrains TeamCity before 2022.10.3 stored XSS on the SSH keys page was possible | 5.4 |
Moyen |
||
| In JetBrains TeamCity before 2022.10.3 stored XSS on “Pending changes” and “Changes” tabs was possible | 5.4 |
Moyen |
||
| In JetBrains TeamCity before 2022.10.2 there was an XSS vulnerability in the group creation process. | 6.1 |
Moyen |
||
| In JetBrains TeamCity before 2022.10.2 there was an XSS vulnerability in the user creation process. | 6.1 |
Moyen |
||
| In JetBrains TeamCity before 2022.10.2 jVMTI was enabled by default on agents. | 9.8 |
Critique |
||
| In JetBrains TeamCity version before 2022.10, Project Viewer could see scrambled secure values in the MetaRunner settings | 7.5 |
Haute |
||
| In JetBrains TeamCity version before 2022.10, Password parameters could be exposed in the build log if they contained special characters | 7.5 |
Haute |
||
| In JetBrains TeamCity version before 2022.10, no audit items were added upon editing a user's settings | 5.3 |
Moyen |
||
| In JetBrains TeamCity before 2022.04.4 environmental variables of "password" type could be logged when using custom Perforce executable | 5.3 |
Moyen |
||
| In JetBrains TeamCity before 2022.04.3 the private SSH key could be written to the server log in some cases | 5.3 |
Moyen |
||
| In JetBrains TeamCity before 2022.04.2 build parameter injection was possible | 8.8 |
Haute |
||
| In JetBrains TeamCity before 2022.04.2 the private SSH key could be written to the build log in some cases | 6.5 |
Moyen |
||
| In JetBrains TeamCity before 2022.04 potential XSS via Referrer header was possible | 6.1 |
Moyen |
||
| In JetBrains TeamCity before 2022.04 leak of secrets in TeamCity agent logs was possible | 4.9 |
Moyen |
||
| In JetBrains TeamCity before 2022.04 reflected XSS on the Build Chain Status page was possible | 6.1 |
Moyen |
||
| JetBrains TeamCity before 2021.2.2 was vulnerable to reflected XSS. | 6.1 |
Moyen |
||
| JetBrains TeamCity before 2021.2.3 was vulnerable to OS command injection in the Agent Push feature configuration. | 9.8 |
Critique |
||
| In JetBrains TeamCity before 2021.2.3, environment variables of the "password" type could be logged in some cases. | 7.5 |
Haute |
||
| In JetBrains TeamCity before 2021.2.1, URL injection leading to CSRF was possible. | 8.8 |
Haute |
||
| In JetBrains TeamCity before 2021.2.1, editing a user account to change its password didn't terminate sessions of the edited user. | 7.5 |
Haute |
||
| In JetBrains TeamCity before 2021.2.1, XXE during the parsing of the configuration file was possible. | 9.8 |
Critique |
||
| JetBrains TeamCity before 2021.2.1 was vulnerable to stored XSS. | 5.4 |
Moyen |
||
| JetBrains TeamCity before 2021.2.1 was vulnerable to reflected XSS. | 6.1 |
Moyen |
||
| In JetBrains TeamCity before 2021.2, health items of pull requests were shown to users who lacked appropriate permissions. | 6.5 |
Moyen |
||
| In JetBrains TeamCity before 2021.2.1, an unauthenticated attacker can cancel running builds via an XML-RPC request to the TeamCity server. | 5.3 |
Moyen |
||
| JetBrains TeamCity before 2021.2 was vulnerable to a Time-of-check/Time-of-use (TOCTOU) race-condition attack in agent registration via XML-RPC. | 8.1 |
Haute |
||
| In JetBrains TeamCity before 2021.2.1, the Agent Push feature allowed selection of any private key on the server. | 5.3 |
Moyen |
||
| In JetBrains TeamCity before 2021.2, blind SSRF via an XML-RPC call was possible. | 6.5 |
Moyen |
||
| In JetBrains TeamCity before 2021.2, a logout action didn't remove a Remember Me cookie. | 5.3 |
Moyen |
||
| In JetBrains TeamCity before 2021.1.4, GitLab authentication impersonation was possible. | 9.8 |
Critique |
||
| In JetBrains TeamCity before 2021.2.1, a redirection to an external site was possible. | 6.1 |
Moyen |
||
| In JetBrains TeamCity before 2021.1.3, the X-Frame-Options header is missing in some cases. | 9.8 |
Critique |
||
| In JetBrains TeamCity before 2021.1.2, user enumeration was possible. | 5.3 |
Moyen |
||
| In JetBrains TeamCity before 2021.1.2, remote code execution via the agent push functionality is possible. | 9.8 |
Critique |
||
| In JetBrains TeamCity before 2021.1, information disclosure via the Docker Registry connection dialog is possible. | 7.5 |
Haute |
||
| In JetBrains TeamCity before 2021.1.2, some HTTP security headers were missing. | 5.3 |
Moyen |
||
| In JetBrains TeamCity before 2021.1.2, email notifications could include unescaped HTML for XSS. | 6.1 |
Moyen |
||
| In JetBrains TeamCity before 2021.1.2, permission checks in the Create Patch functionality are insufficient. | 5.3 |
Moyen |
||
| In JetBrains TeamCity before 2021.1.2, stored XSS is possible. | 5.4 |
Moyen |
||
| In JetBrains TeamCity before 2021.1.2, permission checks in the Agent Push functionality were insufficient. | 9.8 |
Critique |
||
| In JetBrains TeamCity before 2021.1.3, a newly created project could take settings from an already deleted project. | 5.3 |
Moyen |
||
| In JetBrains TeamCity before 2021.1, passwords in cleartext sometimes could be stored in VCS. | 7.5 |
Haute |
||
| In JetBrains TeamCity before 2020.2.4, insufficient checks during file uploading were made. | 5.3 |
Moyen |
||
| In JetBrains TeamCity before 2021.1, an insecure key generation mechanism for encrypted properties was used. | 5.3 |
Moyen |
||
| In JetBrains TeamCity before 2021.1.1, insufficient authentication checks for agent requests were made. | 7.5 |
Haute |
||
| In JetBrains TeamCity before 2020.2.4, there was an insecure deserialization. | 9.8 |
Critique |
||
| In JetBrains TeamCity before 2020.2.3, XSS was possible. | 6.1 |
Moyen |
||
| In JetBrains TeamCity before 2020.2.4, OS command injection leading to remote code execution was possible. | 9.8 |
Critique |
||
| In JetBrains TeamCity before 2020.2.4 on Windows, arbitrary code execution on TeamCity Server was possible. | 9.8 |
Critique |
||
| In JetBrains TeamCity before 2020.2.3, insufficient checks of the redirect_uri were made during GitHub SSO token exchange. | 7.5 |
Haute |
||
| In JetBrains TeamCity before 2020.2.3, account takeover was potentially possible during a password reset. | 8.8 |
Haute |
||
| In JetBrains TeamCity before 2020.2.3, reflected XSS was possible on several pages. | 6.1 |
Moyen |
||
| In JetBrains TeamCity before 2020.2.3, information disclosure via SSRF was possible. | 7.5 |
Haute |
||
| In JetBrains TeamCity before 2020.2.3, stored XSS was possible on several pages. | 5.4 |
Moyen |
||
| In JetBrains TeamCity before 2020.2.3, argument injection leading to remote code execution was possible. | 9.8 |
Critique |
||
| In JetBrains TeamCity before 2020.2.2, stored XSS on a tests page was possible. | 5.4 |
Moyen |
||
| In JetBrains TeamCity before 2020.2.2, permission checks for changing TeamCity plugins were implemented improperly. | 5.3 |
Moyen |
||
| In JetBrains TeamCity before 2020.2.2, audit logs were not sufficient when an administrator uploaded a file. | 2.7 |
Bas |
||
| In JetBrains TeamCity before 2020.2.2, XSS was potentially possible on the test history page. | 6.1 |
Moyen |
||
| JetBrains TeamCity Plugin before 2020.2.85695 SSRF. Vulnerability that could potentially expose user credentials. | 7.5 |
Haute |
||
| In JetBrains TeamCity before 2020.2.1, permissions during token removal were checked improperly. | 5.3 |
Moyen |
||
| In JetBrains TeamCity before 2020.2.1, permissions during user deletion were checked improperly. | 5.3 |
Moyen |
||
| In JetBrains TeamCity before 2020.2.1, the server admin could create and see access tokens for any other users. | 3.8 |
Bas |
||
| In JetBrains TeamCity before 2020.2.1, a user could get access to the GitHub access token of another user. | 4.3 |
Moyen |
||
| In JetBrains TeamCity before 2020.2, an ECR token could be exposed in a build's parameters. | 7.5 |
Haute |
||
| In JetBrains TeamCity before 2020.2.2, TeamCity server DoS was possible via server integration. | 5.3 |
Moyen |
||
| JetBrains TeamCity before 2020.2 was vulnerable to reflected XSS on several pages. | 6.1 |
Moyen |
||
| JetBrains TeamCity before 2020.1.2 was vulnerable to URL injection. | 6.1 |
Moyen |
||
| In JetBrains TeamCity before 2020.1.5, the Guest user had access to audit records. | 4.3 |
Moyen |
||
| In JetBrains TeamCity before 2020.1.5, secure dependency parameters could be not masked in depending builds when there are no internal artifacts. | 5.3 |
Moyen |
||
| JetBrains TeamCity before 2019.2.3 is vulnerable to stored XSS in the administration UI. | 6.1 |
Moyen |
||
| JetBrains TeamCity before 2019.2.3 is vulnerable to reflected XSS in the administration UI. | 6.1 |
Moyen |
||
| In JetBrains TeamCity before 2020.1.1, project parameter values can be retrieved by a user without appropriate permissions. | 6.5 |
Moyen |
||
| In JetBrains TeamCity before 2019.2.3, password parameters could be disclosed via build logs. | 5.3 |
Moyen |
||
| In JetBrains TeamCity before 2020.1, users with the Modify Group permission can elevate other users' privileges. | 8.8 |
Haute |
||
| In JetBrains TeamCity before 2020.1, users are able to assign more permissions than they have. | 4.3 |
Moyen |
||
| In JetBrains TeamCity before 2019.2.1, a user without appropriate permissions was able to import settings from the settings.kts file. | 6.5 |
Moyen |
||
| In JetBrains TeamCity before 2019.2.1, the application state is kept alive after a user ends his session. | 7.5 |
Haute |
||
| In JetBrains TeamCity before 2019.2.2, password values were shown in an unmasked format on several pages. | 7.5 |
Haute |
||
| In JetBrains TeamCity before 2019.1.4, a project administrator was able to retrieve some TeamCity server settings. | 2.7 |
Bas |
||
| In JetBrains TeamCity before 2019.2, several user-level pages were vulnerable to XSS. | 6.1 |
Moyen |
||
| JetBrains TeamCity before 2019.2 was vulnerable to a stored XSS attack by a user with the developer role. | 5.4 |
Moyen |
||
| In JetBrains TeamCity before 2019.1.5, some server-stored passwords could be shown via the web UI. | 7.5 |
Haute |
||
| In JetBrains TeamCity before 2019.1.5, reverse tabnabbing was possible on several pages. | 4.3 |
Moyen |
||
| In JetBrains TeamCity before 2019.1.2, a non-destructive operation could be performed by a user without the corresponding permissions. | 5.3 |
Moyen |
||
| In JetBrains TeamCity before 2019.1.2, secure values could be exposed to users with the "View build runtime parameters and data" permission. | 5.3 |
Moyen |
||
| In JetBrains TeamCity before 2019.1.4, reverse tabnabbing was possible on several pages. | 4.3 |
Moyen |
||
| In JetBrains TeamCity before 2019.1.4, insecure Java Deserialization could potentially allow remote code execution. | 9.8 |
Critique |
||
| In JetBrains TeamCity before 2019.1.2, access could be gained to the history of builds of a deleted build configuration under some circumstances. | 5.3 |
Moyen |
||
| In JetBrains UpSource versions before 2018.2 build 1293, there is credential disclosure via RPC commands. | 9.8 |
Critique |
||
| A user without the required permissions could gain access to some JetBrains TeamCity settings. The issue was fixed in TeamCity 2018.2.2. | 4.3 |
Moyen |
||
| 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. | 6.1 |
Moyen |
||
| Incorrect handling of user input in ZIP extraction was detected in JetBrains TeamCity. The issue was fixed in TeamCity 2018.2.2. | 7.5 |
Haute |
||
| A possible stored JavaScript injection requiring a deliberate server administrator action was detected. The issue was fixed in JetBrains TeamCity 2018.2.3. | 6.1 |
Moyen |
||
| The generated Kotlin DSL settings allowed usage of an unencrypted connection for resolving artifacts. The issue was fixed in JetBrains TeamCity 2018.2.3. | 5.3 |
Moyen |
||
| A possible stored JavaScript injection was detected on one of the JetBrains TeamCity pages. The issue was fixed in TeamCity 2018.2.3. | 6.1 |
Moyen |
2025©
tesweb SA
