CVE-2022-24336
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 · uneditedIn JetBrains TeamCity before 2021.2.1, an unauthenticated attacker can cancel running builds via an XML-RPC request to the TeamCity server.
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 confidenceAn unauthenticated remote attacker can cancel running builds on JetBrains TeamCity servers prior to version 2021.2.1 by sending a specially crafted XML-RPC request to the server's XML-RPC endpoint. This allows any user without credentials to disrupt CI/CD pipeline operations by terminating active builds.
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< 2021.2.1CVSS 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
- None
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N
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 checksWork through these to decide whether this CVE applies to you.
-
Identify TeamCity installationLocate TeamCity server by checking for running processes (look for java processes with TeamCity in command line), checking common installation paths, or querying port 8111 (default TeamCity port)Affected if TeamCity server is running and accessible on the network
-
Determine installed TeamCity versionAccess the TeamCity web interface and check the version displayed in the footer, or check version.txt in the TeamCity installation directoryAffected if Version is lower than 2021.2.1 (e.g., 2021.2.0, 2021.1.x, 2021.0.x, etc.)
-
Check if XML-RPC endpoint is accessibleSend an HTTP request to the XML-RPC endpoint (typically /xml-rpc or /RPC2) on the TeamCity server portAffected if The XML-RPC endpoint responds (returns any HTTP response other than 404/403), indicating the interface is enabled and reachable
User is affected if they are running TeamCity version below 2021.2.1 AND the XML-RPC endpoint is accessible on their server.
Generated from the published advisory. Verify against your own configuration.
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 · scoped2021.2.1
Upgrade TeamCity to version 2021.2.1 or later to patch this vulnerability. If XML-RPC functionality is not required, disable the XML-RPC interface as an additional hardening measure.
TeamCity 2021.2.1 or later
- Back up your TeamCity server data and configuration before upgrading
- Schedule a maintenance window for the upgrade process
- Download TeamCity 2021.2.1 or a later stable version from the official JetBrains website (https://www.jetbrains.com/teamcity/download/)
- Follow the official TeamCity upgrade instructions to install the new version
- After upgrade, verify that: (a) the server starts successfully, (b) existing builds and configurations are intact, (c) the XML-RPC interface is properly secured and requires authentication
- Consider disabling the XML-RPC interface if not needed by configuring the TeamCity server settings
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-24336 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2022-24336 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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