dbcve.org
TeamcityApplication · Jetbrains

CVE-2022-25263

CRITICAL · 9.8 CVSS v3.1 Published 2022-02-25
Fix available
A fix is available. Upgrade to 2021.2.3 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
JetBrains TeamCity before 2021.2.3 was vulnerable to OS command injection in the Agent Push feature configuration.

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 · high confidence

JetBrains TeamCity versions before 2021.2.3 contain an OS command injection vulnerability in the Agent Push feature configuration. An authenticated attacker with appropriate Agent Push permissions can inject and execute arbitrary operating system commands on the TeamCity server with elevated privileges.

MitigationUpgrade TeamCity to version 2021.2.3 or later to patch the command injection vulnerability. Restrict Agent Push feature permissions to only trusted administrators until the upgrade is completed.

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.2.3

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. Identify TeamCity installation and version
    Check the TeamCity server for the version number. This is typically visible on the TeamCity web interface login page, in the server administration area under 'Server Administration > Diagnostics', or in the /buildAgent directory if agents are installed. Run: `cat <teamcity_installation_dir>/buildserver/version.txt` or check the TeamCity web UI footer for the version string.
    Affected if The installed version is earlier than 2021.2.3 (for example, 2021.2.2, 2021.2.1, 2021.1.x, 2020.x, etc.)
  2. Verify Agent Push feature is accessible
    Log into the TeamCity web interface and navigate to the Agent Push configuration area. This is typically found under 'Server Administration > Agent Push' or 'Project Settings > Agent Push'. Check if the feature exists and is accessible to your user account.
    Affected if The Agent Push feature is enabled and accessible to authenticated users with Agent Push permissions in your environment.
  3. Review Agent Push permissions
    In TeamCity, go to 'Server Administration > Users' or 'Server Administration > Roles' and review which users or groups have the 'Agent Push' permission or 'Enable agent push' role assigned. Check the project-level and server-level role assignments.
    Affected if Users other than trusted administrators have Agent Push permissions, or permissions are granted too broadly.
  4. Inspect Agent Push configuration settings
    Navigate to the Agent Push configuration page in TeamCity and examine the settings. Look for fields related to agent installation paths, commands, or any configuration that could accept operating system commands. Check if custom commands or paths are configured.
    Affected if The Agent Push configuration contains custom commands, scripts, or paths that could be manipulated for command injection.

You are affected if your TeamCity version is earlier than 2021.2.3 AND the Agent Push feature is enabled with permissions granted to users who could exploit the command injection flaw.

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.2.3 or later
Fixed in 2021.2.3
Interim mitigation

Upgrade TeamCity to version 2021.2.3 or later to patch the command injection vulnerability. Restrict Agent Push feature permissions to only trusted administrators until the upgrade is completed.

Recommended fix Moderate confidence

2021.2.3 or later

  1. 1. Back up your TeamCity server data and configuration before starting the upgrade
  2. 2. Download TeamCity version 2021.2.3 or a later stable release from the official JetBrains website
  3. 3. Follow the standard TeamCity upgrade procedure: stop the TeamCity server, run the installer or deploy the new version, and start the server
  4. 4. After upgrade, verify that the Agent Push feature functions correctly and that the vulnerability is remediated
  5. 5. Review TeamCity release notes for any additional security patches in your chosen version
Caveat Review the 2021.2.x release notes for any breaking changes specific to your plugins or custom configurations before upgrading

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

Fix this in Teamcity Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,720
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-25263 — 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-25263 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