threat
engine
.sh
Back
·
··:··
Home
/
Product
/
jetbrains teamcity
Product
jetbrains teamcity
258 known vulnerabilities across versions
Vulnerabilities are listed by affected version. Select any CVE for the full briefing and its intelligence graph.
Sort
Newest first
Oldest first
Highest CVSS
Lowest CVSS
Min CVSS
Any
4.0+
7.0+ (High)
9.0+ (Critical)
Published since
Reset
CVE-2026-44413
< 2025.11.5
In JetBrains TeamCity before 2026.1 2025.11.5 authenticated users could expose server API to unauthorised access
8.2
HIGH
CVE-2026-28196
< 2025.11.3
In JetBrains TeamCity before 2025.11.3 disabling versioned settings left a credentials config on disk
2.3
LOW
CVE-2026-28195
< 2025.11.3
In JetBrains TeamCity before 2025.11.3 missing authorization allowed project developers to add parameters to build configurations
4.3
MEDIUM
CVE-2026-28194
< 2025.11.3
In JetBrains TeamCity before 2025.11.3 open redirect was possible in the React project creation flow
4.3
MEDIUM
CVE-2025-68268
< 2025.11.1
In JetBrains TeamCity before 2025.11.1 reflected XSS was possible on the storage settings page
5.4
MEDIUM
CVE-2025-68267
< 2025.11.1
In JetBrains TeamCity before 2025.11.1 excessive privileges were possible due to storing GitHub personal access token instead of a
6.5
MEDIUM
CVE-2025-68166
< 2025.11
In JetBrains TeamCity before 2025.11 a DOM-based XSS was possible on the OAuth connections tab
5.4
MEDIUM
CVE-2025-68165
< 2025.11
In JetBrains TeamCity before 2025.11 reflected XSS was possible on VCS Root setup
5.4
MEDIUM
CVE-2025-68164
< 2025.11
In JetBrains TeamCity before 2025.11 port enumeration was possible via the Perforce connection test
2.7
LOW
CVE-2025-68163
< 2025.11
In JetBrains TeamCity before 2025.11 stored XSS was possible on agentpushInstall page
3.5
LOW
CVE-2025-68162
< 2025.11
In JetBrains TeamCity before 2025.11 maven embedder allowed loading extensions via project configuration
2.7
LOW
CVE-2025-67742
< 2025.11
In JetBrains TeamCity before 2025.11 path traversal was possible via file upload
3.8
LOW
CVE-2025-67741
< 2025.11
In JetBrains TeamCity before 2025.11 stored XSS was possible via session attribute
4.6
MEDIUM
CVE-2025-67740
< 2025.11
In JetBrains TeamCity before 2025.11 improper access control could expose GitHub App token's metadata
2.7
LOW
CVE-2025-67739
< 2025.11.2
In JetBrains TeamCity before 2025.11.2 improper repository URL validation could lead to local paths disclosure
3.1
LOW
CVE-2025-59457
< 2025.07.2
In JetBrains TeamCity before 2025.07.2 missing Git URL validation allowed credential leakage on Windows
7.7
HIGH
CVE-2025-59456
< 2025.07.2
In JetBrains TeamCity before 2025.07.2 path traversal was possible during project archive upload
5.5
MEDIUM
CVE-2025-59455
< 2025.07.2
In JetBrains TeamCity before 2025.07.2 project isolation bypass was possible due to race condition
4.2
MEDIUM
CVE-2025-57734
< 2025.07.1
In JetBrains TeamCity before 2025.07.1 aWS credentials were exposed in Docker script files
4.3
MEDIUM
CVE-2025-57733
< 2025.07.1
In JetBrains TeamCity before 2025.07.1 sMTP injection was possible allowing modification of email content
5.5
MEDIUM
CVE-2025-57732
< 2025.07.1
In JetBrains TeamCity before 2025.07.1 privilege escalation was possible due to incorrect directory ownership
7.5
HIGH
CVE-2025-54538
< 2025.07
In JetBrains TeamCity before 2025.07 password exposure was possible via command line in the "hg pull" command
5.5
MEDIUM
CVE-2025-54537
< 2025.07
In JetBrains TeamCity before 2025.07 user credentials were stored in plain text in memory snapshots
5.5
MEDIUM
CVE-2025-54536
< 2025.07
In JetBrains TeamCity before 2025.07 a CSRF was possible on GraphQL endpoint
5.4
MEDIUM
CVE-2025-54535
< 2025.07
In JetBrains TeamCity before 2025.07 password reset and email verification tokens were using weak hashing algorithms
5.8
MEDIUM
CVE-2025-54534
< 2025.07
In JetBrains TeamCity before 2025.07 reflected XSS was possible on the agentpushPreset page
4.8
MEDIUM
CVE-2025-54533
< 2025.07
In JetBrains TeamCity before 2025.07 improper access control allowed disclosure of build settings via VCS configuration
4.3
MEDIUM
CVE-2025-54532
< 2025.07
In JetBrains TeamCity before 2025.07 improper access control allowed disclosure of build settings via snapshot dependencies
4.3
MEDIUM
CVE-2025-54531
< 2025.07
In JetBrains TeamCity before 2025.07 path traversal was possible via plugin unpacking on Windows
7.7
HIGH
CVE-2025-54530
< 2025.07
In JetBrains TeamCity before 2025.07 privilege escalation was possible due to incorrect directory permissions
7.5
HIGH
CVE-2025-54529
< 2025.07
In JetBrains TeamCity before 2025.07 a CSRF was possible in external OAuth login integration
3.7
LOW
CVE-2025-54528
< 2025.07
In JetBrains TeamCity before 2025.07 a CSRF was possible in GitHub App connection flow
5.4
MEDIUM
CVE-2025-52879
< 2025.03.3
In JetBrains TeamCity before 2025.03.3 reflected XSS in the NPM Registry integration was possible
4.8
MEDIUM
CVE-2025-52878
< 2025.03.3
In JetBrains TeamCity before 2025.03.3 usernames were exposed to the users without proper permissions
4.3
MEDIUM
CVE-2025-52877
< 2025.03.3
In JetBrains TeamCity before 2025.03.3 reflected XSS on diskUsageBuildsStats page was possible
4.8
MEDIUM
CVE-2025-52876
< 2025.03.3
In JetBrains TeamCity before 2025.03.3 reflected XSS on the favoriteIcon page was possible
5.4
MEDIUM
CVE-2025-52875
< 2025.03.3
In JetBrains TeamCity before 2025.03.3 a DOM-based XSS at the Performance Monitor page was possible
5.4
MEDIUM
CVE-2025-47854
< 2025.03.2
In JetBrains TeamCity before 2025.03.2 open redirect was possible on editing VCS Root page
4.3
MEDIUM
CVE-2025-47853
< 2025.03.2
In JetBrains TeamCity before 2025.03.2 stored XSS via Jira integration was possible
4.8
MEDIUM
CVE-2025-47852
< 2025.03.2
In JetBrains TeamCity before 2025.03.2 stored XSS via YouTrack integration was possible
4.8
MEDIUM
CVE-2025-47851
< 2025.03.2
In JetBrains TeamCity before 2025.03.2 stored XSS via GitHub Checks Webhook was possible
4.8
MEDIUM
CVE-2025-46618
< 2025.03.1
In JetBrains TeamCity before 2025.03.1 stored XSS was possible on Data Directory tab
3.5
LOW
CVE-2025-46433
< 2025.03.1
In JetBrains TeamCity before 2025.03.1 improper path validation in loggingPreset parameter was possible
4.9
MEDIUM
CVE-2025-46432
< 2025.03.1
In JetBrains TeamCity before 2025.03.1 base64-encoded credentials could be exposed in build logs
4.3
MEDIUM
CVE-2025-31141
< 2025.03
In JetBrains TeamCity before 2025.03 exception could lead to credential leakage on Cloud Profiles page
2.7
LOW
CVE-2025-31140
< 2025.03
In JetBrains TeamCity before 2025.03 stored XSS was possible on Cloud Profiles page
4.6
MEDIUM
CVE-2025-31139
< 2025.03
In JetBrains TeamCity before 2025.03 base64 encoded password could be exposed in build log
4.3
MEDIUM
CVE-2025-26493
< 2024.12.2
In JetBrains TeamCity before 2024.12.2 several DOM-based XSS were possible on the Code Inspection Report tab
4.6
MEDIUM
CVE-2025-26492
< 2024.12.2
In JetBrains TeamCity before 2024.12.2 improper Kubernetes connection settings could expose sensitive resources
7.7
HIGH
CVE-2025-24461
all versions
In JetBrains TeamCity before 2024.12.1 decryption of connection secrets without proper permissions was possible via Test Connectio
6.5
MEDIUM
CVE-2025-24460
< 2024.12.1
In JetBrains TeamCity before 2024.12.1 improper access control allowed to see Projects’ names in the agent pool
4.3
MEDIUM
CVE-2025-24459
< 2024.12.1
In JetBrains TeamCity before 2024.12.1 reflected XSS was possible on the Vault Connection page
4.6
MEDIUM
CVE-2024-56356
< 2024.12
In JetBrains TeamCity before 2024.12 insecure XMLParser configuration could lead to potential XXE attack
5.9
MEDIUM
CVE-2024-56355
< 2024.12
In JetBrains TeamCity before 2024.12 missing Content-Type header in RemoteBuildLogController response could lead to XSS
4.6
MEDIUM
CVE-2024-56354
< 2024.12
In JetBrains TeamCity before 2024.12 password field value were accessible to users with view settings permission
5.5
MEDIUM
CVE-2024-56353
< 2024.12
In JetBrains TeamCity before 2024.12 backup file exposed user credentials and session cookies
5.5
MEDIUM
CVE-2024-56352
< 2024.12
In JetBrains TeamCity before 2024.12 stored XSS was possible via image name on the agent details page
4.6
MEDIUM
CVE-2024-56351
< 2024.12
In JetBrains TeamCity before 2024.12 access tokens were not revoked after removing user roles
6.3
MEDIUM
CVE-2024-56350
< 2024.12
In JetBrains TeamCity before 2024.12 build credentials allowed unauthorized viewing of projects
4.3
MEDIUM
CVE-2024-56349
< 2024.12
In JetBrains TeamCity before 2024.12 improper access control allowed unauthorized users to modify build logs
5.3
MEDIUM
CVE-2024-56348
< 2024.12
In JetBrains TeamCity before 2024.12 improper access control allowed viewing details of unauthorized agents
4.3
MEDIUM
CVE-2024-47951
< 2024.07.3
In JetBrains TeamCity before 2024.07.3 stored XSS was possible via server global settings
3.5
LOW
CVE-2024-47950
< 2024.07.03
In JetBrains TeamCity before 2024.07.3 stored XSS was possible in Backup configuration settings
3.5
LOW
CVE-2024-47949
< 2024.07.3
In JetBrains TeamCity before 2024.07.3 path traversal allowed backup file write to arbitrary location
4.9
MEDIUM
CVE-2024-47948
< 2024.07.3
In JetBrains TeamCity before 2024.07.3 path traversal leading to information disclosure was possible via server backups
4.9
MEDIUM
CVE-2024-47161
< 2024.07.3
In JetBrains TeamCity before 2024.07.3 password could be exposed via Sonar runner REST API
4.3
MEDIUM
CVE-2024-43810
< 2024.07.1
In JetBrains TeamCity before 2024.07.1 reflected XSS was possible in the AWS Core plugin
4.6
MEDIUM
CVE-2024-43809
< 2024.07.1
In JetBrains TeamCity before 2024.07.1 reflected XSS was possible on the agentPushPreset page
3.5
LOW
CVE-2024-43808
< 2024.07.1
In JetBrains TeamCity before 2024.07.1 self XSS was possible in the HashiCorp Vault plugin
3.7
LOW
CVE-2024-43807
< 2024.07.1
In JetBrains TeamCity before 2024.07.1 multiple stored XSS was possible on Clouds page
4.6
MEDIUM
CVE-2024-43114
< 2024.07.1
In JetBrains TeamCity before 2024.07.1 possible privilege escalation due to incorrect directory permissions
7.5
HIGH
CVE-2024-41829
< 2024.07
In JetBrains TeamCity before 2024.07 an OAuth code for JetBrains Space could be stolen via Space Application connection
3.5
LOW
CVE-2024-41828
< 2024.07
In JetBrains TeamCity before 2024.07 comparison of authorization tokens took non-constant time
2.6
LOW
CVE-2024-41827
< 2024.07
In JetBrains TeamCity before 2024.07 access tokens could continue working after deletion or expiration
7.4
HIGH
CVE-2024-41826
< 2024.07
In JetBrains TeamCity before 2024.07 stored XSS was possible on Show Connection page
3.5
LOW
CVE-2024-41825
< 2024.07
In JetBrains TeamCity before 2024.07 stored XSS was possible on the Code Inspection tab
4.6
MEDIUM
CVE-2024-41824
< 2024.07
In JetBrains TeamCity before 2024.07 parameters of the "password" type could leak into the build log in some specific cases
6.4
MEDIUM
CVE-2024-39879
< 2024.03.3
In JetBrains TeamCity before 2024.03.3 application token could be exposed in EC2 Cloud Profile settings
5.0
MEDIUM
CVE-2024-39878
< 2024.03.3
In JetBrains TeamCity before 2024.03.3 private key could be exposed via testing GitHub App Connection
4.1
MEDIUM
CVE-2024-36470
< 2022.04.7
In JetBrains TeamCity before 2022.04.7, 2022.10.6, 2023.05.6, 2023.11.5 authentication bypass was possible in specific edge cases
8.1
HIGH
CVE-2024-36378
< 2024.03.2
In JetBrains TeamCity before 2024.03.2 server was susceptible to DoS attacks with incorrect auth tokens
5.9
MEDIUM
CVE-2024-36377
< 2024.03.2
In JetBrains TeamCity before 2024.03.2 certain TeamCity API endpoints did not check user permissions
6.5
MEDIUM
CVE-2024-36376
< 2024.03.2
In JetBrains TeamCity before 2024.03.2 users could perform actions that should not be available to them based on their permissions
6.5
MEDIUM
CVE-2024-36375
< 2024.03.2
In JetBrains TeamCity before 2024.03.2 technical information regarding TeamCity server could be exposed
5.3
MEDIUM
CVE-2024-36374
< 2024.03.2
In JetBrains TeamCity before 2024.03.2 stored XSS via build step settings was possible
4.6
MEDIUM
CVE-2024-36373
< 2024.03.2
In JetBrains TeamCity before 2024.03.2 several stored XSS in untrusted builds settings were possible
4.6
MEDIUM
CVE-2024-36372
< 2023.05.6
In JetBrains TeamCity before 2023.05.6 reflected XSS on the subscriptions page was possible
4.6
MEDIUM
CVE-2024-36371
< 2023.05.6
In JetBrains TeamCity before 2023.05.6, 2023.11.5 stored XSS in Commit status publisher was possible
4.6
MEDIUM
CVE-2024-36370
< 2022.04.7
In JetBrains TeamCity before 2022.04.7, 2022.10.6, 2023.05.6, 2023.11.5 stored XSS via OAuth connection settings was possible
4.6
MEDIUM
CVE-2024-36369
< 2022.04.7
In JetBrains TeamCity before 2022.04.7, 2022.10.6, 2023.05.6, 2023.11.5 stored XSS via issue tracker integration was possible
4.6
MEDIUM
CVE-2024-36368
< 2022.04.7
In JetBrains TeamCity before 2022.04.7, 2022.10.6, 2023.05.6, 2023.11.5 reflected XSS via OAuth provider configuration was possibl
4.6
MEDIUM
CVE-2024-36367
< 2022.04.7
In JetBrains TeamCity before 2022.04.7, 2022.10.6, 2023.05.6, 2023.11.5 stored XSS via third-party reports was possible
4.6
MEDIUM
CVE-2024-36366
< 2022.04.7
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 f
5.4
MEDIUM
CVE-2024-36365
< 2022.04.7
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 a
6.8
MEDIUM
CVE-2024-36364
< 2022.04.7
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
6.5
MEDIUM
CVE-2024-36363
< 2022.04.7
In JetBrains TeamCity before 2022.04.7, 2022.10.6, 2023.05.6, 2023.11.5 several Stored XSS in code inspection reports were possibl
4.6
MEDIUM
CVE-2024-36362
< 2022.04.7
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 serv
6.5
MEDIUM
CVE-2024-35302
< 2023.11
In JetBrains TeamCity before 2023.11 stored XSS during restore from backup was possible
5.4
MEDIUM
CVE-2024-35301
< 2024.03.1
In JetBrains TeamCity before 2024.03.1 commit status publisher didn't check project scope of the GitHub App token
5.5
MEDIUM
CVE-2024-35300
all versions
In JetBrains TeamCity between 2024.03 and 2024.03.1 several stored XSS in the available updates page were possible
3.5
LOW
CVE-2024-31140
< 2024.03
In JetBrains TeamCity before 2024.03 server administrators could remove arbitrary files from the server by installing tools
4.1
MEDIUM
CVE-2024-31139
< 2024.03
In JetBrains TeamCity before 2024.03 xXE was possible in the Maven build steps detector
5.9
MEDIUM
CVE-2024-31138
< 2024.03
In JetBrains TeamCity before 2024.03 xSS was possible via Agent Distribution settings
4.6
MEDIUM
CVE-2024-31137
< 2024.03
In JetBrains TeamCity before 2024.03 reflected XSS was possible via Space connection configuration
6.8
MEDIUM
CVE-2024-31136
< 2024.03
In JetBrains TeamCity before 2024.03 2FA could be bypassed by providing a special URL parameter
7.4
HIGH
CVE-2024-31135
< 2024.03
In JetBrains TeamCity before 2024.03 open redirect was possible on the login page
6.1
MEDIUM
CVE-2024-31134
< 2024.03
In JetBrains TeamCity before 2024.03 authenticated users without administrative permissions could register other users when self-r
6.5
MEDIUM
CVE-2024-29880
< 2023.11
In JetBrains TeamCity before 2023.11 users with access to the agent machine might obtain permissions of the user running the agent
4.2
MEDIUM
CVE-2024-28174
< 2023.11.4
In JetBrains TeamCity before 2023.11.4 presigned URL generation requests in S3 Artifact Storage plugin were authorized improperly
5.8
MEDIUM
CVE-2024-28173
>= 2023.11 and < 2023.11.4
In JetBrains TeamCity between 2023.11 and 2023.11.4 custom build parameters of the "password" type could be disclosed
4.3
MEDIUM
CVE-2024-27199
< 2023.11.4
In JetBrains TeamCity before 2023.11.4 path traversal allowing to perform limited admin actions was possible
7.3
HIGH
CVE-2024-27198
< 2023.11.4
In JetBrains TeamCity before 2023.11.4 authentication bypass allowing to perform admin actions was possible
9.8
CRITICAL
CVE-2024-24942
< 2023.11.3
In JetBrains TeamCity before 2023.11.3 path traversal allowed reading data within JAR archives
5.3
MEDIUM
CVE-2024-24938
< 2023.11.2
In JetBrains TeamCity before 2023.11.2 limited directory traversal was possible in the Kotlin DSL documentation
5.3
MEDIUM
CVE-2024-24937
< 2023.11.2
In JetBrains TeamCity before 2023.11.2 stored XSS via agent distribution was possible
4.6
MEDIUM
CVE-2024-24936
< 2023.11.2
In JetBrains TeamCity before 2023.11.2 access control at the S3 Artifact Storage plugin endpoint was missed
4.3
MEDIUM
CVE-2024-23917
< 2023.11.3
In JetBrains TeamCity before 2023.11.3 authentication bypass leading to RCE was possible
9.8
CRITICAL
CVE-2023-50870
< 2023.11.1
In JetBrains TeamCity before 2023.11.1 a CSRF on login was possible
4.3
MEDIUM
CVE-2023-43566
< 2023.05.4
In JetBrains TeamCity before 2023.05.4 stored XSS was possible during nodes configuration
3.5
LOW
CVE-2023-42793
< 2023.05.4
In JetBrains TeamCity before 2023.05.4 authentication bypass leading to RCE on TeamCity Server was possible
9.8
CRITICAL
CVE-2023-41250
< 2023.05.3
In JetBrains TeamCity before 2023.05.3 reflected XSS was possible during user registration
3.5
LOW
CVE-2023-41249
< 2023.05.3
In JetBrains TeamCity before 2023.05.3 reflected XSS was possible during copying Build Step
4.6
MEDIUM
CVE-2023-41248
< 2023.05.3
In JetBrains TeamCity before 2023.05.3 stored XSS was possible during Cloud Profiles configuration
4.6
MEDIUM
CVE-2023-39175
< 2023.05.2
In JetBrains TeamCity before 2023.05.2 reflected XSS via GitHub integration was possible
4.6
MEDIUM
CVE-2023-39174
< 2023.05.2
In JetBrains TeamCity before 2023.05.2 a ReDoS attack was possible via integration with issue trackers
4.3
MEDIUM
CVE-2023-39173
< 2023.05.2
In JetBrains TeamCity before 2023.05.2 a token with limited permissions could be used to gain full account access
5.4
MEDIUM
CVE-2023-38067
< 2023.05.1
In JetBrains TeamCity before 2023.05.1 build parameters of the "password" type could be written to the agent log
4.3
MEDIUM
CVE-2023-38066
< 2023.05.1
In JetBrains TeamCity before 2023.05.1 reflected XSS via the Referer header was possible during artifact downloads
4.6
MEDIUM
CVE-2023-38065
< 2023.05.1
In JetBrains TeamCity before 2023.05.1 stored XSS while viewing the build log was possible
4.6
MEDIUM
CVE-2023-38064
< 2023.05.1
In JetBrains TeamCity before 2023.05.1 build chain parameters of the "password" type could be written to the agent log
4.3
MEDIUM
CVE-2023-38063
< 2023.05.1
In JetBrains TeamCity before 2023.05.1 stored XSS while running custom builds was possible
4.6
MEDIUM
CVE-2023-38062
< 2023.05.1
In JetBrains TeamCity before 2023.05.1 parameters of the "password" type could be shown in the UI in certain composite build confi
4.3
MEDIUM
CVE-2023-38061
< 2023.05.1
In JetBrains TeamCity before 2023.05.1 stored XSS when using a custom theme was possible
4.6
MEDIUM
CVE-2015-1313
>= 8.0 and < 9.0.2
JetBrains TeamCity 8 and 9 before 9.0.2 allows bypass of account-creation restrictions via a crafted request because the required
6.5
MEDIUM
CVE-2023-34229
< 2023.05
In JetBrains TeamCity before 2023.05 stored XSS in GitLab Connection page was possible
4.6
MEDIUM
CVE-2023-34228
< 2023.05
In JetBrains TeamCity before 2023.05 authentication checks were missing - 2FA was not checked for some sensitive account actions
5.3
MEDIUM
CVE-2023-34227
< 2023.05
In JetBrains TeamCity before 2023.05 a specific endpoint was vulnerable to brute force attacks
5.3
MEDIUM
CVE-2023-34226
< 2023.05
In JetBrains TeamCity before 2023.05 reflected XSS in the Subscriptions page was possible
4.6
MEDIUM
CVE-2023-34225
< 2023.05
In JetBrains TeamCity before 2023.05 stored XSS in the NuGet feed page was possible
4.6
MEDIUM
CVE-2023-34224
< 2023.05
In JetBrains TeamCity before 2023.05 open redirect during oAuth configuration was possible
4.8
MEDIUM
CVE-2023-34223
< 2023.05
In JetBrains TeamCity before 2023.05 parameters of the "password" type from build dependencies could be logged in some cases
4.3
MEDIUM
CVE-2023-34222
< 2023.05
In JetBrains TeamCity before 2023.05 possible XSS in the Plugin Vendor URL was possible
4.6
MEDIUM
CVE-2023-34221
< 2023.05
In JetBrains TeamCity before 2023.05 stored XSS in the Show Connection page was possible
4.6
MEDIUM
CVE-2023-34220
< 2023.05
In JetBrains TeamCity before 2023.05 stored XSS in the Commit Status Publisher window was possible
4.6
MEDIUM
CVE-2023-34219
< 2023.05
In JetBrains TeamCity before 2023.05 improper permission checks allowed users without appropriate permissions to edit Build Config
4.3
MEDIUM
CVE-2023-34218
< 2023.05
In JetBrains TeamCity before 2023.05 bypass of permission checks allowing to perform admin actions was possible
9.1
CRITICAL
CVE-2022-48428
< 2022.10.3
In JetBrains TeamCity before 2022.10.3 stored XSS on the SSH keys page was possible
4.6
MEDIUM
CVE-2022-48427
< 2022.10.3
In JetBrains TeamCity before 2022.10.3 stored XSS on “Pending changes” and “Changes” tabs was possible
4.6
MEDIUM
CVE-2022-48426
all versions
In JetBrains TeamCity before 2022.10.3 stored XSS in Perforce connection settings was possible
4.6
MEDIUM
CVE-2022-48344
< 2022.10.2
In JetBrains TeamCity before 2022.10.2 there was an XSS vulnerability in the group creation process.
5.4
MEDIUM
CVE-2022-48343
< 2022.10.2
In JetBrains TeamCity before 2022.10.2 there was an XSS vulnerability in the user creation process.
5.4
MEDIUM
CVE-2022-48342
< 2022.10.2
In JetBrains TeamCity before 2022.10.2 jVMTI was enabled by default on agents.
5.2
MEDIUM
CVE-2022-46831
>= 2022.10 and <= 2022.10.1
In JetBrains TeamCity between 2022.10 and 2022.10.1 connecting to AWS using the "Default Credential Provider Chain" allowed TeamCi
6.6
MEDIUM
CVE-2022-46830
>= 2022.10 and <= 2022.10.1
In JetBrains TeamCity between 2022.10 and 2022.10.1 a custom STS endpoint allowed internal port scanning.
4.1
MEDIUM
CVE-2022-44646
< 2022.10
In JetBrains TeamCity version before 2022.10, no audit items were added upon editing a user's settings
2.2
LOW
CVE-2022-44624
< 2022.10
In JetBrains TeamCity version before 2022.10, Password parameters could be exposed in the build log if they contained special char
6.5
MEDIUM
CVE-2022-44623
< 2022.10
In JetBrains TeamCity version before 2022.10, Project Viewer could see scrambled secure values in the MetaRunner settings
6.5
MEDIUM
CVE-2022-44622
>= 2021.2 and < 2022.10
In JetBrains TeamCity version between 2021.2 and 2022.10 access permissions for secure token health items were excessive
2.7
LOW
CVE-2022-40979
< 2022.04.4
In JetBrains TeamCity before 2022.04.4 environmental variables of "password" type could be logged when using custom Perforce execu
4.4
MEDIUM
CVE-2022-38133
< 2022.04.3
In JetBrains TeamCity before 2022.04.3 the private SSH key could be written to the server log in some cases
3.2
LOW
CVE-2022-36322
< 2022.04.2
In JetBrains TeamCity before 2022.04.2 build parameter injection was possible
5.4
MEDIUM
CVE-2022-36321
< 2022.04.2
In JetBrains TeamCity before 2022.04.2 the private SSH key could be written to the build log in some cases
4.1
MEDIUM
CVE-2022-29929
< 2022.04
In JetBrains TeamCity before 2022.04 potential XSS via Referrer header was possible
3.7
LOW
CVE-2022-29928
< 2022.04
In JetBrains TeamCity before 2022.04 leak of secrets in TeamCity agent logs was possible
4.4
MEDIUM
CVE-2022-29927
< 2022.04
In JetBrains TeamCity before 2022.04 reflected XSS on the Build Chain Status page was possible
4.6
MEDIUM
CVE-2022-25264
< 2021.2.3
In JetBrains TeamCity before 2021.2.3, environment variables of the "password" type could be logged in some cases.
7.5
HIGH
CVE-2022-25263
< 2021.2.3
JetBrains TeamCity before 2021.2.3 was vulnerable to OS command injection in the Agent Push feature configuration.
9.8
CRITICAL
CVE-2022-25261
< 2021.2.2
JetBrains TeamCity before 2021.2.2 was vulnerable to reflected XSS.
6.1
MEDIUM
CVE-2022-24342
< 2021.2.1
In JetBrains TeamCity before 2021.2.1, URL injection leading to CSRF was possible.
8.8
HIGH
CVE-2022-24341
< 2021.2.1
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
HIGH
CVE-2022-24340
< 2021.2.1
In JetBrains TeamCity before 2021.2.1, XXE during the parsing of the configuration file was possible.
9.8
CRITICAL
CVE-2022-24339
< 2021.2.1
JetBrains TeamCity before 2021.2.1 was vulnerable to stored XSS.
5.4
MEDIUM
CVE-2022-24338
< 2021.2.1
JetBrains TeamCity before 2021.2.1 was vulnerable to reflected XSS.
6.1
MEDIUM
CVE-2022-24337
< 2021.2
In JetBrains TeamCity before 2021.2, health items of pull requests were shown to users who lacked appropriate permissions.
6.5
MEDIUM
CVE-2022-24336
< 2021.2.1
In JetBrains TeamCity before 2021.2.1, an unauthenticated attacker can cancel running builds via an XML-RPC request to the TeamCit
5.3
MEDIUM
CVE-2022-24335
< 2021.2.1
JetBrains TeamCity before 2021.2 was vulnerable to a Time-of-check/Time-of-use (TOCTOU) race-condition attack in agent registratio
8.1
HIGH
CVE-2022-24334
< 2021.2.1
In JetBrains TeamCity before 2021.2.1, the Agent Push feature allowed selection of any private key on the server.
5.3
MEDIUM
CVE-2022-24333
< 2021.2
In JetBrains TeamCity before 2021.2, blind SSRF via an XML-RPC call was possible.
6.5
MEDIUM
CVE-2022-24332
< 2021.2
In JetBrains TeamCity before 2021.2, a logout action didn't remove a Remember Me cookie.
5.3
MEDIUM
CVE-2022-24331
< 2021.4
In JetBrains TeamCity before 2021.1.4, GitLab authentication impersonation was possible.
9.8
CRITICAL
CVE-2022-24330
< 2021.2.1
In JetBrains TeamCity before 2021.2.1, a redirection to an external site was possible.
6.1
MEDIUM
CVE-2021-43202
< 2021.1.3
In JetBrains TeamCity before 2021.1.3, the X-Frame-Options header is missing in some cases.
9.8
CRITICAL
CVE-2021-43201
< 2021.1.3
In JetBrains TeamCity before 2021.1.3, a newly created project could take settings from an already deleted project.
5.3
MEDIUM
CVE-2021-43200
< 2021.2
In JetBrains TeamCity before 2021.1.2, permission checks in the Agent Push functionality were insufficient.
9.8
CRITICAL
CVE-2021-43199
< 2021.1.2.
In JetBrains TeamCity before 2021.1.2, permission checks in the Create Patch functionality are insufficient.
5.3
MEDIUM
CVE-2021-43198
< 2021.1.2
In JetBrains TeamCity before 2021.1.2, stored XSS is possible.
5.4
MEDIUM
CVE-2021-43197
< 2021.1.2
In JetBrains TeamCity before 2021.1.2, email notifications could include unescaped HTML for XSS.
6.1
MEDIUM
CVE-2021-43196
< 2021.1
In JetBrains TeamCity before 2021.1, information disclosure via the Docker Registry connection dialog is possible.
7.5
HIGH
CVE-2021-43195
< 2021.1.2
In JetBrains TeamCity before 2021.1.2, some HTTP security headers were missing.
5.3
MEDIUM
CVE-2021-43194
< 2021.1.2
In JetBrains TeamCity before 2021.1.2, user enumeration was possible.
5.3
MEDIUM
CVE-2021-43193
< 2021.1.2
In JetBrains TeamCity before 2021.1.2, remote code execution via the agent push functionality is possible.
9.8
CRITICAL
CVE-2021-37548
< 2021.1
In JetBrains TeamCity before 2021.1, passwords in cleartext sometimes could be stored in VCS.
7.5
HIGH
CVE-2021-37547
< 2020.2.4
In JetBrains TeamCity before 2020.2.4, insufficient checks during file uploading were made.
5.3
MEDIUM
CVE-2021-37546
< 2021.1
In JetBrains TeamCity before 2021.1, an insecure key generation mechanism for encrypted properties was used.
5.3
MEDIUM
CVE-2021-37545
< 2021.1
In JetBrains TeamCity before 2021.1.1, insufficient authentication checks for agent requests were made.
7.5
HIGH
CVE-2021-37544
< 2020.2.4
In JetBrains TeamCity before 2020.2.4, there was an insecure deserialization.
9.8
CRITICAL
CVE-2021-37542
< 2020.2.3
In JetBrains TeamCity before 2020.2.3, XSS was possible.
6.1
MEDIUM
CVE-2021-31915
< 2020.2.4
In JetBrains TeamCity before 2020.2.4, OS command injection leading to remote code execution was possible.
9.8
CRITICAL
CVE-2021-31914
< 2020.2.4
In JetBrains TeamCity before 2020.2.4 on Windows, arbitrary code execution on TeamCity Server was possible.
9.8
CRITICAL
CVE-2021-31913
< 2020.2.3
In JetBrains TeamCity before 2020.2.3, insufficient checks of the redirect_uri were made during GitHub SSO token exchange.
7.5
HIGH
CVE-2021-31912
< 2020.2.3
In JetBrains TeamCity before 2020.2.3, account takeover was potentially possible during a password reset.
8.8
HIGH
CVE-2021-31911
< 2020.2.3
In JetBrains TeamCity before 2020.2.3, reflected XSS was possible on several pages.
6.1
MEDIUM
CVE-2021-31910
< 2020.2.3
In JetBrains TeamCity before 2020.2.3, information disclosure via SSRF was possible.
7.5
HIGH
CVE-2021-3315
< 2020.2.2
In JetBrains TeamCity before 2020.2.2, stored XSS on a tests page was possible.
5.4
MEDIUM
CVE-2021-31909
< 2020.2.3
In JetBrains TeamCity before 2020.2.3, argument injection leading to remote code execution was possible.
9.8
CRITICAL
CVE-2021-31908
< 2020.2.3
In JetBrains TeamCity before 2020.2.3, stored XSS was possible on several pages.
5.4
MEDIUM
CVE-2021-31907
< 2020.2.2
In JetBrains TeamCity before 2020.2.2, permission checks for changing TeamCity plugins were implemented improperly.
5.3
MEDIUM
CVE-2021-31906
< 2020.2.2
In JetBrains TeamCity before 2020.2.2, audit logs were not sufficient when an administrator uploaded a file.
2.7
LOW
CVE-2021-31904
< 2020.2.2
In JetBrains TeamCity before 2020.2.2, XSS was potentially possible on the test history page.
6.1
MEDIUM
CVE-2021-26310
< 2020.2.2.85899
In the TeamCity IntelliJ plugin before 2020.2.2.85899, DoS was possible.
7.5
HIGH
CVE-2021-26309
< 2020.2.2.85899
Information disclosure in the TeamCity plugin for IntelliJ before 2020.2.2.85899 was possible because a local temporary file had I
3.3
LOW
CVE-2021-25778
< 2020.2.1
In JetBrains TeamCity before 2020.2.1, permissions during user deletion were checked improperly.
5.3
MEDIUM
CVE-2021-25777
< 2020.2.1
In JetBrains TeamCity before 2020.2.1, permissions during token removal were checked improperly.
5.3
MEDIUM
CVE-2021-25776
< 2020.2
In JetBrains TeamCity before 2020.2, an ECR token could be exposed in a build's parameters.
7.5
HIGH
CVE-2021-25775
< 2020.2.1
In JetBrains TeamCity before 2020.2.1, the server admin could create and see access tokens for any other users.
3.8
LOW
CVE-2021-25774
< 2020.2.1
In JetBrains TeamCity before 2020.2.1, a user could get access to the GitHub access token of another user.
4.3
MEDIUM
CVE-2021-25773
< 2020.2
JetBrains TeamCity before 2020.2 was vulnerable to reflected XSS on several pages.
6.1
MEDIUM
CVE-2021-25772
< 2020.2.2
In JetBrains TeamCity before 2020.2.2, TeamCity server DoS was possible via server integration.
5.3
MEDIUM
CVE-2020-35667
< 2020.2.85695
JetBrains TeamCity Plugin before 2020.2.85695 SSRF. Vulnerability that could potentially expose user credentials.
7.5
HIGH
CVE-2020-27627
< 2020.1.2
JetBrains TeamCity before 2020.1.2 was vulnerable to URL injection.
6.1
MEDIUM
CVE-2020-27629
< 2020.1.5
In JetBrains TeamCity before 2020.1.5, secure dependency parameters could be not masked in depending builds when there are no inte
5.3
MEDIUM
CVE-2020-27628
< 2020.1.5
In JetBrains TeamCity before 2020.1.5, the Guest user had access to audit records.
4.3
MEDIUM
CVE-2020-15831
< 2019.2.3
JetBrains TeamCity before 2019.2.3 is vulnerable to reflected XSS in the administration UI.
6.1
MEDIUM
CVE-2020-15830
< 2019.2.3
JetBrains TeamCity before 2019.2.3 is vulnerable to stored XSS in the administration UI.
6.1
MEDIUM
CVE-2020-15829
< 2019.2.3
In JetBrains TeamCity before 2019.2.3, password parameters could be disclosed via build logs.
5.3
MEDIUM
CVE-2020-15828
< 2020.1.1
In JetBrains TeamCity before 2020.1.1, project parameter values can be retrieved by a user without appropriate permissions.
6.5
MEDIUM
CVE-2020-15826
< 2020.1
In JetBrains TeamCity before 2020.1, users are able to assign more permissions than they have.
4.3
MEDIUM
CVE-2020-15825
< 2020.1
In JetBrains TeamCity before 2020.1, users with the Modify Group permission can elevate other users' privileges.
8.8
HIGH
CVE-2020-11938
>= 2018.2 and <= 2019.2.1
In JetBrains TeamCity 2018.2 through 2019.2.1, a project administrator was able to see scrambled password parameters used in a pro
4.9
MEDIUM
CVE-2020-11689
< 2019.2.1
In JetBrains TeamCity before 2019.2.1, a user without appropriate permissions was able to import settings from the settings.kts fi
6.5
MEDIUM
CVE-2020-11688
< 2019.2.1
In JetBrains TeamCity before 2019.2.1, the application state is kept alive after a user ends his session.
7.5
HIGH
CVE-2020-11687
< 2019.2.2
In JetBrains TeamCity before 2019.2.2, password values were shown in an unmasked format on several pages.
7.5
HIGH
CVE-2020-11686
< 2019.1.4
In JetBrains TeamCity before 2019.1.4, a project administrator was able to retrieve some TeamCity server settings.
2.7
LOW
CVE-2020-7911
< 2019.2.0
In JetBrains TeamCity before 2019.2, several user-level pages were vulnerable to XSS.
6.1
MEDIUM
CVE-2020-7910
< 2019.2.0
JetBrains TeamCity before 2019.2 was vulnerable to a stored XSS attack by a user with the developer role.
5.4
MEDIUM
CVE-2020-7909
< 2019.1.5
In JetBrains TeamCity before 2019.1.5, some server-stored passwords could be shown via the web UI.
7.5
HIGH
CVE-2020-7908
< 2019.1.5
In JetBrains TeamCity before 2019.1.5, reverse tabnabbing was possible on several pages.
4.3
MEDIUM
CVE-2019-18367
< 2019.1.2
In JetBrains TeamCity before 2019.1.2, a non-destructive operation could be performed by a user without the corresponding permissi
5.3
MEDIUM
CVE-2019-18366
< 2019.1.2
In JetBrains TeamCity before 2019.1.2, secure values could be exposed to users with the "View build runtime parameters and data" p
5.3
MEDIUM
CVE-2019-18365
< 2019.1.4
In JetBrains TeamCity before 2019.1.4, reverse tabnabbing was possible on several pages.
4.3
MEDIUM
CVE-2019-18364
< 2019.1.4
In JetBrains TeamCity before 2019.1.4, insecure Java Deserialization could potentially allow remote code execution.
9.8
CRITICAL
CVE-2019-18363
< 2019.1.2
In JetBrains TeamCity before 2019.1.2, access could be gained to the history of builds of a deleted build configuration under some
5.3
MEDIUM
CVE-2019-15037
all versions
An issue was discovered in JetBrains TeamCity 2018.2.4. It had several XSS vulnerabilities on the settings pages. The issues were
6.1
MEDIUM
CVE-2019-15036
all versions
An issue was discovered in JetBrains TeamCity 2018.2.4. A TeamCity Project administrator could execute any command on the server m
7.2
HIGH
CVE-2019-12157
< 2018.2.5
In JetBrains UpSource versions before 2018.2 build 1293, there is credential disclosure via RPC commands.
9.8
CRITICAL
CVE-2019-15035
all versions
An issue was discovered in JetBrains TeamCity 2018.2.4. A TeamCity Project administrator could get access to potentially confident
4.9
MEDIUM
CVE-2019-15042
all versions
An issue was discovered in JetBrains TeamCity 2018.2.4. It had no SSL certificate validation for some external https connections.
7.5
HIGH
CVE-2019-15038
all versions
An issue was discovered in JetBrains TeamCity 2018.2.4. The TeamCity server was not using some security-related HTTP headers. The
7.5
HIGH
CVE-2019-15039
all versions
An issue was discovered in JetBrains TeamCity 2018.2.4. It had a possible remote code execution issue. This was fixed in TeamCity
9.8
CRITICAL
CVE-2019-15848
all versions
JetBrains TeamCity 2019.1 and 2019.1.1 allows cross-site scripting (XSS), potentially making it possible to send an arbitrary HTTP
6.1
MEDIUM
CVE-2019-12846
< 2018.2.2
A user without the required permissions could gain access to some JetBrains TeamCity settings. The issue was fixed in TeamCity 201
4.3
MEDIUM
CVE-2019-12845
< 2018.2.3
The generated Kotlin DSL settings allowed usage of an unencrypted connection for resolving artifacts. The issue was fixed in JetBr
5.3
MEDIUM
CVE-2019-12844
< 2018.2.3
A possible stored JavaScript injection was detected on one of the JetBrains TeamCity pages. The issue was fixed in TeamCity 2018.2
6.1
MEDIUM
CVE-2019-12843
< 2018.2.3
A possible stored JavaScript injection requiring a deliberate server administrator action was detected. The issue was fixed in Jet
6.1
MEDIUM
CVE-2019-12842
< 2018.2.2
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
MEDIUM
CVE-2019-12841
< 2018.2.2
Incorrect handling of user input in ZIP extraction was detected in JetBrains TeamCity. The issue was fixed in TeamCity 2018.2.2.
7.5
HIGH
CVE-2014-10036
<= 8.0
Cross-site scripting (XSS) vulnerability in JetBrains TeamCity before 8.1 allows remote attackers to inject arbitrary web script o
CVE-2014-10002
<= 8.0
Unspecified vulnerability in JetBrains TeamCity before 8.1 allows remote attackers to obtain sensitive information via unknown vec
Vulnerabilities
CISA KEV catalog
CWE weaknesses
CAPEC attack patterns
Package vulnerabilities
Threat intelligence
Threat actors
Tools & malware
ATT&CK techniques
IOCs
Detection & defense
Sigma rules
YARA rules
Atomic Red Team tests
D3FEND countermeasures
Compliance
NIST 800-53
ISO 27001:2022
SOC 2 TSC
PCI-DSS v4.0
CIS Controls v8.1
About
All capabilities
Live statistics
Data sources
Privacy policy
Terms of service
threatengine.sh · Open-source threat intelligence platform · 100+ authoritative sources · Every fact traces to its origin