dbcve.org
TeamcityApplication · Jetbrains

CVE-2022-24338

MEDIUM · 6.1 CVSS v3.1 Published 2022-02-25
Fix available
A fix is available. Upgrade to 2021.2.1 or later.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable No privileges

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.1 was vulnerable to reflected XSS.

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

Reflected XSS vulnerability in JetBrains TeamCity before 2021.2.1 allows attackers to inject malicious scripts via URL parameters, which execute in the victim's browser when they click a crafted link.

MitigationUpgrade TeamCity to version 2021.2.1 or later to patch the reflected XSS 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.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
Low
Privileges
None
User interaction
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/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 checks

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

  1. Locate TeamCity version information
    Access the TeamCity administration interface and navigate to the 'About' or 'Server Administration' section, which typically displays the installed version number. Alternatively, check the buildServerConfig.xml file or the logs directory for version metadata.
    Affected if The displayed version is a release earlier than 2021.2.1 (for example, 2021.2.0, 2021.1.x, or any earlier major version).
  2. Confirm version via startup logs
    Review the TeamCity server startup logs (usually found in the logs/teamcity-server.log file) or the initial setup page rendered when accessing the TeamCity URL. These sources commonly report the exact version during server initialization.
    Affected if The version logged at startup or displayed on the server info page is below 2021.2.1.
  3. Check UI endpoint for version disclosure
    Access the TeamCity REST API endpoint /app/rest/server/version or navigate to the 'Server Health' section under the Administration menu to view version details programmatically or through the web interface.
    Affected if The returned version string or displayed value is less than 2021.2.1.
  4. Identify if unauthenticated URL parameters are processed
    Review the TeamCity web configuration to confirm that URL parameter handling for unauthenticated or authenticated users is enabled. For reflected XSS, the vulnerability triggers when crafted URLs with malicious parameters are accessed.
    Affected if The TeamCity instance processes URL parameters from user-supplied links and the server version is below 2021.2.1, meaning the reflected XSS vector is present.

A TeamCity installation is affected if its running version is any release earlier than 2021.2.1, as this version introduced the patch for the reflected XSS in URL parameters.

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.1 or later to patch the reflected XSS vulnerability.

Recommended fix High confidence

TeamCity 2021.2.1 or later

  1. Backup your current TeamCity data and configuration
  2. Download TeamCity 2021.2.1 or later from the official JetBrains website
  3. Follow the standard TeamCity upgrade procedure (stop the server, replace the installation files, start the server)
  4. Verify the upgrade was successful by logging into the web interface
  5. Confirm the XSS vulnerability is no longer present
Caveat Review TeamCity 2021.2.1 release notes for any configuration or feature changes

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

Fix this in Teamcity Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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