dbcve.org
TeamcityApplication · Jetbrains

CVE-2024-36367

MEDIUM · 6.1 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 →
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
In JetBrains TeamCity before 2022.04.7, 2022.10.6, 2023.05.6, 2023.11.5 stored XSS via third-party reports 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 allows attackers to inject malicious scripts via third-party report functionality. The injected script persists and executes when other users view the affected reports, enabling session hijacking or data theft.

MitigationUpgrade TeamCity to version 2022.04.7 or later, 2022.10.6 or later, 2023.05.6 or later, or 2023.11.5 or later. Until patched, restrict access to the third-party reports feature to trusted users only.

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
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. Check TeamCity server version
    Log in to TeamCity as administrator and navigate to Administration > Server Configuration > About, or check the version from the server login page footer. Alternatively, inspect the TeamCity installation directory for version metadata.
    Affected if The installed version falls into any of these ranges: < 2022.04.7, >= 2022.10 but < 2022.10.6, >= 2023.05 but < 2023.05.6, or >= 2023.11 but < 2023.11.5
  2. Identify if third-party report functionality is in use
    Review TeamCity build configurations to determine if any third-party reporting tools (such as code quality, test coverage, or static analysis plugins) are configured to generate and display reports within TeamCity.
    Affected if Third-party report generation or display features are enabled and accessible to users in your TeamCity instance
  3. Inspect report generation settings for input handling
    Examine the Administration > Project Settings > Report tabs or similar sections where third-party integrations define how report content is processed and displayed.
    Affected if The report functionality accepts user-supplied content or external inputs without sanitization, allowing unsanitized data to be stored and rendered

You are affected if your TeamCity version is below the fixed releases AND the third-party report feature is enabled and processing external content that could be viewed by other users.

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 or later, 2022.10.6 or later, 2023.05.6 or later, or 2023.11.5 or later. Until patched, restrict access to the third-party reports feature to trusted users only.

Recommended fix High confidence

2023.11.5 (or latest stable release)

  1. 1. Backup your TeamCity database and all configuration files before proceeding with the upgrade
  2. 2. Download the latest stable TeamCity version (2023.11.5 or newer) from the official JetBrains website (www.jetbrains.com/teamcity/download)
  3. 3. Stop the TeamCity server gracefully
  4. 4. Run the TeamCity upgrade installer on your existing installation directory
  5. 5. Follow the on-screen prompts to complete the upgrade process
  6. 6. Start the TeamCity server and verify all services are running properly
  7. 7. Test that third-party report functionality works correctly and that XSS is no longer present
Caveat Review JetBrains release notes for any breaking changes between your current version and 2023.11.5, particularly regarding third-party report plugins

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

Fix this in Teamcity Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,390
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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