CVE-2022-24340
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, XXE during the parsing of the configuration file 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 · high confidenceXML External Entity (XXE) vulnerability in JetBrains TeamCity allows remote attackers to inject malicious XML entities during configuration file parsing, potentially enabling file disclosure, SSRF, or denial of service attacks.
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
- 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 checksWork through these to decide whether this CVE applies to you.
-
Check TeamCity versionAccess the TeamCity administration interface and navigate to 'Administration' > 'Server Administration' > 'Server Information' to view the exact version number. Alternatively, check the buildServer.properties file in the TeamCity data directory for the version property.Affected if The displayed version is lower than 2021.2.1 (for example, 2021.2.0, 2021.1.x, 2020.x, or earlier releases).
-
Identify XML configuration file processingReview any custom or third-party plugins that parse XML configuration files, particularly those that handle import or export of project settings, build configurations, or user-defined XML files.Affected if TeamCity is using plugins or custom scripts that parse XML files with the underlying XML parser having external entity processing enabled (DOCTYPE declarations allowed).
-
Check for exposed XML upload or import featuresLocate any web endpoints, REST API calls, or administrative functions that accept XML file uploads or external XML entity imports, such as project configuration import, backup restoration, or plugin configuration.Affected if The server exposes functionality that processes user-supplied or externally-fetched XML files without disabling external entity resolution.
You are affected if your TeamCity installation version is below 2021.2.1 AND the server processes XML files with external entity processing enabled through plugins, imports, or configuration parsing features.
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. If immediate upgrade is not feasible, disable external entity processing in the XML parser and review configuration file handling.
TeamCity 2021.2.1 or later
- 1. Backup your current TeamCity data and configuration files.
- 2. Download TeamCity 2021.2.1 or a later stable version from the official JetBrains website.
- 3. Stop the running TeamCity server.
- 4. Install the new version following the standard upgrade procedure.
- 5. Start the TeamCity server and verify all services are running correctly.
- 6. Test that the configuration file parsing functionality works as expected.
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation6.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-24340 — 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-24340 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