dbcve.org
TeamcityApplication · Jetbrains

CVE-2024-36371

MEDIUM · 5.4 CVSS v3.1 Published 2024-05-29
Fix available
A fix is available. Upgrade to 2023.05.6 / 2023.11.5 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 2023.05.6, 2023.11.5 stored XSS in Commit status publisher 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

A stored cross-site scripting (XSS) vulnerability exists in the Commit status publisher feature of JetBrains TeamCity versions prior to 2023.05.6 and 2023.11.5. An attacker could inject malicious JavaScript or HTML into commit status messages that get stored and executed when other users view these statuses.

MitigationUpgrade TeamCity to version 2023.05.6, 2023.11.5, or later to remediate the stored XSS vulnerability in the Commit status publisher.

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:< 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. Determine TeamCity version
    Access the TeamCity server administration page, typically at /app/admin/serverOverview.html, or check the buildServer.properties file in the TeamCity data directory for the version number
    Affected if The installed version is earlier than 2023.05.6, or is 2023.11.x earlier than 2023.11.5 (versions 2023.11.0 through 2023.11.4)
  2. Locate the Commit Status Publisher configuration
    Navigate to the TeamCity administration interface, then to the 'VCS Settings' or 'Version Control Settings' for your projects, and locate any configured Commit Status Publisher plugins or integrations
    Affected if The Commit Status Publisher feature is enabled and configured for one or more build configurations
  3. Identify stored commit status messages
    Review build logs and commit status entries displayed in the TeamCity web UI under the 'Changes' or 'Build Status' sections, particularly those showing external VCS integration statuses
    Affected if There are existing commit status messages stored in the system that could contain injected payloads (requires manual inspection of the raw status data)
  4. Verify user access to status views
    Check which TeamCity users and roles have permission to view build status and commit status pages in the 'Roles and Permissions' administration section
    Affected if Multiple users or roles can view commit status messages, as this determines the potential impact of stored XSS execution

You are affected if your TeamCity version is earlier than 2023.05.6 or falls between 2023.11.0 and 2023.11.4 inclusive, AND the Commit Status Publisher feature is enabled and being used in your environment.

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 2023.05.6 / 2023.11.5 or later
Fixed in 2023.05.62023.11.5
Interim mitigation

Upgrade TeamCity to version 2023.05.6, 2023.11.5, or later to remediate the stored XSS vulnerability in the Commit status publisher.

Recommended fix High confidence

2023.05.6 or 2023.11.5 (or later)

  1. Backup your TeamCity data and configuration before proceeding with the upgrade
  2. Stop the TeamCity server
  3. Download the fixed TeamCity version (2023.05.6 or 2023.11.5 or later) from the official JetBrains website
  4. Install or upgrade TeamCity to the selected fixed version following the standard upgrade procedure
  5. Start the TeamCity server
  6. Verify the upgrade was successful and the server is functioning properly
Caveat Standard TeamCity upgrade considerations apply - review release notes for migration requirements and test in non-production environment first

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

Fix this in Teamcity Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA3.0 h
21.0 hours of engineering $3,680
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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