dbcve.org
TeamcityApplication · Jetbrains

CVE-2022-24331

CRITICAL · 9.8 CVSS v3.1 Published 2022-02-25
Fix available
A fix is available. Upgrade to 2021.4 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
In JetBrains TeamCity before 2021.1.4, GitLab authentication impersonation was possible.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

In JetBrains TeamCity before 2021.1.4, a vulnerability in the GitLab authentication integration allowed attackers to impersonate legitimate users, potentially gaining unauthorized access to the CI/CD platform and its resources.

MitigationUpgrade TeamCity to version 2021.1.4 or later to remediate the GitLab authentication impersonation vulnerability.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
TeamcityApplication
Affected:< 2021.4

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Locate the TeamCity installation directory
    Identify the TeamCity home directory (commonly at /TeamCity on Linux or C:\TeamCity on Windows). Check for the /buildAgent directory or the main TeamCity server files.
    Affected if TeamCity is not installed on the system.
  2. Determine the installed TeamCity version
    Look for a version file in the installation directory, typically found in /buildServer/VERSION or /buildServer/build.txt. Alternatively, access the TeamCity administration UI and navigate to Administration > Server Administration to view the version number.
    Affected if Unable to locate or read the version information.
  3. Check if GitLab authentication integration is enabled
    In the TeamCity web UI, go to Administration > Authentication Settings. Look for GitLab or GitLab.com listed as an enabled authentication module. If using external authentication configuration files, inspect the <authenticator> settings in the main-config.xml file.
    Affected if GitLab authentication integration is not configured or enabled.
  4. Compare the installed version against the affected range
    Match the discovered version number to the range TeamCity < 2021.1.4. If the version string begins with a number lower than 2021.1.4 (such as 2021.1.3, 2021.0.x, or earlier), the instance is in the affected range.
    Affected if The installed version is 2021.1.3 or earlier, or any version below 2021.1.4.

You are affected if TeamCity is installed with GitLab authentication integration enabled and the server version is below 2021.1.4.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 2021.4 or later
Fixed in 2021.4
Interim mitigation

Upgrade TeamCity to version 2021.1.4 or later to remediate the GitLab authentication impersonation vulnerability.

Recommended fix High confidence

2021.1.4 or later (2021.4.x recommended for additional fixes)

  1. Back up your TeamCity instance and database before upgrading
  2. Download TeamCity 2021.1.4 or later from the official JetBrains website
  3. Review the upgrade documentation at https://www.jetbrains.com/help/teamcity/upgrade.html
  4. Stop the TeamCity server
  5. Run the installer for the new version, pointing to the existing TeamCity data directory
  6. Start the TeamCity server after upgrade completes
  7. Verify GitLab authentication is working correctly
  8. Confirm the vulnerability is resolved by testing GitLab authentication impersonation scenarios
Caveat Standard TeamCity upgrade considerations apply - review release notes for breaking changes between your current version and target version

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Teamcity Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-24331 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2022-24331 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data