dbcve.org
TeamcityApplication · Jetbrains

CVE-2024-36369

MEDIUM · 5.4 CVSS v3.1 Published 2024-05-29
Fix available
A fix is available. Upgrade to 2022.04.7 / 2022.10.6 or later.
See remediation →
58/100
Remediation priority · Elevated
Remotely reachable

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
In JetBrains TeamCity before 2022.04.7, 2022.10.6, 2023.05.6, 2023.11.5 stored XSS via issue tracker integration 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 confidence

Stored XSS vulnerability in JetBrains TeamCity's issue tracker integration allows attackers to inject malicious scripts that persist on the server and execute when other users view the compromised issue tracker data. The vulnerability affects multiple versions prior to the patched releases.

MitigationUpgrade TeamCity to version 2022.04.7, 2022.10.6, 2023.05.6, 2023.11.5 or later. If immediate upgrade is not feasible, disable or restrict the issue tracker integration as a temporary measure.

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:< 2022.04.7>= 2022.10, < 2022.10.6>= 2023.05, < 2023.05.6>= 2023.11, < 2023.11.5

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
Low
User interaction
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/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. Check installed TeamCity version
    Log into the TeamCity web UI as administrator, then navigate to 'Administration' > 'Server Administration' > 'Server Information' to view the exact version number. Alternatively, check the startup logs or the 'TeamCity/data/version.txt' file in the installation directory.
    Affected if The displayed version falls into any of these ranges: < 2022.04.7, >= 2022.10 and < 2022.10.6, >= 2023.05 and < 2023.05.6, or >= 2023.11 and < 2023.11.5
  2. Verify issue tracker integration status
    In the TeamCity web UI, go to 'Administration' > 'Issue Trackers' to see if any issue tracker connections (such as JetBrains YouTrack, GitHub, GitLab, or other integrated systems) are configured and enabled.
    Affected if Any issue tracker integration is configured and active on the server
  3. Check for custom issue tracker templates or third-party plugins
    Navigate to 'Administration' > 'Plugins' to list all installed plugins. Review any custom or third-party issue tracker-related plugins that may interface with external systems.
    Affected if Third-party or custom plugins related to issue tracking are installed

You are affected if your TeamCity version is below any of these thresholds (2022.04.7, 2022.10.6, 2023.05.6, or 2023.11.5) AND the issue tracker integration feature is configured or enabled.

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 2022.04.7 / 2022.10.6 / 2023.05.6 or later
Fixed in 2022.04.72022.10.62023.05.6
Interim mitigation

Upgrade TeamCity to version 2022.04.7, 2022.10.6, 2023.05.6, 2023.11.5 or later. If immediate upgrade is not feasible, disable or restrict the issue tracker integration as a temporary measure.

Recommended fix High confidence

Upgrade to 2023.11.5 or later (latest stable release recommended)

  1. 1. Back up your TeamCity database and configuration files before upgrading
  2. 2. Download the fixed TeamCity version from jetbrains.com (2022.04.7, 2022.10.6, 2023.05.6, or 2023.11.5 or later)
  3. 3. Stop the TeamCity server and agents
  4. 4. Install the new version using the standard TeamCity upgrade procedure
  5. 5. Start the TeamCity server and verify the issue tracker integration works correctly
  6. 6. Validate that the XSS vulnerability is no longer present by testing issue tracker functionality
Caveat TeamCity upgrades may require database migration; review release notes for breaking changes between major versions

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

Fix this in Teamcity Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
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,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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