dbcve.org
TeamcityApplication · Jetbrains

CVE-2022-24335

HIGH · 8.1 CVSS v3.1 Published 2022-02-25
Fix available
A fix is available. Upgrade to 2021.2.1 or later.
See remediation →
90/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 was vulnerable to a Time-of-check/Time-of-use (TOCTOU) race-condition attack in agent registration via XML-RPC.

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

TeamCity before version 2021.2 contains a Time-of-check/Time-of-use (TOCTOU) race condition vulnerability in the build agent registration process via XML-RPC. An unauthenticated attacker could potentially exploit this race condition during agent registration to hijack or impersonate a build agent, potentially gaining code execution privileges on the TeamCity server.

MitigationUpgrade TeamCity to version 2021.2 or later. If immediate upgrade is not possible, consider restricting XML-RPC agent registration interfaces via network controls or disabling untrusted agent registration.

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

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
High
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:H/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. Determine installed TeamCity version
    Access the TeamCity administration web interface and navigate to 'Administration' > 'Server Administration' > 'Server Information', or check the buildServer.properties configuration file in the TeamCity data directory for the version string.
    Affected if The displayed version is earlier than 2021.2.1 (for example, 2021.1.x, 2021.0.x, or older major versions).
  2. Check if XML-RPC agent registration is enabled
    In the TeamCity web UI, go to 'Administration' > 'Server Administration' > 'Agent Connections' and verify whether the 'Allow agents to register via XML-RPC' or similar option is enabled. Alternatively, inspect the internal.properties or buildAgent.properties configuration files for XML-RPC related settings.
    Affected if XML-RPC agent registration is explicitly enabled in the TeamCity configuration.
  3. Verify network exposure of XML-RPC interface
    Identify the XML-RPC port (default 9090) used by TeamCity for agent communication. Check network firewall rules, security groups, or port bindings to determine if this port is accessible from untrusted networks or the public internet.
    Affected if The XML-RPC port (typically 9090) is exposed to untrusted or public network segments without authentication barriers.
  4. Confirm unauthenticated agent registration is permitted
    Review TeamCity server logs for any failed or successful agent registration attempts from unexpected sources. Check the 'Agents' section in the web UI to see registered agents and verify if any unauthorized agents have connected.
    Affected if Agents can register without proper authentication or unexpected agents appear in the agent pool.

A TeamCity installation is affected if it runs a version earlier than 2021.2.1 AND has XML-RPC agent registration enabled AND is network-accessible to untrusted parties, allowing potential exploitation of the TOCTOU race condition.

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.1 or later
Fixed in 2021.2.1
Interim mitigation

Upgrade TeamCity to version 2021.2 or later. If immediate upgrade is not possible, consider restricting XML-RPC agent registration interfaces via network controls or disabling untrusted agent registration.

Recommended fix High confidence

TeamCity 2021.2.1 or later

  1. Upgrade TeamCity to version 2021.2.1 or later to remediate the TOCTOU race condition vulnerability in agent registration via XML-RPC
Caveat Review TeamCity upgrade notes for potential breaking changes between your current version and 2021.2.1

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

Fix this in Teamcity Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing6.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,580
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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