dbcve.org
TeamcityApplication · Jetbrains

CVE-2024-31138

MEDIUM · 5.4 CVSS v3.1 Published 2024-03-28
Fix available
A fix is available. Upgrade to 2024.03 or later.
See remediation →
58/100
Remediation priority · Elevated
High EPSS 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 2024.03 xSS was possible via Agent Distribution settings

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

Cross-site scripting (XSS) vulnerability in JetBrains TeamCity versions prior to 2024.03 allows injection of malicious scripts through the Agent Distribution settings. The vulnerability has a CVSS score of 5.4 (Medium), indicating moderate severity with low privileges required and user interaction needed.

MitigationUpgrade to TeamCity version 2024.03 or later to obtain the patch for this 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:< 2024.03

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. Identify TeamCity installation and version
    Log into the TeamCity web interface and navigate to the Administration > Server Administration page, or check the buildServer.properties configuration file for the version property. The version is also displayed on the login page footer.
    Affected if The installed version is any release prior to 2024.03 (for example, 2024.02, 2023.11, etc.)
  2. Confirm Agent Distribution feature is accessible
    Navigate to the Agent Distribution settings page within TeamCity (typically found under Agent > Agent Distribution or in the project build configuration settings). Verify if this feature is enabled for any project or build configuration.
    Affected if The Agent Distribution feature is enabled and accessible to the user account being tested
  3. Verify user role permissions
    Check the user or user group permissions in TeamCity Administration > Users and Administration > User Groups. Determine if the tested account has low-level privileges such as Project Viewer, Agent Manager, or similar roles that can access Agent Distribution.
    Affected if The account has low privileges (such as Project Viewer or limited project access) and can still access the Agent Distribution settings interface
  4. Test for XSS in Agent Distribution parameters
    In the Agent Distribution settings (e.g., when assigning agents to build configurations), attempt to inject a harmless test script payload into fields such as agent name, build configuration name, or distribution parameters. Use a browser developer console or network tool to observe if the payload is reflected without encoding.
    Affected if User-supplied input in Agent Distribution fields is reflected in the response without proper HTML encoding or sanitization

A user is affected if their TeamCity version is earlier than 2024.03 and the Agent Distribution feature is accessible to users with low-level privileges, allowing injected scripts to execute when viewing or interacting with those settings.

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 2024.03 or later
Fixed in 2024.03
Interim mitigation

Upgrade to TeamCity version 2024.03 or later to obtain the patch for this XSS vulnerability.

Recommended fix High confidence

TeamCity 2024.03

  1. Upgrade JetBrains TeamCity to version 2024.03 or later to remediate the XSS vulnerability in Agent Distribution settings

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

Fix this in Teamcity Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing3.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,750
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,800.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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